MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

MCP News: the Model Context Protocol ecosystem, verified

MCP News catalogs 796 MCP entities (781 servers, 15 clients) with verified facts: 48 verified on the current spec revision (2026-07-28), 76 verified first-party servers.

Model Context Protocol project
security

Thirty-three further MCP security records landed between September 3 and 15; here is each one

Between 2026-09-03 and 2026-09-15, thirty-three more MCP security records were published or entered a GitHub/NVD listing outside the AWS Labs, IBM ContextForge, Langflow, firecrawl-mcp-server, and CKAN MCP Server stories already covered this cycle. They range from a same-day critical authorization bypass in Casdoor's /api/mcp endpoint, unpatched as of this fetch, to a coordinated VulnCheck batch of path-traversal and injection findings against several single-purpose stdio servers published within about thirty minutes on 2026-09-04. A third Kotlin SDK advisory, a ninth MCPHub CVE, a fifth SiYuan record, and a second three-CVE PraisonAI batch extend stories already running. Severity below is stated exactly as each discloser framed it.

· verified 2026-09-15

server release

Go SDK 1.8.0 hardens transports against resource exhaustion and lets servers narrow protocol versions

The official Go SDK released v1.8.0 on 2026-09-14, equivalent to the v1.8.0-pre.2 pre-release that opened the cycle on 2026-09-04. The release adds no new protocol revision: per the release notes, "2026-07-28 remains the newest version the SDK negotiates." It bounds decoding paths that previously buffered input without limit, including JSON nesting depth, SSE event size, stdio frame length, and OAuth dynamic client registration responses, and adds ServerOptions.SupportedProtocolVersions and ServerOptions.SetCacheable.

client release

Goose 1.50.1 rolls back the "prefer latest MCP version" change that 1.50.0 shipped six days earlier, after it broke stdio and streamable_http extension startup

Goose released v1.49.0 on 2026-09-03 with several MCP-relevant additions: sampling support for reasoning-first responses, pre-registered OAuth clients for streamable_http extensions, MCP conformance tests added to CI, Unicode tag sanitization in MCP prompts, and preserving extensions when adding MCP servers. v1.50.0, released 2026-09-08, shipped "Prefer latest MCP version" (PR #11827), which made the client attempt the 2026-07-28 protocol via server/discover before falling back to a legacy handshake. Two regressions followed: stdio extensions whose servers support only protocol versions up to 2025-11-25 failed to start, and streamable_http extensions against servers that keep their notification channel open but silent failed with an "empty sse stream" error. v1.50.1, released 2026-09-14, reverted the change under the heading "Roll back MCP default version selection update."

server release

Playwright MCP 0.0.81 makes its file access check follow symlinks so a workspace symlink can no longer reach files outside the allowed roots

Microsoft released playwright-mcp v0.0.81 on 2026-09-14. Its release notes state that the file access check now follows symlinks, so a symlink inside the workspace can no longer be used to read or write files outside the allowed roots. The same release adds WebMCP tool support (browser_webmcp_list, browser_webmcp_call), a --profile-dir-name option for selecting a Chrome profile in extension mode, and an idle timeout that closes headless browsers after an hour without tool calls. No GitHub security advisory covers the symlink fix; it shipped as a release-notes bug fix.

All news →

Every story carries primary sources and a verification date.

48 Verified on 2026-07-28 748 Awaiting verification 76 First-party servers 5 Spec revisions tracked 796 Entities cataloged

More news

security

IBM's ContextForge MCP Gateway draws six CVE records in ten days, one critical default-credentials bug already patched and one SSRF report closed by documentation alone

IBM's own CNA published five CVE records against ContextForge MCP Gateway between 2026-09-04 and 2026-09-10, and GitHub's CNA published a sixth against the same repository on 2026-09-14. The critical record, CVE-2026-78573, is a hardcoded "changeme" default across three password settings; IBM's support page names v1.0.10, not the v1.0.8 the CVE text's own truncated version range would imply, as the actual fix, released 2026-09-07. Four more IBM-track records cover SSRF and credential-handling bugs with shipped fixes, except CVE-2026-18489, which IBM's text says was closed by a documentation change with no code fix. GitHub's separate record covers a DNS TOCTOU SSRF bypass fixed three months before it was published.

security

Langflow discloses five CVEs against its MCP Tools component, including a critical unauthenticated code execution bug, all already fixed

IBM's CNA, which now issues security records for Langflow, published five CVE records between 2026-09-04 and 2026-09-14 against Langflow's MCP Tools component. The worst, CVE-2026-85025 (critical, 9.8), let an unauthenticated attacker execute code and tamper with chat sessions through publicly shared MCP project endpoints. Two high-severity records (8.8 each) cover separate paths to arbitrary command execution through an MCP Tools stdio subprocess configuration. All three were fixed in Langflow OSS v1.11.6, released 2026-09-01, before any of them were published. Two medium records, one narrower information-disclosure bug and one older header-spoofing bypass fixed a release earlier, round out the batch.

governance

SEP-2640 merges as Final: Agent Skills get a spec-level home over MCP Resources, the first proposal accepted since the 2026-07-28 release

On 2026-09-13 the MCP maintainers merged SEP-2640, the Skills Extension, with status Final on the Extensions Track. It defines how a server exposes Agent Skills as MCP resources under a skill:// URI convention, two required methods, skills/list and skills/get, and an optional resources/directory/read, under the extension identifier io.modelcontextprotocol/skills. It is the first SEP merged since the 2026-07-28 release, and because it is an extension the draft changelog for the next dated revision stays empty. MCP Inspector had shipped support for it four days earlier, in 2.6.0.

client release

Claude Managed Agents add an auto permission policy for agent and MCP tool calls, dated September 10, 2026

Claude's platform release notes, dated September 10, 2026, added an auto permission policy to Claude Managed Agents: the server evaluates each agent or MCP tool call and runs it, denies it, or pauses for approval. The agent.tool_use and agent.mcp_tool_use events now report that outcome in an evaluation field alongside evaluated_permission.

client release

OpenAI releases the Agents API in public beta on September 10, 2026, with built-in MCP server connections

OpenAI's API changelog recorded the Agents API entering public beta on September 10, 2026, describing a managed Codex harness that lets a developer "connect your own tools and MCP servers." The Agents API overview confirms agents can operate in a sandbox that connects to MCP servers, and the linked MCP connections guide documents three ways to attach a server: over HTTP hosted by OpenAI, over HTTP from the developer's own environment, or over stdio inside that environment. This is a separate product surface from the Agents SDK, which OpenAI added MCP support to in March 2025.

server release

rmcp 3.3.0 adds enterprise token exchanges and an initialize negotiation hook

The official Rust SDK released rmcp 3.3.0 on 2026-09-10, adding ServerHandler::negotiate_initialize and, under auth, enterprise refresh-token and ID-JAG token exchanges. The macros crate now rejects an empty tool_router, and a fix saturates SSE reconnect backoff to avoid an overflow panic.

The MCP 500 Full list →

# Server Index Downloads/wk Stars
1 Playwright MCP 85.06 4.6M 37k
2 Chrome DevTools MCP 82.60 1.5M 52k
3 Context7 81.78 1.1M 62k
4 Firebase MCP Server 80.31 2.2M 4.5k
5 MongoDB MCP Server 79.54 56k 1.1k

Start here

Verified on 2026-07-28

Ash AI MCP Server

Current Spec Verified First-party

MCP server · by ash-project · verified

AshAi.Mcp.Server is a library module the ash_ai package (hex:ash_ai) ships for the Elixir Ash Framework; operators mount it themselves via forward "/mcp", AshAi.Mcp.Router, tools: [...], otp_app: :my_app in their own Phoenix router, or as a plain Plug in any Plug-based application, so there is no single hosted Ash AI MCP Server to point at, only per-deployment mounts of the same library code. It runs over the MCP Streamable HTTP transport only; its SSE support is an in-band response-encoding option within Streamable HTTP requests, not the deprecated standalone HTTP+SSE transport, which the source explicitly disclaims. Authentication defaults to none: the README's authentication section documents two opt-in options, "OAuth 2.1 - the right choice for 'remote' MCP clients that self-register and run the standard OAuth flow" via ash_authentication_oauth2_server, and "API keys - the quickest way to value when your clients are configured by hand with a static credential" via AshAuthentication.Strategy.ApiKey.Plug, and the router forwards without either configured by default. Both the shipped source (lib/ash_ai/mcp/server.ex at v1.0.3) and the live hexdocs page for the same module state, under "Protocol versions," that "the server supports multiple protocol revisions in tandem on the same endpoint": 2026-07-28, 2025-06-18, and 2025-03-26, grounding spec_status as current. The README's separate "Production MCP Server" section still states "The protocol version we implement is 2025-03-26," language the shipped v1.0.3 source and hexdocs supersede.

Cloudflare MCP servers

Current Spec Verified First-party

MCP server · by cloudflare · verified

Cloudflare's product-specific MCP servers, sixteen Cloudflare-hosted endpoints on mcp.cloudflare.com subdomains. Each request runs on a fresh stateless server with no protocol session. Historical /sse URLs survive as aliases to the same Streamable HTTP handler but no longer serve the deprecated HTTP+SSE transport. Authorization is OAuth with scope selection; the docs endpoint answers unauthenticated. A 2026-08-07 probe of docs.mcp.cloudflare.com/mcp answered server/discover at 2026-07-28 over streamable-http. Endpoint probe confirmed support for 2026-07-28 via server/discover.

DBHub

Current Spec Verified First-party

MCP server · by bytebase · verified

Bytebase's universal database MCP server for PostgreSQL, MySQL, SQL Server, MariaDB, and SQLite, run locally via npx with a connection DSN. Supports a read-only mode and a bearer-token-authenticated HTTP transport. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @bytebase/dbhub 1.2.0 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.

homebutler

Current Spec Verified First-party

MCP server · by github-higangssh · verified

Homelab management tool distributed as npm:homebutler, a thin installer (bin homebutler-mcp) that downloads a compiled Go binary rather than shipping an SDK-based JavaScript server; the package declares no @modelcontextprotocol/sdk dependency. It runs the MCP interface over stdio only, with no network port opened and no auth token, since the README states only the parent AI process can reach it over stdin/stdout. Vendor docs (docs/mcp-server.md, "Protocol versions") state that homebutler implements MCP revisions 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05, which grounds spec_status as current with legacy support recorded for the four earlier revisions via matching support atoms.

MCP Inspector

Current Spec Verified

MCP client · by modelcontextprotocol · verified

The protocol project's reference tool for inspecting MCP servers, shipped as the @modelcontextprotocol/inspector npm package with web, CLI, and TUI frontends. The v2 line targets the modern protocol: the README documents the "modern (2026-07-28) protocol era" including MRTR replacing server-to-client elicitation, 2.1.0 shipped SEP-2243 header mirroring, and 2.2.0 runs on the stable TypeScript SDK 2.0.0.

Notion MCP

Current Spec Verified First-party

MCP server · by notion · verified

Notion's hosted MCP server. The developer changelog entry of 2026-08-03 states the Streamable HTTP endpoint at mcp.notion.com/mcp supports protocol version 2026-07-28, and that clients negotiating the earlier 2025-era protocol on the same endpoint continue to work unchanged. Authorization is OAuth 2.0 with mandatory S256 PKCE; Client ID Metadata Documents are supported as an alternative to Dynamic Client Registration.

Verified on an earlier revision

Adeu

Earlier Revision First-party

MCP server · by dealfluence · verified

DOCX redlining engine exposed as an MCP server, in Python and Node.js implementations: translates .docx files to a Markdown representation for LLM editing and applies edits back as native Word Track Changes. npm's latest @adeu/mcp-server is 2.4.0 (2026-08-13); the registry record trails at 1.7.1 (2026-05-16). No surface names a supported MCP revision. Resolved from the published package: @adeu/mcp-server 2.4.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Appium MCP

Earlier Revision First-party

MCP server · by appium · verified

The Appium project's own MCP server for driving mobile automation sessions on iOS and Android, including test creation tools. Published from the appium GitHub organization; npm and the registry agree on 1.92.2 (2026-08-13). No project surface names a supported MCP revision. Resolved from the published package: appium-mcp 1.92.4 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Bitbucket MCP (MatanYemini)

Earlier Revision Community

MCP server · by github-matanyemini · verified

Community MCP server for the Bitbucket Cloud and Server APIs by an individual developer; not published by Atlassian. npm's latest is 5.0.6 (2025-12-22), one patch ahead of the registry record's 5.0.5. No surface names a supported MCP revision. Resolved from the published package: bitbucket-mcp 5.0.6 depends on @modelcontextprotocol/sdk@1.1.1, whose artifact implements 2024-11-05. This records what the artifact implements, not what a deployment negotiates.

Browser Use MCP Server

Earlier Revision First-party

MCP server · by browser-use · verified

MCP server shipped inside the browser-use Python library for driving a real Chrome browser, run locally over stdio. The registry-published package launches the minimal --cli-mcp variant (browser_exec, browser_screenshot); the richer tool set documented on docs.browser-use.com runs behind the --mcp flag. No vendor documentation surface names a supported MCP revision. Resolved from the published package: browser-use 0.13.8 depends on mcp@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

BrowserStack MCP Server

Earlier Revision First-party

MCP server · by browserstack · verified

BrowserStack's official MCP server for its testing platform, run locally from the @browserstack/mcp-server npm package with BrowserStack account credentials. No vendor documentation surface names a supported MCP revision. npm's latest (1.2.36, 2026-08-11) is well ahead of the registry record (1.0.0, 2025-10-28). Resolved from the published package: @browserstack/mcp-server 1.2.36 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

claude-flow

Earlier Revision Community

MCP server · by github-ruvnet · verified

Community agent-orchestration harness by the developer rUv, exposing MCP tools for multi-agent workflows. Renamed to "ruflo" (repo ruvnet/ruflo, npm ruflo); the registry record still uses the claude-flow name at a September 2025 alpha. A critical unauthenticated RCE (CVE-2026-59726) was patched in ruflo 3.16.3. Checked 2026-08-25: the v3 MCP package README in the ruflo repository states "MCP 2025-11-25 Compliant - Standalone Model Context Protocol server implementation with full Resources, Prompts, and Tasks support". Both npm packages claude-flow and ruflo ship 3.38.20 from the same commit; releases 3.38.18 and 3.38.19 (2026-08-22) name MCP HTTP transport fixes.

Desktop Commander

Earlier Revision First-party

MCP server · by desktop-commander · verified

MCP server giving an assistant terminal command execution, process management, and filesystem operations on the local machine, run over stdio via npx @wonderwhy-er/desktop-commander. Telemetry is on by default with a documented opt-out. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @wonderwhy-er/desktop-commander 0.2.47 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Firebase MCP Server

Earlier Revision First-party

MCP server · by google · verified

Firebase's MCP server ships inside the Firebase CLI (firebase-tools) and runs locally via npx firebase-tools mcp, exposing tools across Firestore, Auth, Storage, Crashlytics, Functions, and other Firebase products using the developer's existing CLI credentials. No vendor documentation surface names a supported MCP revision. Resolved from the published package: firebase-tools 15.28.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Firecrawl MCP Server

Earlier Revision First-party

MCP server · by firecrawl · verified

Firecrawl's official MCP server for web search, scraping, and structured extraction, hosted at mcp.firecrawl.dev/v2/mcp (keyless free tier for a tool subset, bearer API key or OAuth for the rest) and installable locally via npm. A 2026-08-07 probe of the hosted endpoint negotiated 2025-11-25 and rejected 2026-07-28, naming 2025-11-25 as its newest supported revision. Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.

Framelink MCP for Figma

Earlier Revision Community

MCP server · by framelink · verified

Community MCP server (Framelink, by Graham Lipsman) that fetches Figma file data through Figma's REST API and simplifies it for coding agents to implement designs; requires a Figma personal access token and runs locally over stdio. Not published by Figma. No vendor documentation surface names a supported MCP revision. Resolved from the published package: figma-developer-mcp 0.13.2 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

GitLab MCP Server

Earlier Revision First-party

MCP server · by gitlab · verified

GitLab's official MCP server, built into the GitLab application at /api/v4/mcp. GitLab docs state support for the 2025-03-26 and 2025-06-18 MCP protocol specifications was added in GitLab 18.7. Beta on all tiers of GitLab.com, Self-Managed, and Dedicated. No GitLab surface names 2026-07-28 support; a probe on 2026-08-14 answered with an OAuth challenge, so revision behavior is not observable without credentials.

gitlab-mcp

Earlier Revision Community

MCP server · by zereight · verified

Community MCP server (by independent developer zereight) fronting the GitLab API: projects, merge requests, issues, pipelines, wiki, releases. Requires a GitLab personal access token by default, with OAuth modes for self-hosted remote deployments. Not published by GitLab, which operates its own official MCP server. No surface names a supported MCP revision. Resolved from the published package: @zereight/mcp-gitlab 2.1.49 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Hostinger API MCP Server

Earlier Revision First-party

MCP server · by hostinger · verified

Hostinger's first-party MCP server for the Hostinger API, run locally from npm or used via the hosted remote at mcp.hostinger.com, which requires OAuth. No vendor surface names a supported MCP revision; a 2026-08-14 probe of the remote returned an OAuth challenge, so revision behavior is not observable without credentials. Resolved from the published package: hostinger-api-mcp 1.45.3 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

ikeytz - Schlüsseldienst Ludwigsburg

Earlier Revision First-party

MCP server · by ikeytz · verified

Fronts the operator's own locksmith business (ikeytz - Schlüsseldienst Ludwigsburg) as a remote streamable-http MCP server; no repository or GitHub presence was found for the operator. Probed 2026-09-15, a legacy initialize request with protocolVersion 2025-11-25 returned HTTP 200 with a matching negotiated protocolVersion, capabilities for tools, resources and prompts (listChanged false), and serverInfo name "ikeytz" version "1.0.0". The same session's POST of server/discover under Mcp-Protocol-Version 2026-07-28 returned HTTP 200 but a JSON-RPC error, method not found, so support for the current spec revision is not established. The server's own instructions string states that the published npm package @ikeytz/mcp is a command-line client rather than this HTTP server, so no package coordinate is recorded here. Authority rests on the domain-verified com.ikeytz registry namespace and a matching npm package author, tying the same registered operator to the business the server fronts.

Mailtrap MCP Server

Earlier Revision First-party

MCP server · by mailtrap · verified

Mailtrap's official MCP server for its email delivery and testing platform, run locally from the mcp-mailtrap npm package with a MAILTRAP_API_TOKEN. npm's latest is 0.7.0 (2026-08-04); the registry record trails at 0.6.0. No vendor surface names a supported MCP revision. Resolved from the published package: mcp-mailtrap 0.8.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

mobile-mcp

Earlier Revision First-party

MCP server · by mobile-next · verified

Mobile Next's MCP server for iOS and Android automation across simulators, emulators, and real devices, run locally over stdio. No vendor documentation surface names a supported MCP revision. Resolved from the published package: @mobilenext/mobile-mcp 1.0.2 depends on @modelcontextprotocol/sdk@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

MongoDB MCP Server

Earlier Revision First-party

MCP server · by mongodb · verified

MongoDB's first-party MCP server for MongoDB databases and Atlas clusters, run locally via npx mongodb-mcp-server or Docker. Version 2.0.0 (2026-08-04) removed session state and requires explicit connection ids. No vendor documentation surface names a supported MCP revision. Resolved from the published package: mongodb-mcp-server 2.1.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Power BI Modeling MCP Server

Earlier Revision First-party

MCP server · by microsoft · verified

Distributed as npm:@microsoft/powerbi-modeling-mcp. Checked 2026-08-25: the README states "This MCP Server supports the Elicitation MCP protocol", linking the 2025-06-18 specification's elicitation section; no later revision is named anywhere in the repository. Public Preview with no GitHub releases; npm 0.5.0-beta.12 ships platform-specific binaries with no SDK runtime dependency. Authority: the repository is in the microsoft GitHub organization, the package under the @microsoft npm scope, and the registry namespace com.microsoft is DNS-verified by the official registry.

PraisonAI

Earlier Revision

MCP client · by github-mervinpraison · verified

Python agent framework whose praisonaiagents[mcp] MCP() class connects agents to external MCP servers over stdio, Streamable HTTP, WebSocket, or legacy SSE (auto-detected from the server URL or scheme). The client docs carry an explicit "Protocol Revision: 2025-11-25" statement; that revision is recorded as the latest verified for the client role only, not for PraisonAI's separate praisonai-mcp server package. Fails closed since PR #4423 (merged 2026-08-26): MCP() now raises when a stdio server times out, errors on init, or advertises zero tools.

Sentry MCP Server

Earlier Revision First-party

MCP server · by sentry · verified

Sentry's first-party MCP server for error monitoring and issue data, hosted at mcp.sentry.dev with OAuth, plus a work-in-progress local stdio transport using a Sentry user auth token. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no vendor documentation surface names a supported MCP revision. Resolved from the published package: @sentry/mcp-server 0.37.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Snyk MCP Server

Earlier Revision First-party

MCP server · by snyk · verified

Snyk's MCP server ships inside the Snyk CLI and runs via the snyk mcp command, exposing Snyk security scans (open source, code, IaC, container, SBOM, secrets) to agentic tools. Checked 2026-08-25: the studio-mcp repository ships MCP specification conformance tests stating they "verify compliance with the Model Context Protocol specification" for versions 2025-11-25 and 2025-06-18 (internal/mcp/mcp_spec_conformance_test.go). The server is a Go binary inside the Snyk CLI, invoked as snyk mcp and built on mark3labs/mcp-go v0.31.0; the npm snyk package itself declares no MCP SDK dependency.

Splunk MCP Server

Earlier Revision First-party

MCP server · by splunk · verified

Splunk publishes the Splunk MCP Server app (Splunkbase uid 7931, appid Splunk_MCP_Server) as an installable Splunkbase package for a customer's own Splunk Search Head or Search Head Cluster; there is no Splunk-hosted public endpoint and no linked source repository on the advisory, the CVE record, or the Splunkbase listing. The app's 1.3.1 release entry (published 2026-08-03 per the Splunkbase release API) states "Updated MCP protocol version to 2025-11-25," a vendor release note naming a revision, so spec_status is legacy with latest_spec 2025-11-25 and a matching support edge; no fetched page ties a revision to the current 2.0.0 release, and no page names 2026-07-28.

Supabase MCP Server

Earlier Revision First-party

MCP server · by supabase · verified

Supabase's first-party MCP server, hosted at mcp.supabase.com/mcp with OAuth dynamic client registration; feature-group, project-scoping, and read-only flags are documented. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no vendor documentation surface names a supported MCP revision. Resolved from the published package: @supabase/mcp-server-supabase 0.10.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

Telnyx MCP Server

Earlier Revision First-party

MCP server · by telnyx · verified

Telnyx's MCP server (npm telnyx-mcp) fronts the Telnyx communications API, run locally via npx with Telnyx API credentials. It ships from the telnyx-node monorepo; the ranked registry row points at the SDK package (npm telnyx), not this server. No surface names a supported MCP revision. Resolved from the published package: telnyx-mcp 7.16.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

WebCrypt MCP Server

Earlier Revision First-party

MCP server · by github-putervision · verified

A self-contained cryptography toolkit and MCP server offering AES-256-GCM, RSA-4096, ECDH, ECDSA/HMAC and post-quantum Kyber/Dilithium operations, all executed locally through the native Web Crypto API with zero runtime dependencies. It is distributed as the npm package webcrypt, invoked over stdio via npx, and documents no MCP-level authentication since every operation runs in-process with no network calls. The server implements its own hand-rolled JSON-RPC 2.0 stdio framing rather than wrapping an SDK. Its own docs/ARCHITECTURE.md states that WebCrypt "introduces a zero-dependency Model Context Protocol (MCP) stdio server conforming to JSON-RPC 2.0 and specification 2024-11-05," a vendor-authored statement naming an early spec revision, so spec_status is legacy with latest_spec 2024-11-05, several revisions behind the current 2026-07-28.

Spec support unverified

Agent Swarm

Spec Support Unverified First-party

MCP server · by desplega-ai · verified

First-party Desplega Labs server for its own agent-swarm product, distributed as npm:@desplega.ai/agent-swarm and self-hosted: the registry declares the remote as https://{swarm_host}/mcp, where the operator supplies the host of their own instance, so there is no vendor endpoint to probe. Auth is a bearer API key plus an X-Agent-ID header naming a registered agent. No documentation names a supported MCP specification revision. Two protocol versions appear in source, both as defaults in code rather than support statements: an outbound MCP client wrapper defaults to 2025-03-26, and a dashboard-generated debug snippet hardcodes 2025-06-18. The declared streamable-http transport is a transport, not a revision.

AgentPhone

Spec Support Unverified First-party

MCP server · by agentphone-ai · verified

First-party AgentPhone server for its own telephony API, distributed as npm:agentphone-mcp and hosted by the vendor at https://mcp.agentphone.ai/mcp. Probed 2026-09-03: both server/discover at 2026-07-28 and a legacy initialize returned HTTP 401 {"error":"Missing Authorization header"}, which grounds the endpoint as live and bearer-gated but negotiates no revision, so spec support stays unknown. No documentation names a revision; the package depends on @modelcontextprotocol/sdk ^1.26.0. Identity drift worth noting: the registry name's trailing segment is "agentphone" while both the repository and the npm package are "agentphone-mcp", and the registry record pins 0.6.0 while npm ships 0.7.0.

Apache SkyWalking MCP

Spec Support Unverified First-party

MCP server · by apache · verified

The Apache SkyWalking project's own MCP server, a Go binary named swmcp that queries a SkyWalking OAP backend for traces, logs, metrics, topology and alarms. It serves stdio, streamable HTTP and legacy SSE, and authenticates to OAP rather than to its own callers. The 0.3.0 changelog entry on master says the server migrated to the official Go SDK and added support for the 2026-07-28 revision, but no 0.3.0 release is tagged: the newest tag is v0.2.0, so revision support is not yet recorded as shipped.

argocd-mcp

Spec Support Unverified Community

MCP server · by argoproj-labs · verified

MCP server for Argo CD, distributed as npm:argocd-mcp and run over stdio, HTTP stream, or SSE; it is self-hosted only, with no vendor-managed remote endpoint. It lives in argoproj-labs, which the Argo Project's own governance README describes as "a separate GitHub org that we setup for community contributions related to the Argoproj ecosystem," administered by each project's owners and, per the labs org's own profile, "not part of the CNCF Argo umbrella projects." Argo CD's own repository and docs do not link the server. Its creators are named engineers from Akuity, a company founded by Argo CD's co-founders, but Akuity is not the vendor of Argo CD, which is a CNCF project. Authority is therefore community: verified maintainers, outside the project that owns the fronted service. No documentation names a supported MCP specification revision; the README's own curl example and a security-advisory proof of concept both hard-code protocolVersion 2024-11-05 in sample JSON-RPC payloads, which is example boilerplate rather than a stated capability. Auth is dual and asymmetric: ARGOCD_API_TOKEN authenticates the server outbound to Argo CD, while MCP_AUTH_TOKEN, added in v0.9.0, is an optional inbound bearer token required only once the listener binds beyond loopback; recorded here as api_key for the closest enum fit, since the enum has no dual-credential option. CVE-2026-82456 (CVSS 3.1 and 4.0 both 10.0, record published 2026-08-29) affected v0.8.0's unauthenticated, all-interfaces HTTP bind and is fixed in v0.9.0, released 2026-08-11, advisory GHSA-rp45-5x3v-48mr.

AWS Labs postgres MCP Server

Spec Support Unverified First-party

MCP server · by aws · verified

AWS Labs' own MCP server for Amazon Aurora and RDS Postgres, distributed from the awslabs/mcp monorepo at src/postgres-mcp-server. Authority is first-party on two AWS-controlled surfaces: GitHub reports the awslabs organization as verified ("is_verified": true, name "Amazon Web Services - Labs"), and the monorepo's own README describes the collection as "Open source MCP servers for AWS... A suite of specialized MCP servers that help you get the most out of AWS, wherever you use MCP." The server runs over stdio only, per the monorepo root README's transport statement ("The MCP servers in this repository are designed to support stdio only") and confirmed in source, where server.py calls mcp.run() with no transport argument. The auth enum has no clean match for this server's credential model: it authenticates to AWS through the AWS_PROFILE/AWS_REGION credential chain, requires an RDS Data API resource ARN carrying rds-data:ExecuteStatement permission, and separately authenticates to Postgres via IAM or username/password credentials held in AWS Secrets Manager and referenced by --secretManagerARN; api_key is recorded here for lack of a better enum value rather than as a literal description. The server is read-only by default; --allow_write_query disables that enforcement, and the README's own security section calls the mechanism "a best-effort, defense-in-depth mechanism, not a security boundary." Neither the README nor the docs site enumerates a tool list; tools_count 7 and the key_tools below were recovered by reading the source directly at https://raw.githubusercontent.com/awslabs/mcp/main/src/postgres-mcp-server/awslabs/postgres_mcp_server/server.py.

ChatGPT

Spec Support Unverified

MCP client · by openai · verified

OpenAI's assistant supports MCP through connectors: deep research and company knowledge require read-only search and fetch tools, while developer mode unlocks custom servers with full tool access. MCP also reaches the Responses API and the prompts dashboard. OpenAI's docs use the SSE streaming interface and link the 2025-11-25 authorization specification, but name no full MCP spec revision, so revision support is unverified.

Chrome DevTools MCP

Spec Support Unverified First-party

MCP server · by google · verified

Google's Chrome DevTools MCP server: lets a coding agent control and inspect a live Chrome browser with DevTools-grade debugging, performance tracing, and Puppeteer-based automation, run locally over stdio via npx chrome-devtools-mcp. Hand check 2026-08-25: no MCP revision statement in README, CHANGELOG or docs; @modelcontextprotocol/sdk 1.30.0 is a devDependency of a bundled build, so the SDK chain cannot ground a revision. v1.8.0 released 2026-08-25.

Claude Code

Spec Support Unverified

MCP client · by anthropic · verified

Anthropic's terminal and IDE coding agent. MCP servers connect over streamable HTTP (recommended; type http, with streamable-http accepted as an alias), stdio, deprecated SSE, and WebSocket for server-push use cases. Supports roots/list with change notifications, list_changed refresh for tools, prompts, and resources, and OAuth on HTTP servers. No Anthropic surface names a supported MCP spec revision for the client as a whole, so revision support is unverified; the connector docs name the 2025-03-26, 2025-06-18, and 2025-11-25 authorization specifications as supported.

Claude Desktop

Spec Support Unverified

MCP client · by anthropic · verified

Anthropic's desktop client and the first shipping MCP client: local MCP server support launched with the protocol in November 2024, and remote connectors run over streamable HTTP (legacy HTTP+SSE deprecated). Claude's connector docs ground tools, prompts, and resources with text, image, and binary content; resource subscriptions and sampling are not yet supported. Authorization specs 2025-03-26, 2025-06-18, and 2025-11-25 are supported with DCR. No full MCP spec revision is named, so revision support stays unverified.

CloudBase MCP

Spec Support Unverified First-party

MCP server · by tencentcloudbase · verified

First-party Tencent CloudBase server, distributed as npm:@cloudbase/cloudbase-mcp and also offered as a Tencent-hosted endpoint at tcb-api.cloud.tencent.com/mcp/v1, which requires an env_id parameter plus Tencent Cloud API key headers and so cannot be probed anonymously. Probed 2026-09-03: a GET answered HTTP 405 with a JSON-RPC error body and an uncredentialed server/discover answered HTTP 403 "Forbidden: Missing credentials", which grounds the endpoint as live and credential-gated without negotiating a revision. No documentation names a supported MCP specification revision; the package pins @modelcontextprotocol/sdk 1.30.0, which records what the artifact bundles rather than what the hosted deployment negotiates.

Concord MCP

Spec Support Unverified First-party

MCP server · by github-get-concord-ai · verified

Local-first coordination server distributed as npm:@concord-ai/concord-mcp, giving coding agents shared work-state across harnesses (Claude Code, Codex, Cursor, Gemini CLI, Grok Build) through five tools backed by a local SQLite store. It runs over stdio only, installed globally via npm and registered into each client's own MCP config by a `concord setup` command; no auth token or OAuth flow gates the MCP interface itself. The vendor's own site, getconcord.ai, links directly to this repository and instructs installing this exact package, establishing Concord AI as the vendor whose product the server fronts. No documentation names a supported MCP specification revision, so spec_status is unknown.

Contentful MCP Server

Spec Support Unverified First-party

MCP server · by contentful · verified

Authority rests on the server living in the verified contentful GitHub organization, which GitHub's API reports with "is_verified": true, and on its publication under the @contentful npm scope; package.json for both workspace packages lists author "Contentful GmbH". The published package, @contentful/mcp-server, depends on a shared library, @contentful/mcp-tools, published from the same monorepo and versioned separately. No fetched page names an MCP protocol revision (README, CHANGELOG.md, and AGENTS.md were all checked); the @modelcontextprotocol/sdk ^1.26.0 dependency is a version range, not evidence of a specific revision, so spec_status is unknown. Vendor documentation on contentful.com was not verified this session: the domain returned HTTP 429 on every attempt, so authority and entity facts here rest on the GitHub org record, the README, package.json, and the advisory API rather than any contentful.com page.

Coroot

Spec Support Unverified First-party

MCP server · by coroot · verified

Coroot's MCP surface is a built-in feature of the Coroot product itself, not a separate package; it is served at /mcp on a customer's own Coroot instance, so no public remote_url applies. Coroot's docs describe the exposed surface (application topology, health signals, distributed traces, raw telemetry) and list 19 distinct tools, 2 marked Enterprise-Edition-only, without naming each tool individually on the fetched page, so key_tools is left empty here rather than guessed. Authentication is OAuth 2.0 with dynamic client registration (/oauth/register, /oauth/authorize, /oauth/token, /oauth/revoke, /.well-known/oauth-authorization-server), confirmed both in the docs ("Each user signs in with their own Coroot account on first connect, and the agent runs with that user's RBAC permissions") and in source. No fetched page names an MCP protocol revision; the go.mod dependency on github.com/mark3labs/mcp-go v0.45.0 is an SDK version, not evidence of revision support. CVE-2026-79786 (VulnCheck CNA, published 2026-08-25, CVSS 3.1 7.1 high) documents that the MCP OAuth registration endpoint validates redirect_uris with Go's url.Parse only, with no scheme or host allowlist, enabling open-redirect consent-phishing against authenticated users; affected versions 1.20.2 through 1.24.5. As of 2026-09-15 there is still no fix: api/mcp_oauth.go is unchanged at release v1.26.1 (published 2026-09-14) and on the current main branch (pushed 2026-09-15), and the file's last commit remains the 2026-05-05 change that introduced the MCP server. A proposed fix, PR #960, opened 2026-08-13 to add a scheme/host allowlist, was closed without merging. The public tracking issue, coroot/coroot#929, opened 2026-07-01, remains open with no maintainer fix committed.

Decionis MCP

Spec Support Unverified First-party

MCP server · by decionis · verified

Decionis' own MCP server, distributed as npm:@decionis/mcp and documented on decionis.com/docs/protocol-mcp as "a local stdio MCP server that lets Claude Code, Codex, Cursor, and any MCP client... asks permission before it executes," which grounds first-party authority on a domain-verified vendor surface. The registry record's repository field cites https://github.com/decionis/agent-safe-pipeline, a real and active Decionis repository that does not contain this server's code anywhere in its tree; the repository that actually documents @decionis/mcp is a separate one, https://github.com/decionis/mcp, whose own README states the published npm package's source of truth lives in a private Decionis platform monorepo and that this public repo exists only to host setup guides, samples, and issue reports. repo_url below points at the latter, since it is where the server is actually documented. Probed 2026-09-15: a POST server/discover at protocol revision 2026-07-28 and a legacy POST initialize at 2025-11-25 against the documented remote endpoint both returned HTTP 401 with WWW-Authenticate: Bearer resource_metadata pointing at the endpoint's own oauth-protected-resource document, error invalid_token, and a JSON-RPC {-32001, "Unauthorized MCP request"} body. A separate plain GET against the same endpoint, sent without a JSON-RPC body, returned a self-descriptive JSON document advertising supported_protocol_versions up through 2025-11-25 at https://protocol.decionis.com/mcp; that document is advertised metadata, not a negotiated session, so spec_status stays unknown.

Doc Bridge

Spec Support Unverified First-party

MCP server · by github-agentskit-io · verified

Resolves documentation ownership, edit roots and human handoffs before an agent edits code, distributed as npm:@agentskit/doc-bridge and launched via npx ak-docs mcp over stdio. First-party rests on four agreeing surfaces: the AgentsKit-io GitHub organization, the @agentskit npm scope, the doc-bridge.agentskit.io product page (which links only to this repository) and the parent agentskit.io site, which lists Doc Bridge among its own products. The dedicated docs/mcp.md page enumerates eight tools, while the README separately states a packaged bundle advertises fourteen; the extra six are not itemized anywhere fetched. The official MCP Registry record is pinned at version 1.2.6 from 2026-08-03, roughly forty releases behind npm's 1.7.45 as of 2026-08-29, and GitHub's own release feed stopped at v1.4.3. No file fetched, including the README, CHANGELOG and docs pages, names an MCP protocol revision, so spec support is recorded as unknown.

Dynatrace-mcp

Spec Support Unverified First-party

MCP server · by github-dynatrace-oss · verified

Distributed as npm:@dynatrace-oss/dynatrace-mcp-server. DEPRECATED by the vendor, recorded 2026-08-25: the README states "This repository is deprecated. Version 2.1.2 was the final release" and directs users to Dynatrace-for-ai with dtctl or the Dynatrace Remote MCP Server. v2.1.2 published 2026-07-20. Authority: the dynatrace-oss organization describes itself as "Open Source projects maintained by Dynatrace".

GitHub Copilot CLI

Spec Support Unverified

MCP client · by github · verified

GitHub's terminal coding agent. MCP servers "give Copilot access to different data sources and tools", with the GitHub MCP server as the documented built-in example. Enterprise management is partial: the docs state Copilot CLI cannot yet enforce the "MCP servers in Copilot" and "MCP Registry URL" organization policies. Since 2026-08-12 it also installs Agent Plugins, whose mcp.json files carry MCP server configurations. No MCP spec revision is named.

gk-cli

Spec Support Unverified First-party

MCP server · by gitkraken · verified

Distributed as npm:@gitkraken/gk. Authority resolved 2026-08-25: the repository is owned by the gitkraken GitHub organization and the npm package is maintained by axosoft (dev.subs@gitkraken.com); the MCP server is the CLI's own gk mcp subcommand wrapping git, GitHub, Jira actions and GitKraken APIs. No MCP revision statement in the README or the GitKraken help page for the MCP server (checked 2026-08-25).

Google Drive MCP

Spec Support Unverified Community

MCP server · by piotr-agier · verified

Community server for Google Workspace, distributed as npm:@piotr-agier/google-drive-mcp and self-hosted by the operator. The user supplies their own Google Cloud OAuth client, so the server holds no vendor credentials of its own. No documentation names a dated MCP specification revision: the deployment guide links the draft authorization specification for its team mode, which is the draft rather than a released revision, and the package depends on @modelcontextprotocol/sdk ^1.24.0, an SDK range. Published by an individual GitHub user with no Google affiliation, so authority is community despite the product names in the title.

Goose

Spec Support Unverified

MCP client · by aaif · verified

General-purpose AI agent published by the Agentic AI Foundation (AAIF), distributed as a native desktop app for macOS, Linux and Windows plus a Rust CLI, connecting to MCP extensions configured under extensions in ~/.config/goose/config.yaml. The ExtensionConfig enum in crates/goose/src/agents/extension.rs (v1.50.1) has Stdio and StreamableHttp (serde rename "streamable_http") variants; there is no Sse variant in this type, so SSE is not a configurable extension transport even though the docs site's navigation still lists an SSE entry. agent.rs line 102 sets "pub const MCP_PROTOCOL_VERSION: ProtocolVersion = ProtocolVersion::V_2025_11_25;", which after the v1.50.1 revert of the "prefer latest MCP version" change means the client's default lifecycle is the legacy initialize handshake at protocol version 2025-11-25 rather than probing server/discover for 2026-07-28. No vendor statement anywhere in the repository, release notes, or docs site names a protocol revision that Goose itself supports, so spec_status stays unknown.

GPT Researcher

Spec Support Unverified

MCP client · by github-assafelovic · verified

Open-source research agent that acts as an MCP client through an opt-in retriever mode. Servers are configured as Python dictionaries passed to the mcp_configs constructor argument, launched as a local stdio subprocess by default or connected remotely over WebSocket or streamable HTTP depending on the connection URL's scheme. The retriever activates when RETRIEVER=mcp is set and depends on mcp>=1.9.1 plus langchain-mcp-adapters>=0.1.0. Documentation and source describe only the tools feature: an LLM stage selects relevant tools across configured servers and calls them with generated arguments; no resources, prompts, sampling, elicitation, or roots support is documented. No project surface names an MCP specification revision.

Hermes Agent

Spec Support Unverified

MCP client · by nous-research · verified

AI agent published by Nous Research, distributed with an MCP client that ships as part of the standard install rather than an optional extra. Servers are added as entries under mcp_servers in ~/.hermes/config.yaml, each a command plus args for a local stdio launch or a URL for a remote connection, and separately through a curated, disabled-by-default catalog of 70 vendor-reviewed servers stored under optional-mcps/ in the repository. The client implements stdio, Streamable HTTP and SSE transports, and supports tools, resources, prompts, sampling and elicitation, the last two on by default per server; roots is not documented. A pyproject.toml code comment states that the pinned mcp==2.0.0 SDK dependency "implements MCP revision 2026-07-28," which is evidence about that SDK dependency rather than a Hermes-authored claim about the client's own supported revision, so spec status stays unknown.

Ignite UI Theming MCP Server

Spec Support Unverified First-party

MCP server · by github-igniteui · verified

Generates Sass palettes, typography, elevations and component themes for Infragistics' Ignite UI design system, distributed as the single npm package igniteui-theming, which bundles both the Sass library and the MCP server binary. The server runs over stdio only, launched with npx, and documents no authentication scheme. No README, changelog or registry manifest names a supported MCP specification revision; the resolved @modelcontextprotocol/sdk artifact implements up to protocol version 2025-11-25, but that is a fact about the underlying SDK build rather than a vendor statement about this server's own revision support, so spec_status stays unknown. The vendor's root README and its packages/mcp sub-package README disagree on tool count, eight versus twelve, a documentation drift rather than a protocol ambiguity.

IWE

Spec Support Unverified First-party

MCP server · by github-iwe-org · verified

Turns a directory of markdown files into a knowledge graph that an editor's LSP and an AI agent's MCP client both read from, exposing fourteen tools for finding, creating, updating, querying and refactoring notes. It is distributed as the npm installer package @iwe-org/mcp, wrapping a Rust binary also published to crates.io as iwe, and runs over stdio by default with an optional self-hosted streamable-http mode. The HTTP mode binds to localhost by default and documents no built-in authentication, leaving TLS and access control to an external reverse proxy. No README, docs page, changelog or server.json names a supported MCP specification revision, so spec_status is unknown; the rmcp v3 dependency in the server's Cargo.toml is an SDK range, not a revision statement.

mcp-omnisearch

Spec Support Unverified Community

MCP server · by github-spences10 · verified

Community search aggregator distributed as npm:mcp-omnisearch, unifying four tools over seven third-party providers: Tavily, Brave, Kagi, Exa, Linkup, Firecrawl and GitHub. It runs over stdio only, built on the third-party tmcp framework rather than @modelcontextprotocol/sdk. Callers supply a per-provider API key for whichever services they use; a provider without a key is skipped rather than causing an error. No documentation, dependency file, or registry record names a supported MCP specification revision, so spec_status is unknown.

mcp-ssh-manager

Spec Support Unverified Community

MCP server · by github-bvisible · verified

Community SSH management server distributed as npm:mcp-ssh-manager, giving Claude Code and OpenAI Codex 37 tools across command execution, file transfer, backups, database operations and health monitoring on operator-configured remote hosts. It runs over stdio only; MCP-level auth is none, while a separate per-server security mode (unrestricted, readonly, or restricted with allow/deny regex patterns) gates which commands each configured SSH connection accepts. No documentation or dependency file names a supported MCP specification revision; the package's @modelcontextprotocol/sdk ^1.30.0 dependency is a version range, not evidence of a specific revision, so spec_status is unknown.

MCPHub

Spec Support Unverified First-party

MCP server · by github-samanhappy · verified

MCPHub is a self-hosted MCP gateway and control plane: it both consumes upstream MCP servers, configured through data/mcp_settings.json, and exposes its own MCP endpoints to AI clients. This atom describes the exposed surface only. Authority is recorded as first_party under the self-owned-project precedent: the repository, the docs site (docs.mcphub.app), and the product site (mcphub.app, listed as the repo's own homepage) are all controlled by the same individual maintainer, so MCPHub fronts no separate third-party vendor relationship for this record to misrepresent. The README describes the exposed routes generically as supporting "SSE / Streamable HTTP / stdio" without pinning transport to a single value; transports here record both streamable-http and sse-legacy rather than asserting one exclusively. Auth on the exposed endpoints is layered: a built-in OAuth 2.0 authorization server ("Both client and server modes for secure authentication"), bearer keys, and JWT + bcrypt for local dashboard accounts, with MCP endpoints requiring authentication by default unless Bearer Authentication is explicitly disabled. oauth is recorded as the primary auth value because the exposed endpoints carry a real embedded OAuth 2.0 authorization server, not only static bearer keys. As a client, MCPHub can also connect to upstream MCP servers over stdio, SSE, or streamable HTTP; that consumer role is not otherwise assessed here.

Microsoft Advertising MCP Server

Spec Support Unverified First-party

MCP server · by microsoft · verified

Microsoft's own remote-only MCP server for Microsoft Advertising, documented on Microsoft Advertising's Learn setup guide (ms.date 2026-07-22); no repository is linked from any fetched Microsoft Advertising or Learn page. Authority is first-party on two Microsoft-controlled surfaces: the Learn guide instructs readers to "Register an OAuth client and connect Microsoft Advertising MCP Server to supported AI clients," and the documented endpoint itself resolves on Microsoft's own bingads.microsoft.com domain. Probed 2026-09-15: a POST server/discover at protocol revision 2026-07-28 and a legacy POST initialize at 2025-11-25 both returned HTTP 401 with a WWW-Authenticate: Bearer challenge naming the endpoint's own RFC 9728 protected-resource metadata document, and a direct GET of that document confirmed the resource URL, two authorization servers, and the required scopes. Neither probe negotiated a specification revision, so spec_status stays unknown. No fetched page names a transport; the setup guide's only signal is a VS Code mcp.json snippet setting "type" to "http," so transports is left empty even though the endpoint plainly accepts JSON-RPC over HTTPS.

PageSpeed Insights MCP

Spec Support Unverified Community

MCP server · by github-ruslanlap · verified

Wraps Google's PageSpeed Insights and Chrome UX Report APIs in six workflow tools for auditing web performance, replacing an earlier set of nineteen endpoint-shaped tools in a breaking rewrite shipped 2026-08-26. It is distributed as the npm package pagespeed-insights-mcp and runs over stdio only, launched via npx. Callers must supply their own Google API key through the required GOOGLE_API_KEY environment variable; the server has no MCP-level authentication of its own. No README, changelog or docs page names a supported MCP specification revision, so spec_status is unknown. The maintainer is an individual Ukraine-based developer publishing under a personal npm account, not Google, which sets the authority as community rather than first_party.

PDF Reader MCP

Spec Support Unverified First-party

MCP server · by github-sylphxai · verified

Distributed as npm:@sylphx/pdf-reader-mcp. Renamed, recorded 2026-08-25: version 5.0.0 is a hard cut to the @sylphx/citra npm package ("Current production identity: @sylphx/citra@5.0.0" per docs/migration.md), with the project stating a new MCP identity io.github.SylphxAI/citra; the registry_name here reflects the pre-rename record. Native Rust engine behind a thin Node launcher. No MCP revision statement in README or docs (checked 2026-08-25). Authority: Sylphx is a GitHub organization (sylphx.com) and the tool is its own product.

pinkpixel-dev-web-scout-mcp

Spec Support Unverified Community

MCP server · by github-pinkpixel-dev · verified

Listed with a remote endpoint. Publisher corrected 2026-08-25: the maintainer is the Pink Pixel organization (pinkpixel-dev on GitHub; npm maintainer sizzlebop, admin@pinkpixel.dev); Smithery is the hosting platform for the remote deployment, not the author. Authority community: the server fronts DuckDuckGo search, which the publisher does not operate. No MCP revision statement found (README, CHANGELOG, src/index.ts checked 2026-08-25); package.json declares @modelcontextprotocol/sdk ^1.18.1, not sufficient on its own.

Playwright MCP

Spec Support Unverified First-party

MCP server · by microsoft · verified

Microsoft's Playwright MCP server: browser automation through structured accessibility snapshots rather than screenshots, run locally over stdio via npx @playwright/mcp. Hand check 2026-08-25: no MCP revision statement in the README or linked docs; @modelcontextprotocol/sdk ^1.25.2 appears only as a devDependency, so the SDK chain cannot ground a revision. Runs stdio by default, HTTP with --port.

PraisonAI MCP Server

Spec Support Unverified First-party

MCP server · by github-mervinpraison · verified

Heavy-host MCP server package (pypi:praisonai-mcp), one of three MCP packages PraisonAI documents alongside a client (praisonaiagents[mcp]) and a light server (praisonai-code). Serves 86 tools, 7 resources, and 7 prompts via `praisonai-mcp serve` (or `praisonai mcp serve`) over stdio (default) or --transport http-stream at a default /mcp endpoint, gated by a single wildcard-scoped --api-key or a --keys-file of per-key scopes. The one Official MCP Registry record found (io.github.MervinPraison/praisonai, v2.3.42, stdio only) describes the older monolithic praisonai package, not this package, and is stale against current releases, so no registry_name is recorded here. No vendor page fetched this session names an MCP spec revision for this server role; the client transports page's "Protocol Revision: 2025-11-25" statement covers only the separate praisonaiagents MCP client class and does not speak for this package. Six CVE records have been filed against PraisonAI's MCP-adjacent code since 2026-08-25, spanning three surfaces: the pip praisonai HTTP-stream transport (three records), the pip praisonai UI host app's stdio-spawn client path (one record), and the separate npm praisonai TypeScript MCPServer (two records); all six are fixed in current releases.

ROS 2 MCP Server

Spec Support Unverified Community

MCP server · by wise-vision · verified

Python MCP server bridging MCP clients to ROS 2 nodes, topics, services and actions over stdio, distributed as the Docker image mcp/ros2 in Docker's curated MCP catalog. No documentation names a supported MCP specification revision: the README links the 2025-06-18 prompts section to explain what prompts are, which is a pointer to the spec rather than a support claim, and the pyproject dependency mcp[cli]>=1.23.0 records an SDK floor, not a revision. The registry record is stale: the repository was renamed from mcp_server_ros_2 to ros2_mcp and its own server.json now declares io.github.wise-vision/ros2_mcp, while the published registry entry still carries the old name and version 1.0.0 from 2025-11-26.

rsdoctor

Spec Support Unverified Publisher unverified

MCP server · by github-yifancong · verified

Distributed as npm:@rsdoctor/mcp-server. Hand check 2026-08-25: no MCP revision statement on rsdoctor.rs, in the repository or the npm README; @modelcontextprotocol/sdk 1.29.0 is a devDependency only. Identity note: the npm package's source directory (packages/ai) is not present on the repository's main branch; the primary npm maintainer is yifancong, matching the registry namespace, while the repository lives in the web-infra-dev organization.

sem

Spec Support Unverified First-party

MCP server · by github-ataraxy-labs · verified

Distributed as npm:@ataraxy-labs/sem. Authority resolved 2026-08-25: Ataraxy Labs Inc. is a verified GitHub organization (blog ataraxy-labs.com) and sem is its own product within the Ataraxy Labs stack; nothing is fronted that the publisher does not operate. No MCP revision statement in README or docs (checked 2026-08-25); "sem mcp starts a Model Context Protocol server over stdin/stdout"; native Rust binary whose npm wrapper declares no dependencies.

SiYuan

Spec Support Unverified First-party

MCP server · by siyuan-note · verified

Built-in MCP server of the SiYuan note-taking application (siyuan-note/siyuan), shipped inside the same Go kernel binary used by the desktop, server, and Docker builds; there is no separate package to install. kernel/mcp/server.go (tag v3.8.3) registers `ginServer.POST("/mcp", model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, serveHTTP(handler))`, plus matching GET and DELETE routes, as Streamable HTTP only; no stdio or SSE code path exists for this server. Auth is an API token, via an `Authorization: Token`/`Bearer` header or a `?token=` query parameter, or an existing session, gated to the Administrator role; the default tool-exposure policy found in source is allow with no overrides, so an authenticated administrator reaches the full tool set by default. The only revision-dated string found anywhere in the fetched surfaces is a source constant, `protocolVersion20260728 = "2026-07-28"`, used only to branch HTTP-handler behavior by request header; that is source code observed via static fetch, not a vendor statement, docs page, or live probe, so spec_status stays unknown. No SiYuan user-guide page for the MCP feature could be fetched: b3log.org/siyuan does not mention MCP and a guessed English-language doc path returned HTTP 404 (COULD NOT VERIFY). The v3.8.0 changelog, published 2026-08-12, announced "Support Model Context Protocol (MCP)" as a new feature, though repository security advisories show the underlying route already existed and was exploitable at v3.7.1, released 2026-07-04, over a month before that changelog entry.

ssh-mcp

Spec Support Unverified Community

MCP server · by tufantunc · verified

Community SSH server distributed as npm:ssh-mcp, running over stdio by default with an optional bearer-token HTTP transport. Destructive and privileged commands are gated behind an MCP elicitation prompt, and the README states that a client without elicitation support has every such command refused rather than silently allowed. No documentation names a supported MCP specification revision; the package depends on @modelcontextprotocol/sdk ^1.30.0, which is an SDK range rather than a revision. The repository has published six security advisories between 2026-08-09 and 2026-09-02, five of them variations on the same defect: the command classifier that enforces read-only mode and the approval gate can be fed a command it misreads.

Storybook MCP Addon

Spec Support Unverified First-party

MCP server · by storybook · verified

Storybook addon that serves an MCP endpoint from the Storybook dev server (default http://localhost:6006/mcp) so agents can read component docs, generate stories, and run story tests. AI features are in preview and React-only per Storybook's docs. Hand check 2026-08-25: no MCP revision statement in the monorepo README, addon README or changelogs. The addon migrated from @modelcontextprotocol/sdk to the third-party tmcp library (addon 0.7.0 depends on tmcp ^1.19.4), which the SDK chain does not cover.

TikTok for Business MCP Server

Spec Support Unverified First-party

MCP server · by tiktok · verified

TikTok's first-party MCP server for the TikTok Ads platform, documented on business-api.tiktok.com as packaging roughly 400 TikTok API for Business endpoints as MCP tools. It is served at two paths under /open_mcp/: tt-ads-mcp-flat loads the full tool set at connection time, and tt-ads-mcp-layer loads around 40 core tools with the rest discoverable on demand. Tokens are scoped per path. Authorization is OAuth 2.0 with dynamic client registration and PKCE (S256), access tokens valid 24 hours and refresh tokens 30 days. No TikTok surface names a supported MCP revision, so spec support is unverified.

Toggl MCP Server

Spec Support Unverified First-party

MCP server · by toggl · verified

Distributed as npm:@togglhq/mcp. First-party on two independent grounds: the GitHub-verified io.github.toggl namespace resolves to Toggl's verified GitHub organization, and npm lists toggl-engineering among the package maintainers. No public repository: npm carries no repository field and github.com/toggl/toggl-mcp returned 404 on 2026-08-27. Authentication is a browser sign-in flow via the server's own auth tool. No MCP revision statement found (checked 2026-08-27).

Weather MCP Server

Spec Support Unverified Community

MCP server · by github-isdaniel · verified

Distributed as pypi:mcp-weather-server. Authority resolved 2026-08-25: the publisher is the personal GitHub account isdaniel (PING-HSIU SHIH) and the server fronts the third-party Open-Meteo API, which the publisher does not operate. No MCP revision statement found (checked 2026-08-25): the README's "latest MCP Streamable HTTP specification" names no revision, and server.json's $schema date is the registry server schema, not a spec revision. PyPI requires mcp[cli]>=1.12.0, an ambiguous range.

Windsurf

Spec Support Unverified

MCP client · by cognition · verified

The Windsurf editor line's agent (Cascade, with Devin Local as the current default) is an MCP client supporting tools, resources, and prompts over stdio, streamable HTTP, and SSE, with OAuth on each transport. Configured in ~/.codeium/windsurf/mcp_config.json with a 100-tool ceiling. The docs now live under docs.devin.ai with Devin as the primary product name. No MCP spec revision is named, so revision support is unverified.

What is MCP News?

MCP News is a factual catalog of Model Context Protocol servers and clients plus a primary-sourced news feed for the MCP ecosystem. Every record carries source URLs, a verification date, and a calibrated confidence score, so claims like "first-party server" or "supports the 2026-07-28 stateless revision" can be checked rather than guessed at. Records that fall below the publishing threshold stay in moderation and never appear here.