MCP Servers
781 MCP servers are cataloged on MCP News - 47 with verified support for the current spec revision (2026-07-28), 76 verified first-party.
781 servers cataloged. Click a server for verified facts, access details, and spec-support records.
- @imqueue - Earlier Revision
imqueue.org
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
0nMCP — Universal AI API Orchestrator - Earlier Revision0nork
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
1Claw Vault - Spec Support Unverified1clawAI
Distributed as npm:@1claw/mcp. Spec revision support not yet verified.
-
1password - Current Spec VerifiedCakeRepository
Distributed as npm:@takescake/1password-mcp. Resolved from the published package: @takescake/1password-mcp 4.0.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
Address Validator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Adeu - Earlier RevisionDealfluence
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.
- adrkit decision memory - Current Spec Verified
adrkit.dev
Distributed as npm:@adrkit/mcp. Resolved from the published package: @adrkit/mcp 0.8.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.
-
Advanced GitLab MCP server - Earlier Revisionstructured-world
Distributed as npm:@structured-world/gitlab-mcp. Resolved from the published package: @structured-world/gitlab-mcp 9.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
aegis - Earlier Revisiongetaegis
Distributed as npm:@getaegis/cli. Resolved from the published package: @getaegis/cli 1.0.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Affiliate Networks MCP - Earlier Revision
agenticaffiliate.ai
Listed with a remote endpoint. Resolved from the published package: affiliate-networks-mcp 0.20.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.
-
Agent Comms - Earlier RevisionExaDev
Distributed as npm:agent-comms. Resolved from the published package: agent-comms 1.24.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.
- Agent Swarm - Spec Support Unverified
Desplega Labs
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.
-
agent-device - Earlier RevisionCallstack
Callstack's CLI and MCP server for driving iOS, Android, TV, desktop, and web apps from coding agents, run locally via agent-device mcp over stdio. Its hand-rolled MCP implementation hard-codes protocol revision 2025-11-25 in the initialize handshake; 2026-07-28 support is not implemented.
-
agent-lsp - Spec Support Unverifiedblackwell-systems
Distributed as npm:@blackwell-systems/agent-lsp. Spec revision support not yet verified.
-
agent-recall - Earlier RevisionGoldentrii
Distributed as npm:agent-recall-mcp. Resolved from the published package: agent-recall-mcp 3.4.45 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
agent-security-scanner-mcp - Earlier Revisionsinewaveai
Distributed as npm:agent-security-scanner-mcp. Resolved from the published package: agent-security-scanner-mcp 4.5.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
agent-spend-policy-mcp - Earlier Revisiondingdawg
Distributed as npm:@dingdawg/agent-spend-policy-mcp. Resolved from the published package: @dingdawg/agent-spend-policy-mcp 0.1.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.
-
Agent360 Browser MCP - Earlier RevisionAgent360dk
Distributed as npm:@agent360/browser-mcp. Resolved from the published package: @agent360/browser-mcp 1.25.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.
-
Agent402.Tools - pay-per-call web tools - Earlier RevisionMikeyPetrillo
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
agentcash - Earlier RevisionMerit-Systems
Distributed as npm:agentcash. Resolved from the published package: agentcash 0.17.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.
-
Agentic Mermaid - Current Spec Verifiedadewale
Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
agentmap - Spec Support Unverifiedraymondchins
Distributed as npm:@raymondchins/agentmap. Spec revision support not yet verified.
- AgentPhone - Spec Support Unverified
AgentPhone
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.
-
AgentUtility Compose - Earlier Revisionagentutility.ai
Distributed as npm:@agentutility/mcp-compose. Resolved from the published package: @agentutility/mcp-compose 0.18.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.
-
AgentUtility Edge Finance - Earlier Revisionagentutility.ai
Distributed as npm:@agentutility/mcp-edge-finance. Resolved from the published package: @agentutility/mcp-edge-finance 0.19.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.
-
AgentUtility Wordmint - Earlier Revisionagentutility.ai
Distributed as npm:@agentutility/mcp-wordmint. Resolved from the published package: @agentutility/mcp-wordmint 0.17.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
agentwallet - Earlier Revisionhifriendbot
Distributed as npm:agentwallet-mcp. Resolved from the published package: agentwallet-mcp 1.10.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.
-
Agoragentic Agent OS MCP - Current Spec Verifiedrhein1
Endpoint probe confirmed support for 2026-07-28 via server/discover.
- ai-agent-firewall - Earlier Revision
fidacy.com
Distributed as npm:@fidacy/mcp. Resolved from the published package: @fidacy/mcp 0.18.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ai-context - Earlier Revisionvibgrate.com
Distributed as npm:@vibgrate/cli. Resolved from the published package: @vibgrate/cli 2026.819.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.
- ai-netcafe - Current Spec Verified
ainetcafe.com
Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
ai-test-process-mcp - Earlier RevisionHashi-Kazu
Distributed as npm:ai-test-process-mcp. Resolved from the published package: ai-test-process-mcp 0.39.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ai·rete·rag - Earlier Revisionai-rete-rag.com
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
ainative-gtm-mcp - Earlier RevisionAINative-Studio
Distributed as npm:@ainative/gtm-mcp. Resolved from the published package: @ainative/gtm-mcp 0.5.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.
-
AIOProductOS MCP - Earlier Revisionaioproductos.com
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
AIquila - Nextcloud MCP Server - Earlier Revisionelgorro
Distributed as npm:aiquila-mcp. Resolved from the published package: aiquila-mcp 0.4.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.
-
Airdrop Checker API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
airmcp - Earlier Revisionheznpc
Distributed as npm:airmcp. Resolved from the published package: airmcp 2.16.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Airtable - Earlier Revisiondomdomegg
Distributed as npm:airtable-mcp-server. Resolved from the published package: airtable-mcp-server 1.14.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.
-
Airweave Search - Earlier Revisionairweave-ai
Listed with a remote endpoint. Resolved from the published package: airweave-mcp-search 0.9.62 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- aiterm-mcp - Earlier Revision
kitepon-rgb
Distributed as npm:aiterm-mcp. Resolved from the published package: aiterm-mcp 0.27.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.
-
Aiven MCP - Earlier Revisionaiven.io
Distributed as npm:mcp-aiven. Resolved from the published package: mcp-aiven 1.15.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
AlgoVault - Crypto Quant Trade Calls - Earlier RevisionAlgoVaultFi
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
alphacouncil-agent - Spec Support UnverifiedZhao73
Distributed as npm:alphacouncil-agent. Spec revision support not yet verified.
-
Amazon Bedrock AgentCore Gateway - Current Spec VerifiedAmazon Web Services
A managed AWS service rather than an installable server: each customer gets a per-tenant gateway endpoint and registers their own tool targets. Support for the 2026-07-28 revision is opt-in per gateway, enabled by calling UpdateGateway with the revision in supportedVersions. No source repository or package exists.
-
amcharts5 - Earlier Revisionamcharts
Distributed as npm:@amcharts/amcharts5-mcp. Resolved from the published package: @amcharts/amcharts5-mcp 1.4.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.
-
Amicus - Earlier RevisionBourbonDog
Distributed as npm:amicus. Resolved from the published package: amicus 4.7.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.
-
AniList MCP Server - Current Spec VerifiedGrinv
Distributed as npm:anilist-mcp-server. Resolved from the published package: anilist-mcp-server 0.8.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.
-
Anki MCP Server - Current Spec Verifiedankimcp.ai
Distributed as npm:@ankimcp/anki-mcp-server. Resolved from the published package: @ankimcp/anki-mcp-server 0.24.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
antics-mcp - Earlier Revisionantics-gg
Distributed as npm:antics-mcp. Resolved from the published package: antics-mcp 0.4.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.
-
anytype-mcp - Earlier Revisionanyproto
Distributed as npm:@anyproto/anytype-mcp. Resolved from the published package: @anyproto/anytype-mcp 1.2.10 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Apache SkyWalking MCP - Spec Support UnverifiedThe Apache Software Foundation
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.
-
Apify MCP Server - Current Spec VerifiedApify
Apify's first-party MCP server, hosted at mcp.apify.com over streamable HTTP, which exposes the Apify Store of scrapers and automations as MCP tools and can load an individual Actor's own MCP tools. Auth is OAuth or an Apify API token as a bearer header; an unauthenticated request to the endpoint returns 401. Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
app-publish - Earlier Revisionmikusnuz
Distributed as npm:app-publish-mcp. Resolved from the published package: app-publish-mcp 0.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.
-
Appfigures - Spec Support Unverifiedappfigures.com
Distributed as npm:@appfigures/cli. Spec revision support not yet verified.
- Appium MCP - Earlier Revision
Appium
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.
-
Apple Health - Earlier Revisionneiltron
Distributed as npm:@neiltron/apple-health-mcp. Resolved from the published package: @neiltron/apple-health-mcp 1.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.
-
Applitools - Earlier Revisionapplitools
Distributed as npm:@applitools/mcp. Resolved from the published package: @applitools/mcp 0.5.16 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
appstoreconnect-mcp - Current Spec Verifiedakoskomuves
Distributed as npm:@akoskomuves/appstoreconnect-mcp. Resolved from the published package: @akoskomuves/appstoreconnect-mcp 1.9.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.
-
Ara - audits d'accessibilité RGAA - Current Spec VerifiedDavidPivert
Distributed as npm:ara-rgaa-mcp. Resolved from the published package: ara-rgaa-mcp 2.5.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.
-
Argent - Earlier Revisionsoftware-mansion
Distributed as npm:@swmansion/argent. Resolved from the published package: @swmansion/argent 0.21.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.
- argocd-mcp - Spec Support Unverified
argoproj-labs
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.
- argot - Spec Support Unverified
get-tmonier
Distributed as npm:@tmonier/argot. Spec revision support not yet verified.
-
argus-decision-mcp - Earlier Revisioncommet
Distributed as npm:argus-decision-mcp. Resolved from the published package: argus-decision-mcp 2.0.23 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
asc-mcp - Earlier Revisionpofky
Distributed as npm:@pofky/asc-mcp. Resolved from the published package: @pofky/asc-mcp 1.9.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Ash AI MCP Server - Current Spec Verified
Ash Framework
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.
-
ask-antigravity - Earlier RevisionLykhoyda
Distributed as npm:@ask-llm/antigravity-mcp. Resolved from the published package: @ask-llm/antigravity-mcp 0.7.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.
-
ask-codex - Earlier RevisionLykhoyda
Distributed as npm:@ask-llm/codex-mcp. Resolved from the published package: @ask-llm/codex-mcp 0.7.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.
-
ask-llm - Earlier RevisionLykhoyda
Distributed as npm:@ask-llm/mcp. Resolved from the published package: @ask-llm/mcp 0.6.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ask-ollama - Earlier RevisionLykhoyda
Distributed as npm:@ask-llm/ollama-mcp. Resolved from the published package: @ask-llm/ollama-mcp 0.5.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
astro-mcp - Spec Support Unverifiedmorinokami
Distributed as npm:astro-mcp. Spec revision support not yet verified.
-
ateam-mcp - Earlier Revisionariekogan
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
atlassian-dc-mcp-bitbucket - Earlier Revisionb1ff
Distributed as npm:@atlassian-dc-mcp/bitbucket. Resolved from the published package: @atlassian-dc-mcp/bitbucket 0.29.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.
-
atlassian-dc-mcp-confluence - Earlier Revisionb1ff
Distributed as npm:@atlassian-dc-mcp/confluence. Resolved from the published package: @atlassian-dc-mcp/confluence 0.29.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.
-
atlassian-dc-mcp-jira - Earlier Revisionb1ff
Distributed as npm:@atlassian-dc-mcp/jira. Resolved from the published package: @atlassian-dc-mcp/jira 0.29.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.
-
Atomic Mail - Earlier RevisionAtomic-Mail
Distributed as npm:@atomicmail/mcp-modelcontextprotocol. Resolved from the published package: @atomicmail/mcp-modelcontextprotocol 0.3.26 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Attio MCP Server - Earlier Revisionkesslerio
Distributed as npm:attio-mcp. Resolved from the published package: attio-mcp 1.6.1 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Auth0 MCP Server - Earlier Revisionauth0.com
Distributed as npm:@auth0/auth0-mcp-server. Resolved from the published package: @auth0/auth0-mcp-server 0.1.0-beta.19 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
AutoMobile - Earlier Revisionjasonpearson.dev
Distributed as npm:@kaeawc/auto-mobile. Resolved from the published package: @kaeawc/auto-mobile 0.0.60 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
avito-mcp - Current Spec Verifiedelchin92
Distributed as npm:avito-mcp. Resolved from the published package: avito-mcp 2.0.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.
-
AWS Labs postgres MCP Server - Spec Support UnverifiedAmazon Web Services
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.
-
Axis - Earlier Revisionuseaxis.dev
Listed with a remote endpoint. Resolved from the published package: @virsanghavi/axis-server 1.14.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Azure MCP Server - Current Spec VerifiedMicrosoft
Microsoft's first-party Azure MCP server, distributed from the microsoft/mcp monorepo. The CHANGELOG records the migration to the 2026-07-28 stateless protocol in prerelease 3.0.0-beta.29 dated 2026-07-23. No stable 3.0.0 has shipped and no vendor-hosted remote endpoint is published; the README documents self-hosting only.
-
better-email-mcp - Earlier Revisionn24q02m
Distributed as npm:@n24q02m/better-email-mcp. Resolved from the published package: @n24q02m/better-email-mcp 1.39.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.
-
Bilibili MCP Server - Earlier RevisionXZXZZX-Ai
Distributed as npm:@xzxzzx/bilibili-mcp. Resolved from the published package: @xzxzzx/bilibili-mcp 1.13.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.
-
bisibility - Earlier Revisionbisibility.com
Listed with a remote endpoint. Resolved from the published package: @bisibility/mcp 0.9.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.
-
Bitbucket MCP (MatanYemini) - Earlier RevisionMatanYemini
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.
-
Black Duck Security Scanner - Earlier Revisionblackduck.com
Distributed as npm:@black-duck/mcp-server. Resolved from the published package: @black-duck/mcp-server 1.1.8 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
blockrun-mcp - Earlier RevisionBlockRunAI
Distributed as npm:@blockrun/mcp. Resolved from the published package: @blockrun/mcp 0.40.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
BoondManager MCP Server - Earlier Revisionfauguste
Distributed as npm:boondmanager-mcp-server. Resolved from the published package: boondmanager-mcp-server 2.12.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Bowmark - Earlier Revisionbowmark.ai
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
brains - Earlier Revisionspacecowboyian
Distributed as npm:brains-mcp. Resolved from the published package: brains-mcp 1.68.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.
-
Brandsystem MCP - Brand Guidelines for AI - Earlier RevisionBrandcode-Studio
Distributed as npm:@brandsystem/mcp. Resolved from the published package: @brandsystem/mcp 0.16.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.
-
brave-search-mcp-server - Earlier Revisionbrave
Distributed as npm:@brave/brave-search-mcp-server. Resolved from the published package: @brave/brave-search-mcp-server 2.1.0 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- bray - Earlier Revision
forgesworn.dev
Distributed as npm:nostr-bray. Resolved from the published package: nostr-bray 3.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
brightdata-mcp - Earlier Revisionbrightdata
Distributed as npm:@brightdata/mcp. Resolved from the published package: @brightdata/mcp 2.11.1 depends on @modelcontextprotocol/sdk@1.21.2, whose artifact implements 2025-06-18. This records what the artifact implements, not what a deployment negotiates.
-
brilliant-directories-mcp - Earlier Revisionbrilliantdirectories
Distributed as npm:brilliant-directories-mcp. Resolved from the published package: brilliant-directories-mcp 6.58.595 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Browser Automation - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-browser-automation. Resolved from the published package: @mindstone/mcp-server-browser-automation 0.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Browser Use MCP Server - Earlier RevisionBrowser Use
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.
-
browser-devtools-mcp - Earlier Revisionserkan-ozal
Distributed as npm:browser-devtools-mcp. Resolved from the published package: browser-devtools-mcp 0.9.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.
-
browser-gateway - Earlier Revisionbrowser-gateway
Distributed as npm:browser-gateway. Resolved from the published package: browser-gateway 0.4.13 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
BrowserStack MCP Server - Earlier RevisionBrowserStack
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.
-
bvcc-agent-wallet - Earlier Revisionblockventurechaincapital.com
Distributed as npm:@bvcc/agent-mcp. Resolved from the published package: @bvcc/agent-mcp 0.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
C64 Bridge - Earlier Revisionchrisgleissner
Distributed as npm:c64bridge. Resolved from the published package: c64bridge 1.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
caldav-mcp - Earlier Revisiondominik1001
Distributed as npm:caldav-mcp. Resolved from the published package: caldav-mcp 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.
-
calibre-mcp - Earlier Revisioncaelum29
Distributed as npm:calibre-mcp. Resolved from the published package: calibre-mcp 0.7.3 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Callosium - Earlier Revisioncallosium
Distributed as npm:callosium. Resolved from the published package: callosium 0.1.18 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
calm-mcp - Spec Support UnverifiedEilodon
Distributed as npm:@eilodon/calm-mcp. Spec revision support not yet verified.
-
campus-cli - Earlier Revisionalejooroncoy
Distributed as npm:campus-cli. Resolved from the published package: campus-cli 2.0.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.
-
canvas-lms-mcp - Earlier Revisionbruchris
Distributed as npm:canvas-lms-mcp. Resolved from the published package: canvas-lms-mcp 1.27.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.
-
ccu-mcp - Earlier Revisionclaymore666
Distributed as npm:ccu-mcp. Resolved from the published package: ccu-mcp 1.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.
-
cesium-mcp-dev - Current Spec Verifiedgaopengbin
Distributed as npm:cesium-mcp-dev. Resolved from the published package: cesium-mcp-dev 1.145.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
cesium-mcp-runtime - Current Spec Verifiedgaopengbin
Distributed as npm:cesium-mcp-runtime. Resolved from the published package: cesium-mcp-runtime 1.145.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
charlotte - Current Spec VerifiedTickTockBent
Distributed as npm:@ticktockbent/charlotte. Resolved from the published package: @ticktockbent/charlotte 0.8.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.
-
Chrome DevTools MCP - Spec Support UnverifiedGoogle
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.
-
chrome-bridge - Earlier Revisionfrsorrentino
Distributed as npm:chrome-bridge-mcp. Resolved from the published package: chrome-bridge-mcp 1.15.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.
-
chron - Earlier RevisionSirinivasK
Distributed as npm:chron-mcp. Resolved from the published package: chron-mcp 0.1.52 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
cituna-mcp - Earlier Revisioncituna.com
Distributed as npm:cituna-mcp. Resolved from the published package: cituna-mcp 1.0.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.
-
ckan-mcp-server - Earlier Revisionaborruso
Distributed as npm:@aborruso/ckan-mcp-server. Resolved from the published package: @aborruso/ckan-mcp-server 0.4.118 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 FAF - Earlier Revisionfaf.one
Distributed as npm:claude-faf-mcp. Resolved from the published package: claude-faf-mcp 5.22.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.
-
claude-flow - Earlier Revisionruvnet
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.
-
claude-mcp-bridge - Earlier Revisionhampsterx
Distributed as npm:claude-mcp-bridge. Resolved from the published package: claude-mcp-bridge 0.7.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.
-
claude-prompts-mcp - Current Spec Verifiedminipuft
Distributed as npm:claude-prompts. Resolved from the published package: claude-prompts 4.0.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
Claudexor - Spec Support Unverifiedrazzant
Distributed as npm:claudexor. Spec revision support not yet verified.
-
claudinho - Earlier Revisionarturogarrido
Distributed as npm:@claudinho/mcp. Resolved from the published package: @claudinho/mcp 0.9.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.
-
CLEO MCP Server - Spec Support Unverifiedkryptobaseddev
Distributed as npm:@cleocode/cleo. Spec revision support not yet verified.
-
cli-microsoft365-mcp-server - Earlier Revisionpnp
Distributed as npm:@pnp/cli-microsoft365-mcp-server. Resolved from the published package: @pnp/cli-microsoft365-mcp-server 0.1.23 depends on @modelcontextprotocol/sdk@1.27.1, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
clickup - Earlier Revisiontaazkareem
Distributed as npm:@taazkareem/clickup-mcp-server. Resolved from the published package: @taazkareem/clickup-mcp-server 0.14.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- CloudBase MCP - Spec Support Unverified
Tencent CloudBase
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.
-
Cloudflare MCP servers - Current Spec VerifiedCloudflare
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.
-
code-auditor-mcp - Earlier RevisionBenAHammond
Distributed as npm:code-auditor-mcp. Resolved from the published package: code-auditor-mcp 3.4.15 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
code-index - Spec Support UnverifiedRegsorm
Distributed as npm:@regsorm/code-index-mcp. Spec revision support not yet verified.
-
Codebase Memory MCP - Spec Support UnverifiedMartin Vogel
Community MCP server (by developer Martin Vogel) that indexes a codebase into a persistent knowledge graph for AI agents, distributed as a static binary via npm or PyPI and run locally over stdio. Hand check 2026-08-25: no MCP revision statement in README or docs; ships as a native binary whose npm package declares no runtime dependencies, so no SDK chain exists.
-
codebase-synapse - Spec Support Unverifiediwiels
Distributed as npm:codebase-synapse. Spec revision support not yet verified.
-
codegraph - Spec Support Unverifiedcodegraph-ai
Distributed as npm:@astudioplus/codegraph-mcp. Spec revision support not yet verified.
-
CodeInspectus - Earlier RevisionSynvoya
Distributed as npm:codeinspectus. Resolved from the published package: codeinspectus 2.5.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.
-
codeledger - Spec Support UnverifiedcodeledgerECF
Distributed as npm:@codeledger/cli. Spec revision support not yet verified.
-
codescene-mcp-server - Spec Support Unverifiedcodescene.com
Distributed as npm:@codescene/codehealth-mcp. Spec revision support not yet verified.
-
codexa - Earlier Revisionmirnoorata
Distributed as npm:@mirnoorata/codexa. Resolved from the published package: @mirnoorata/codexa 0.18.0 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
coldstart - Earlier RevisionAkashGoenka
Distributed as npm:@cstart/coldstart. Resolved from the published package: @cstart/coldstart 2.2.18 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Color Palette Generator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
comfyui-mcp - Earlier Revisionartokun
Distributed as npm:comfyui-mcp. Resolved from the published package: comfyui-mcp 0.52.25 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
compass-mcp - Earlier Revisionchrischall
Distributed as npm:compass-mcp. Resolved from the published package: compass-mcp 0.12.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.
-
Computer Use - Earlier Revisiondomdomegg
Distributed as npm:computer-use-mcp. Resolved from the published package: computer-use-mcp 1.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.
- Concord MCP - Spec Support Unverified
Concord AI
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.
-
Containerization Assist - Earlier RevisionAzure
Distributed as npm:containerization-assist-mcp. Resolved from the published package: containerization-assist-mcp 1.5.0 depends on @modelcontextprotocol/sdk@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Contentful MCP Server - Spec Support Unverified
Contentful
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.
-
Contentrain - Earlier RevisionContentrain
Distributed as npm:@contentrain/mcp. Resolved from the published package: @contentrain/mcp 3.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.
-
context - Earlier Revisionneuledge
Distributed as npm:@neuledge/context. Resolved from the published package: @neuledge/context 1.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
context-firewall - Earlier RevisionAlepha188838884
Distributed as npm:context-firewall. Resolved from the published package: context-firewall 0.3.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.
-
Context7 - Current Spec VerifiedUpstash
Upstash's Context7 documentation server: pulls current, version-specific library docs into prompts. Hosted at mcp.context7.com/mcp with bearer API keys (anonymous use is rate-limited); also runs locally via npm. The 4.0.0 release of 2026-08-07 migrated to the 2026-07-28 revision, and an endpoint probe the same day confirmed it. Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
ContextStream MCP Server - Earlier Revisioncontextstreamio
Distributed as npm:@contextstream/mcp-server. Resolved from the published package: @contextstream/mcp-server 0.4.82 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ControlKeel - Spec Support Unverifiedaryaminus
Distributed as npm:@aryaminus/controlkeel. Spec revision support not yet verified.
-
coolify - Earlier RevisionStuMason
Distributed as npm:@masonator/coolify-mcp. Resolved from the published package: @masonator/coolify-mcp 2.19.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.
- Coroot - Spec Support Unverified
Coroot
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.
-
cortex - Spec Support UnverifiedDanielBlomma
Distributed as npm:@danielblomma/cortex-mcp. Spec revision support not yet verified.
-
Cortex RMCP - Spec Support Unverifieddinglebear.ai
Distributed as npm:@dinglebear/cortex. Spec revision support not yet verified.
- crawlforge-mcp-server - Earlier Revision
mysleekdesigns
Distributed as npm:crawlforge-mcp-server. Resolved from the published package: crawlforge-mcp-server 5.0.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.
-
crawlio-browser - Earlier Revisioncrawlio.app
Distributed as npm:crawlio-browser. Resolved from the published package: crawlio-browser 1.11.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.
-
Crontab Generator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Crypto News Feed API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
CSV to JSON API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
ctxlint - Spec Support UnverifiedYawLabs
MCP server and CLI that lints AI agent context files (CLAUDE.md, AGENTS.md, and similar) against the actual codebase they describe. Registry and npm agree on 0.22.0 (2026-08-08). No project surface names a supported MCP revision.
-
cuba-memorys - Spec Support UnverifiedLeandroPG19
Distributed as npm:cuba-memorys. Spec revision support not yet verified.
-
Currency Converter API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
dark-memory-mcp - Spec Support UnverifiedOpita-Code
Distributed as npm:@opitacode/dark-memory-mcp. Spec revision support not yet verified.
-
datadog-mcp - Earlier RevisionTANTIOPE
Distributed as npm:datadog-mcp. Resolved from the published package: datadog-mcp 5.8.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Dates-LE - Spec Support Unverifiednolindnaidoo
Distributed as npm:dates-le-mcp. Spec revision support not yet verified.
-
DBHub - Current Spec VerifiedBytebase
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.
-
dbx - Spec Support Unverifiedt8y2
Distributed as npm:@dbx-app/mcp-server. Hand check 2026-08-25: no MCP revision statement in the main or mcp-server package READMEs; the Rust server depends on rmcp 2.2.0 (Cargo.toml), not sufficient evidence on its own. Authority evidence: t8y2 is the sole npm maintainer (tongty.it@gmail.com) and owns the repository; dbx is the account's own product.
- Decionis MCP - Spec Support Unverified
Decionis
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.
-
DeepSeek MCP Server - Earlier RevisionDMontgomery40
Distributed as npm:deepseek-mcp-server. Resolved from the published package: deepseek-mcp-server 0.6.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.
-
DeFi Yield Finder API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
deja-vu - Spec Support Unverifiedvshulcz
Distributed as npm:@vshulcz/deja-vu. Spec revision support not yet verified.
-
depwire - Earlier Revisionatef-ataya
Distributed as npm:depwire-cli. Resolved from the published package: depwire-cli 1.16.0 depends on @modelcontextprotocol/sdk@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
DERO MCP Server - Current Spec VerifiedDHEBP
Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
Desktop Commander - Earlier RevisionDesktop Commander
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.
-
desktop-touch-mcp - Spec Support UnverifiedHarusame64
Distributed as npm:@harusame64/desktop-touch-mcp. Spec revision support not yet verified.
-
DEX Swap Quotes API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
- dex-data - Spec Support Unverified
donnyautomation.com
Distributed as npm:dex-data-mcp. Spec revision support not yet verified.
-
dgmo-mcp - Earlier Revisiondiagrammo
Distributed as npm:@diagrammo/dgmo-mcp. Resolved from the published package: @diagrammo/dgmo-mcp 0.28.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.
-
Diff Checker API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Discord MCP - Current Spec Verifiedcappyeo
Distributed as npm:@discord-mcp/cli. Resolved from the published package: @discord-mcp/cli 0.23.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.
-
discord-mcp - Earlier RevisionPaSympa
Distributed as npm:@pasympa/discord-mcp. Resolved from the published package: @pasympa/discord-mcp 2.1.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.
-
DNS Lookup API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
dns-doctor - Earlier Revisiondnsdoctor.dev
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
- Doc Bridge - Spec Support Unverified
AgentsKit.io
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.
-
docdex - Spec Support Unverifiedbekirdag
Distributed as npm:docdex. Spec revision support not yet verified.
-
DocGuard - Spec Support Unverifiedraccioly
Distributed as npm:docguard-cli. Spec revision support not yet verified.
-
DollhouseMCP - Earlier RevisionDollhouseMCP
Distributed as npm:@dollhousemcp/mcp-server. Resolved from the published package: @dollhousemcp/mcp-server 2.0.40 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- domain-check-skills-mcp - Earlier Revision
seomarlboro
Distributed as npm:domain-check-skills-mcp. Resolved from the published package: domain-check-skills-mcp 1.2.10 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
domain-search-mcp - Earlier Revisiondorukardahan
Distributed as npm:domain-search-mcp. Resolved from the published package: domain-search-mcp 1.13.1 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
DomainKits - Earlier RevisionABTdomain
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
DopamineDesk x402 Marketplace - Earlier Revisionjblaz6335
Distributed as npm:dopaminedesk-ai-data-marketplace-mcp. Resolved from the published package: dopaminedesk-ai-data-marketplace-mcp 2.8.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.
-
dot-ai - Earlier Revisionvfarcic
Distributed as npm:@vfarcic/dot-ai. Resolved from the published package: @vfarcic/dot-ai 2.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Drengr - Spec Support Unverified
drengr.dev
Distributed as npm:drengr. Spec revision support not yet verified.
- driflyte-mcp-server - Earlier Revision
driflyte.com
Listed with a remote endpoint. Resolved from the published package: @driflyte/mcp-server 0.1.15 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
DroidAgentKit - Spec Support UnverifiediVamsi
Distributed as npm:@droidagentkit/launcher. Spec revision support not yet verified.
-
dvalincode - Spec Support Unverifiedarthurpanhku
Distributed as npm:dvalincode. Spec revision support not yet verified.
-
dynatrace-managed-mcp - Earlier Revisiondynatrace-oss
Distributed as npm:@dynatrace-oss/dynatrace-managed-mcp-server. Resolved from the published package: @dynatrace-oss/dynatrace-managed-mcp-server 1.0.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.
-
Dynatrace-mcp - Spec Support Unverifieddynatrace-oss
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".
-
Dynoxide - Spec Support Unverifiednubo-db
Distributed as npm:dynoxide. Authority resolved 2026-08-25: nubo-db is a GitHub organization and Dynoxide is its own product, a DynamoDB emulator whose MCP server is one of its run modes (dynoxide mcp, stdio or HTTP, 35 tools). No MCP revision statement in README, docs/mcp.md or server.json (checked 2026-08-25); Cargo.lock pins rmcp 1.8.0, not sufficient evidence on its own.
-
e-arveldaja-mcp - Earlier Revisioniseppo
Distributed as npm:e-arveldaja-mcp. Resolved from the published package: e-arveldaja-mcp 0.25.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
easy-notion - Earlier Revisionmisterwigglesworth
Distributed as npm:easy-notion-mcp. Resolved from the published package: easy-notion-mcp 1.0.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.
-
EasyEDA Copilot - Earlier Revisionbiosshot
Distributed as npm:easyeda-copilot-mcp. Resolved from the published package: easyeda-copilot-mcp 1.1.7 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
easyeda-mcp-pro - Earlier Revisionoaslananka
Distributed as npm:easyeda-mcp-pro. Resolved from the published package: easyeda-mcp-pro 0.35.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.
-
edict - Earlier RevisionSowiedu
Distributed as npm:edict-lang. Resolved from the published package: edict-lang 1.23.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ellmos CodeCommander - Earlier Revisionellmos-ai
Distributed as npm:ellmos-codecommander-mcp. Resolved from the published package: ellmos-codecommander-mcp 1.3.22 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Email Deliverability Audit API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Email Finder API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
email-mcp - Earlier Revisioncodefuturist
Distributed as npm:@codefuturist/email-mcp. Resolved from the published package: @codefuturist/email-mcp 0.2.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.
- emailmd - Earlier Revision
emailmd.dev
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
EnConvert - Earlier Revisionenconvert.com
Distributed as npm:@enconvert/mcp. Resolved from the published package: @enconvert/mcp 0.5.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.
- endiagram-mcp - Earlier Revision
dushyant30suthar
Endpoint probe negotiated 2025-03-26; support for 2026-07-28 not confirmed.
-
enquire-mcp - Earlier Revisionoomkapwn
Distributed as npm:@oomkapwn/enquire-mcp. Resolved from the published package: @oomkapwn/enquire-mcp 3.11.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ENS Resolver API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Entroly - Earlier Revisionjuyterman1000
Distributed as pypi:entroly. Resolved from the published package: entroly 1.0.78 depends on mcp@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
esa - Earlier Revisionesaio
Distributed as npm:@esaio/esa-mcp-server. Resolved from the published package: @esaio/esa-mcp-server 0.14.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.
-
Event Resolver API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
eventbrite-mcp - Earlier Revisionchrischall
Distributed as npm:@chrischall/eventbrite-mcp. Resolved from the published package: @chrischall/eventbrite-mcp 0.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
EveryAILaw - Spec Support Unverifiedsnapsynapse
Distributed as npm:every-ai-law. Spec revision support not yet verified.
-
Expo Android MCP - Earlier Revisionfrndchagas
Distributed as npm:@fndchagas/expo-android. Resolved from the published package: @fndchagas/expo-android 0.5.1 depends on @modelcontextprotocol/sdk@1.25.1, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Fathom - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-fathom. Resolved from the published package: @mindstone/mcp-server-fathom 0.3.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.
-
Figma MCP Server - Earlier Revisionplanetabhi
Distributed as npm:figma-mcp-server. Resolved from the published package: figma-mcp-server 3.1.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.
-
figma-mcp-express - Spec Support Unverifiedsunhome243
Distributed as npm:figma-mcp-express. Spec revision support not yet verified.
-
figma-mcp-go - Spec Support Unverifiedtunglt1810
Distributed as npm:@tunglt1810/figma-mcp-go. Spec revision support not yet verified.
-
figma-mcp-go - Spec Support Unverifiedvkhanhqui
Distributed as npm:@vkhanhqui/figma-mcp-go. Spec revision support not yet verified.
-
figma-mcp-rust - Spec Support Unverifiedalvinindra
Distributed as npm:@alvinindra/figma-mcp-rust. Spec revision support not yet verified.
-
figma-ui-mcp - Earlier RevisionTranHoaiHung
Distributed as npm:figma-ui-mcp. Resolved from the published package: figma-ui-mcp 2.5.26 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Financial Modeling Prep MCP Server - Earlier Revisionimbenrabi
Distributed as npm:financial-modeling-prep-mcp-server. Resolved from the published package: financial-modeling-prep-mcp-server 2.6.12 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Find doctors and specialists in the Greater Toronto Area - Earlier Revisiontypestoofast
Distributed as npm:@find-doc/finddoc-mcp. Resolved from the published package: @find-doc/finddoc-mcp 0.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.
-
fiori-mcp-server - Spec Support UnverifiedSAP
Distributed as npm:@sap-ux/fiori-mcp-server. Hand check 2026-08-25: no MCP revision statement in the package README; src/server.ts negotiates the protocol version with FALLBACK_PROTOCOL_VERSION '2024-11-05', and @modelcontextprotocol/sdk 1.29.0 appears as a devDependency, so the SDK chain cannot ground a revision. Frequent releases (1.11.14 on 2026-08-25).
-
Firebase MCP Server - Earlier RevisionGoogle
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 RevisionFirecrawl
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.
-
fitbitmcp - Earlier Revisiondavidmosiah
Distributed as npm:fitbit-mcp-unofficial. Resolved from the published package: fitbit-mcp-unofficial 0.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
five46 - Spec Support Unverifiedsekharsdet
Distributed as npm:five46. Spec revision support not yet verified.
-
fixmap - Earlier Revisionaryamthecodebreaker
Distributed as npm:@aryam/fixmap. Resolved from the published package: @aryam/fixmap 0.9.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.
-
fondue-city-mcp - Earlier RevisionEdward-CH-Wang
Distributed as npm:fondue-city-mcp. Resolved from the published package: fondue-city-mcp 0.1.14 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
formio-mcp - Earlier Revisionform.io
Distributed as npm:@formio/mcp. Resolved from the published package: @formio/mcp 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.
-
formio-uag - Earlier Revisionform.io
Distributed as npm:@formio/uag. Resolved from the published package: @formio/uag 1.13.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- formlab-mcp - Earlier Revision
juliu1980
Distributed as npm:formlab-mcp. Resolved from the published package: formlab-mcp 0.6.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Framelink MCP for Figma - Earlier Revision
Framelink
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.
-
france-data-mcp - Earlier Revisioncturkieh
Endpoint probe negotiated 2025-06-18; support for 2026-07-28 not confirmed.
-
fred-mcp-server - Earlier Revisionstefanoamorelli
Distributed as npm:fred-mcp-server. Resolved from the published package: fred-mcp-server 1.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
FreightUtils MCP Server - Earlier RevisionSoapyRED
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Frihet ERP - Earlier Revisionfrihet.io
Listed with a remote endpoint. Resolved from the published package: @frihet/mcp-server 1.16.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Funplay Cocos MCP - Spec Support UnverifiedFunplayAI
Distributed as npm:funplay-cocos-mcp. Spec revision support not yet verified.
-
Funplay Godot MCP - Spec Support UnverifiedFunplayAI
Distributed as npm:funplay-godot-mcp. Spec revision support not yet verified.
-
Gaffer - Earlier Revisiongaffer.sh
Distributed as npm:@gaffer-sh/mcp. Resolved from the published package: @gaffer-sh/mcp 0.9.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.
-
Gamma - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-gamma. Resolved from the published package: @mindstone/mcp-server-gamma 0.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.
-
garminmcp - Earlier Revisiondavidmosiah
Distributed as npm:garmin-mcp-unofficial. Resolved from the published package: garmin-mcp-unofficial 0.7.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.
-
Gas Estimator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Gateco - Earlier Revisiongateco.ai
Distributed as pypi:gateco. Resolved from the published package: gateco 1.8.1 depends on mcp@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
gemini - Earlier Revisionhoutini-ai
Distributed as npm:@houtini/gemini-mcp. Resolved from the published package: @houtini/gemini-mcp 2.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
gemini-mcp - Earlier Revisionchrischall
Distributed as npm:@chrischall/gemini-mcp. Resolved from the published package: @chrischall/gemini-mcp 1.7.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.
-
gemini-mcp - Earlier RevisionRLabs-Inc
Distributed as npm:@rlabs-inc/gemini-mcp. Resolved from the published package: @rlabs-inc/gemini-mcp 0.8.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.
-
GEML - a plain-text document format built to be edited in place, one section at a time - Spec Support Unverifiedgeml-spec
Distributed as npm:@geml/geml. Spec revision support not yet verified.
-
genexus - Spec Support Unverifiedlennix1337
Distributed as npm:genexus-mcp. Spec revision support not yet verified.
- gently - Earlier Revision
gently.is
Listed with a remote endpoint. Resolved from the published package: @gently/mcp-server 0.1.22 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ghl-command - Earlier Revisiondrjerryrelth
Distributed as npm:@elitedcs/ghl-mcp. Resolved from the published package: @elitedcs/ghl-mcp 3.67.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.
-
GitHits - Earlier Revisiongithits.com
Listed with a remote endpoint. Resolved from the published package: githits 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.
-
GitHub MCP Server - Current Spec VerifiedGitHub
GitHub's first-party MCP server: a GitHub-hosted remote endpoint at api.githubcopilot.com/mcp/ (OAuth, or a personal access token) plus a local Docker distribution over stdio. Toolsets cover repositories, issues, pull requests, and code analysis. Supports the stateless 2026-07-28 revision, shipped ahead of the revision's release on the official Go SDK.
-
GitLab MCP Server - Earlier RevisionGitLab
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 Revisionzereight
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.
-
gitworthy - Earlier Revisiontrippyogi
Distributed as npm:gitworthy. Resolved from the published package: gitworthy 0.4.0 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Giveaway & Raffle Winner Picker (provably fair) - Earlier Revision
promptcoin.app
Distributed as npm:provably-fair-mcp. Resolved from the published package: provably-fair-mcp 1.0.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.
-
gk-cli - Spec Support Unverifiedgitkraken.com
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).
-
GLM MCP - Earlier Revisiondjerok
Distributed as npm:glm-mcp. Resolved from the published package: glm-mcp 1.3.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.
-
Gmail-MCP-Server - Earlier RevisionArtyMcLabin
Distributed as npm:@artymclabin/gmail-mcp. Resolved from the published package: @artymclabin/gmail-mcp 1.2.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.
-
Godot Agent Loop - Earlier Revisionberemaran
Distributed as npm:@beremaran/godot-agent-loop. Resolved from the published package: @beremaran/godot-agent-loop 3.0.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.
-
Godot MCP - Earlier Revisionsatelliteoflove
Distributed as npm:@satelliteoflove/godot-mcp. Resolved from the published package: @satelliteoflove/godot-mcp 4.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.
-
Godot MCP Runtime - Earlier RevisionErodenn
Distributed as npm:godot-mcp-runtime. Resolved from the published package: godot-mcp-runtime 3.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
godot-mcp - Earlier Revisiontomyud1
Distributed as npm:godot-mcp-server. Resolved from the published package: godot-mcp-server 0.5.0 depends on @modelcontextprotocol/sdk@1.25.3, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
gogcli-mcp - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp. Resolved from the published package: gogcli-mcp 2.25.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.
-
gogcli-mcp-classroom - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp-classroom. Resolved from the published package: gogcli-mcp-classroom 2.25.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.
-
gogcli-mcp-docs - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp-docs. Resolved from the published package: gogcli-mcp-docs 2.25.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.
-
gogcli-mcp-drive - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp-drive. Resolved from the published package: gogcli-mcp-drive 2.25.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.
-
gogcli-mcp-sheets - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp-sheets. Resolved from the published package: gogcli-mcp-sheets 2.25.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.
-
gogcli-mcp-slides - Earlier Revisionchrischall
Distributed as npm:gogcli-mcp-slides. Resolved from the published package: gogcli-mcp-slides 2.25.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.
-
gongio-mcp - Earlier RevisionJustinBeckwith
Distributed as npm:gongio-mcp. Resolved from the published package: gongio-mcp 2.0.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.
-
GoodMemory - Current Spec Verifiedhjqcan
Distributed as npm:goodmemory. Resolved from the published package: goodmemory 0.7.5 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
- Google Drive MCP - Spec Support Unverified
Piotr Agier
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.
-
Google Maps MCP Server - Earlier Revisioncablate
Distributed as npm:@cablate/mcp-google-map. Resolved from the published package: @cablate/mcp-google-map 0.0.55 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Google Workspace - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-google-workspace. Resolved from the published package: @mindstone/mcp-server-google-workspace 0.4.1 depends on @modelcontextprotocol/sdk@0.7.0, whose artifact implements 2024-11-05. This records what the artifact implements, not what a deployment negotiates.
- Google Workspace MCP (aaronsb) - Spec Support Unverified
aaronsb
Distributed as npm:@aaronsb/google-workspace-mcp. Community: the publisher is the personal GitHub account aaronsb and the server fronts Google Workspace, which the publisher does not operate. Requires the user's own Google OAuth credentials. No MCP revision statement found (checked 2026-08-27).
-
google-drive - Earlier Revisionus-all
Distributed as npm:@us-all/google-drive-mcp. Resolved from the published package: @us-all/google-drive-mcp 1.15.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- google-flights - Earlier Revision
pulsemcp.com
Distributed as npm:google-flights-mcp-server. Resolved from the published package: google-flights-mcp-server 0.2.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
google-health-mcp - Earlier Revisiondavidmosiah
Distributed as npm:google-health-mcp-unofficial. Resolved from the published package: google-health-mcp-unofficial 0.7.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
google-surf-mcp - Earlier RevisionHarimxChoi
Distributed as npm:google-surf-mcp. Resolved from the published package: google-surf-mcp 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.
-
gossipcat - Earlier Revisionataberk-xyz
Distributed as npm:gossipcat. Resolved from the published package: gossipcat 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.
-
gpt-4o-image-mcp - Earlier Revisionrunapi-builder
Distributed as npm:@runapi.ai/gpt-4o-image-mcp. Resolved from the published package: @runapi.ai/gpt-4o-image-mcp 0.1.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
gpt-image-2-mcp - Earlier Revisionrunapi-builder
Distributed as npm:@runapi.ai/gpt-image-2-mcp. Resolved from the published package: @runapi.ai/gpt-image-2-mcp 0.1.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
gpt-image-mcp - Earlier Revisionrunapi-builder
Distributed as npm:@runapi.ai/gpt-image-mcp. Resolved from the published package: @runapi.ai/gpt-image-mcp 0.1.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
groundtruth - Earlier Revisionrm-rf-prod
Distributed as npm:@groundtruth-mcp/gt-mcp. Resolved from the published package: @groundtruth-mcp/gt-mcp 7.5.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.
-
growthbook-mcp - Earlier Revisiongrowthbook
Distributed as npm:@growthbook/mcp. Resolved from the published package: @growthbook/mcp 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.
-
gsc - Earlier Revisionmikusnuz
Distributed as npm:@mikusnuz/gsc-mcp. Resolved from the published package: @mikusnuz/gsc-mcp 1.3.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.
- Guardian Engine - Earlier Revision
kaimeilabs.dev
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Guesty MCP Server - Spec Support UnverifiedDLJRealty
Distributed as npm:guesty-mcp-server. Spec revision support not yet verified.
-
Haptic Paper - Earlier Revisionhapticpaper.com
Listed with a remote endpoint. Resolved from the published package: @hapticpaper/mcp-server 1.0.62 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Hash Generator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Help Scout MCP Server - Earlier Revisiondrewburchfield
Distributed as npm:help-scout-mcp-server. Resolved from the published package: help-scout-mcp-server 2.1.0 depends on @modelcontextprotocol/sdk@1.27.1, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Hera Agent Unity - Spec Support UnverifiedNotNull92
Distributed as npm:hera-agent-unity. Spec revision support not yet verified.
-
Hermoso - Earlier Revisionhermoso-ai
Listed with a remote endpoint. Resolved from the published package: hermoso 0.1.114 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
hetzner - Earlier Revisionlazyants
Distributed as npm:@lazyants/hetzner-mcp-server. Resolved from the published package: @lazyants/hetzner-mcp-server 2.3.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.
-
Hevy MCP Server - Current Spec Verifiedchrisdoc
Distributed as npm:hevy-mcp. Resolved from the published package: hevy-mcp 6.1.4 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
hilan-mcp - Earlier Revisionudah1
Distributed as npm:hilan-mcp. Resolved from the published package: hilan-mcp 0.3.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.
-
HOI4 Agent Tools - Earlier RevisionklimPaskov
Distributed as npm:hoi4-agent-tools. Resolved from the published package: hoi4-agent-tools 2.5.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Holdings - Earlier Revisiongetholdings.com
Listed with a remote endpoint. Resolved from the published package: @getholdings/mcp 0.3.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.
- homebutler - Current Spec Verified
SangheeSon
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.
-
Homespun - Earlier Revisionhomespun.dev
Listed with a remote endpoint. Resolved from the published package: @homespunapps/mcp 1.6.64 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
honeybook-mcp - Earlier Revisionchrischall
Distributed as npm:honeybook-mcp. Resolved from the published package: honeybook-mcp 0.4.6 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 RevisionHostinger
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.
-
HTML to Markdown API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
HTTP Headers Analyzer API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
HubSpot - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-hubspot. Resolved from the published package: @mindstone/mcp-server-hubspot 0.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.
-
Huly MCP - Spec Support Unverifieddearlordylord
Distributed as npm:@firfi/huly-mcp. Spec revision support not yet verified.
-
Humaans - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-humaans. Resolved from the published package: @mindstone/mcp-server-humaans 0.3.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.
-
human-survey - Earlier Revisionsunsiyuan
Distributed as npm:humansurvey-mcp. Resolved from the published package: humansurvey-mcp 1.2.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.
-
Hyperliquid Perp Market Data API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
ibanforge - Earlier Revisioncammac-creator
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Identity Forge - Earlier Revisionidentityforge.io
Distributed as npm:identityforge. Resolved from the published package: identityforge 0.4.6 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Ignite UI MCP Server - Earlier RevisionInfragistics (Ignite UI)
Distributed as npm:@igniteui/mcp-server. Resolved from the published package: @igniteui/mcp-server 15.5.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.
-
Ignite UI Theming MCP Server - Spec Support UnverifiedInfragistics (Ignite UI)
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.
- ikeytz - Schlüsseldienst Ludwigsburg - Earlier Revision
ikeytz - Schlüsseldienst Ludwigsburg
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.
-
illustrator-mcp-server - Earlier Revisionie3jp
Distributed as npm:illustrator-mcp-server. Resolved from the published package: illustrator-mcp-server 1.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Image Reader MCP - Earlier RevisionSylphxAI
Distributed as npm:@sylphx/image-reader-mcp. Resolved from the published package: @sylphx/image-reader-mcp 0.1.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
imap-mcp-server - Earlier Revisionnikolausm
Distributed as npm:imap-mcp-server. Resolved from the published package: imap-mcp-server 2.0.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.
-
Infimium - Earlier Revisionaryankumar06
Distributed as npm:infimium. Resolved from the published package: infimium 0.5.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Infrawise - Earlier Revision
Sidd27
Distributed as npm:infrawise. Resolved from the published package: infrawise 0.27.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.
-
InsForge - Earlier RevisionInsForge
Listed with a remote endpoint. Resolved from the published package: @insforge/mcp 1.2.11 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
insightsentry_mcp - Earlier Revisionrezmeplxrf
Distributed as npm:@insightsentry/mcp. Resolved from the published package: @insightsentry/mcp 1.4.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.
-
IP Geolocation API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
iterminal - Earlier RevisioniTophua
Distributed as npm:iterminal-mcp-server. Resolved from the published package: iterminal-mcp-server 2.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
ITM Platform - Earlier Revisionitmplatform
Listed with a remote endpoint. Resolved from the published package: @itm-platform/mcp-server 1.0.20 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- IWE - Spec Support Unverified
IWE
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.
-
Jacobian - Spec Support Unverifiedmorluto
Distributed as npm:jacobian. Spec revision support not yet verified.
-
jamgate - Earlier Revisionamirj4m
Distributed as npm:jamgate. Resolved from the published package: jamgate 1.0.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.
-
janusmcp - Spec Support UnverifiedBayway
Distributed as npm:@bayway/janusmcp. Spec revision support not yet verified.
-
jshookmcp - Earlier Revisionvmoranv
Distributed as npm:@jshookmcp/jshook. Resolved from the published package: @jshookmcp/jshook 0.3.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Judges Panel - Earlier RevisionKevinRabun
Distributed as npm:@kevinrabun/judges. Resolved from the published package: @kevinrabun/judges 3.129.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
JustHandled Agent Utility Gateway - Earlier Revisionjusthandledlabs
Distributed as npm:@justhandledlabs/agent-client. Resolved from the published package: @justhandledlabs/agent-client 0.11.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.
-
JWT Decoder API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
- kage - Earlier Revision
kage-core.com
Distributed as npm:@kage-core/kage-graph-mcp. Resolved from the published package: @kage-core/kage-graph-mcp 3.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.
- kai - Spec Support Unverified
kailayerhq
Distributed as npm:kai-mcp. Spec revision support not yet verified.
-
kaneo - Earlier Revisionusekaneo
Distributed as npm:@kaneo/mcp. Resolved from the published package: @kaneo/mcp 0.1.11 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
kcp-agent - KCP navigation planner - Spec Support Unverifiedcantara.no
Distributed as npm:kcp-agent. Spec revision support not yet verified.
-
kcp-harness - KCP compliance proxy - Spec Support Unverifiedcantara.no
Distributed as npm:kcp-harness. Spec revision support not yet verified.
-
Keyword Research API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
kiaaccess-mcp - Earlier Revisionchrischall
Distributed as npm:kiaaccess-mcp. Resolved from the published package: kiaaccess-mcp 0.6.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.
-
KiCad MCP Pro - Earlier Revisionoaslananka
Distributed as pypi:kicad-mcp-pro. Resolved from the published package: kicad-mcp-pro 3.32.0 depends on mcp@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Kin - Spec Support Unverifiedkinlab.ai
Distributed as npm:@kinlab/kin-mcp. Spec revision support not yet verified.
- Kiprio MCP Server - Spec Support Unverified
kiprio.com
Distributed as pypi:kiprio-mcp. Spec revision support not yet verified.
-
Kiwoom Securities MCP Server - Earlier RevisionChunSam
Distributed as npm:kiwoom-mcp-server. Resolved from the published package: kiwoom-mcp-server 0.52.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.
-
korean-elementary-learning-map-mcp - Earlier Revisiontaehyeonglim
Distributed as npm:korean-elementary-learning-map-mcp. Resolved from the published package: korean-elementary-learning-map-mcp 0.5.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.
-
kubernetes-mcp-server - Spec Support Unverifiedcontainers
Distributed as npm:kubernetes-mcp-server. Hand check 2026-08-25: no MCP revision statement in README or docs; go.mod pins modelcontextprotocol/go-sdk v1.7.0, which can prove capability but never a served revision (2026-07-28 support there is conditional on StreamableHTTPOptions.Stateless). Native Go binary; the npm package is a wrapper.
-
Labby - Spec Support Unverifieddinglebear.ai
Distributed as npm:@dinglebear/labby. Spec revision support not yet verified.
-
langcare-mcp-fhir - Spec Support Unverifiedlangcare
Distributed as npm:@langcare/langcare-mcp-fhir. Spec revision support not yet verified.
-
Language Detector API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
lighthouse-mcp - Earlier Revisionpriyankark
Distributed as npm:lighthouse-mcp. Resolved from the published package: lighthouse-mcp 0.1.15 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
livepilot - Spec Support Unverifieddreamrec
Distributed as npm:livepilot. Spec revision support not yet verified.
-
livetennisapi-mcp - Earlier Revisionlivetennisapi
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
llmtrim - Spec Support Unverifiedfkiene
Distributed as npm:@llmtrim/cli. Spec revision support not yet verified.
-
lm - Earlier Revisionhoutini-ai
Distributed as npm:@houtini/lm. Resolved from the published package: @houtini/lm 3.2.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.
-
Local Memory - Earlier Revisionstudiomeyer-io
Distributed as npm:@studiomeyer/local-memory-mcp. Resolved from the published package: @studiomeyer/local-memory-mcp 2.4.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.
-
Local YDB MCP - Earlier Revisionastandrik
Distributed as npm:@astandrik/local-ydb-mcp. Resolved from the published package: @astandrik/local-ydb-mcp 0.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.
-
localstack-mcp-server - Spec Support Unverifiedlocalstack
Distributed as npm:@localstack/localstack-mcp-server. Spec revision support not yet verified.
-
logi-approval - Earlier Revision1pass.dev
Distributed as npm:@logi-auth/mcp-approval. Resolved from the published package: @logi-auth/mcp-approval 0.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
loki-mode - Spec Support Unverifiedasklokesh
Distributed as npm:loki-mode. Hand check 2026-08-25: no MCP revision statement in README, CHANGELOG or mcp/server.py; the Python adapter requires mcp>=1.0.0,<2.0.0, an ambiguous range spanning SDK eras. MCP is one interface of a multi-agent SDLC framework (36 tools via loki mcp).
-
Lokka - Earlier Revisionjozrahq
Distributed as npm:@merill/lokka. Resolved from the published package: @merill/lokka 2.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Lunch Money - Earlier Revisionakutishevsky
Distributed as npm:@akutishevsky/lunchmoney-mcp. Resolved from the published package: @akutishevsky/lunchmoney-mcp 3.0.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.
- Lune Research - Earlier Revision
luneresearch.com
Listed with a remote endpoint. Resolved from the published package: @retrograde-labs/lune-mcp-server 2.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
m1nd - Spec Support Unverifiedmaxkle1nz
Distributed as npm:@maxkle1nz/m1nd. Spec revision support not yet verified.
-
Madar - Spec Support Unverifiedmohanagy
Distributed as npm:@lubab/madar. Spec revision support not yet verified.
-
madeonsol - Earlier RevisionMadeOnSol
Distributed as npm:mcp-server-madeonsol. Resolved from the published package: mcp-server-madeonsol 1.24.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.
-
Mailtrap MCP Server - Earlier RevisionMailtrap
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.
-
makers-page-mcp - Earlier Revisionalexcloudstar
Distributed as npm:makers-page-mcp. Resolved from the published package: makers-page-mcp 0.4.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.
-
MAL MCP Server - Current Spec VerifiedGrinv
Distributed as npm:mal-mcp. Resolved from the published package: mal-mcp 0.9.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
Markdown Renderer API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Markdown to HTML API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
- marketnow - Earlier Revision
edgarfloresguerra2011-a11y
Distributed as npm:marketnow-mcp. Resolved from the published package: marketnow-mcp 1.10.0 depends on @modelcontextprotocol/sdk@0.5.0, whose artifact implements 2024-11-05. This records what the artifact implements, not what a deployment negotiates.
-
marrow - Spec Support Unverifiedgetmarrow
Distributed as npm:@getmarrow/mcp. Spec revision support not yet verified.
-
mcp - Earlier Revisionaicommander.dev
Listed with a remote endpoint. Resolved from the published package: @aicommander/mcp 1.0.55 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisionapideck.com
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
mcp - Earlier Revisionbykaranteli.com
Distributed as npm:bykaranteli-mcp. Resolved from the published package: bykaranteli-mcp 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.
-
mcp - Earlier Revisionclipy.online
Distributed as npm:@clipy/mcp. Resolved from the published package: @clipy/mcp 0.13.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.
-
mcp - Earlier Revisionpushinpay.com.br
Distributed as npm:@pushinpaybr/mcp-server. Resolved from the published package: @pushinpaybr/mcp-server 0.1.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.
-
mcp - Earlier Revisionfluf.io
Distributed as npm:fluf-mcp. Resolved from the published package: fluf-mcp 0.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revision2s-io
Distributed as npm:@2sio/mcp. Resolved from the published package: @2sio/mcp 1.81.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.
-
mcp - Earlier Revisionagenticmail
Distributed as npm:@agenticmail/mcp. Resolved from the published package: @agenticmail/mcp 0.9.29 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisiondiscourse
Distributed as npm:@discourse/mcp. Resolved from the published package: @discourse/mcp 0.2.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisionextensiondev
Distributed as npm:@extension.dev/mcp. Resolved from the published package: @extension.dev/mcp 10.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.
-
mcp - Earlier Revisionflorentine-ai
Distributed as npm:@florentine-ai/mcp. Resolved from the published package: @florentine-ai/mcp 1.0.0 depends on @modelcontextprotocol/sdk@1.27.1, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisionpictify-io
Listed with a remote endpoint. Resolved from the published package: @pictify/mcp-server 1.5.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.
-
mcp - Earlier RevisionQVerisAI
Distributed as npm:@qverisai/mcp. Resolved from the published package: @qverisai/mcp 0.14.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.
-
mcp - Earlier Revisionsapiom
Distributed as npm:@sapiom/mcp. Resolved from the published package: @sapiom/mcp 0.12.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisionwebdriverio
Distributed as npm:@wdio/mcp. Resolved from the published package: @wdio/mcp 3.11.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.
-
mcp - Spec Support Unverifiedinfobip.com
Listed with a remote endpoint. Spec revision support not yet verified.
- mcp - Earlier Revision
keboola.com
Listed with a remote endpoint. Resolved from the published package: keboola-mcp-server 1.74.6 depends on mcp@1.28.1, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp - Earlier Revisionnestr.io
Listed with a remote endpoint. Resolved from the published package: @nestr/mcp 0.1.97 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-abap-adt - Earlier Revisionfr0ster
Distributed as npm:@mcp-abap-adt/core. Resolved from the published package: @mcp-abap-adt/core 8.13.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.
-
mcp-accessibility-scanner - Current Spec VerifiedJustasMonkev
Distributed as npm:mcp-accessibility-scanner. Resolved from the published package: mcp-accessibility-scanner 3.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.
-
mcp-address-history - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-address-history. Resolved from the published package: @cryptoapis-io/mcp-address-history 0.3.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.
-
mcp-adr-analysis-server - Earlier Revisiontosin2013
Distributed as npm:mcp-adr-analysis-server. Resolved from the published package: mcp-adr-analysis-server 2.6.14 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-animenewsnetwork - Earlier Revisionsmeet666
Distributed as npm:mcp-animenewsnetwork. Resolved from the published package: mcp-animenewsnetwork 1.2.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.
-
mcp-arr - Earlier Revisionaplaceforallmystuff
Distributed as npm:mcp-arr-server. Resolved from the published package: mcp-arr-server 1.7.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.
-
mcp-bastion - Earlier RevisionGowthaman90
Distributed as npm:mcp-bastion. Resolved from the published package: mcp-bastion 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.
-
mcp-blockchain-events - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-blockchain-events. Resolved from the published package: @cryptoapis-io/mcp-blockchain-events 0.4.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.
-
mcp-blockchain-fees - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-blockchain-fees. Resolved from the published package: @cryptoapis-io/mcp-blockchain-fees 0.4.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.
-
mcp-broadcast - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-broadcast. Resolved from the published package: @cryptoapis-io/mcp-broadcast 0.4.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.
-
mcp-devkit-server - Earlier Revisionmapbox
Listed with a remote endpoint. Resolved from the published package: @mapbox/mcp-devkit-server 0.8.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-gads - Earlier Revisionpijusz
Distributed as npm:mcp-gads. Resolved from the published package: mcp-gads 0.10.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-graphql-enhanced - Earlier Revisionletoribo
Distributed as npm:@letoribo/mcp-graphql-enhanced. Resolved from the published package: @letoribo/mcp-graphql-enhanced 4.14.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.
-
mcp-gsc - Earlier Revisionpijusz
Distributed as npm:mcp-gsc. Resolved from the published package: mcp-gsc 0.3.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-gsheets - Earlier Revisionfreema
Distributed as npm:mcp-gsheets. Resolved from the published package: mcp-gsheets 1.10.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-hd-wallet - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-hd-wallet. Resolved from the published package: @cryptoapis-io/mcp-hd-wallet 0.3.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.
-
mcp-image - Earlier Revisionshinpr
Distributed as npm:mcp-image. Resolved from the published package: mcp-image 0.12.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-jira-stdio - Earlier Revisionfreema
Distributed as npm:mcp-jira-stdio. Resolved from the published package: mcp-jira-stdio 1.11.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.
-
mcp-local-rag - Earlier Revisionshinpr
Distributed as npm:mcp-local-rag. Resolved from the published package: mcp-local-rag 0.17.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.
-
mcp-lrclib - Earlier Revisionsmeet666
Distributed as npm:mcp-lrclib. Resolved from the published package: mcp-lrclib 1.5.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.
-
mcp-lyricscom - Earlier Revisionsmeet666
Distributed as npm:mcp-lyricscom. Resolved from the published package: mcp-lyricscom 1.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.
-
mcp-marmiton - Earlier Revisionsmeet666
Distributed as npm:mcp-marmiton. Resolved from the published package: mcp-marmiton 1.8.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.
-
mcp-metacritic - Earlier Revisionsmeet666
Distributed as npm:mcp-metacritic. Resolved from the published package: mcp-metacritic 1.2.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.
-
mcp-observatory - Earlier RevisionKryptosAI
Distributed as npm:@kryptosai/mcp-observatory. Resolved from the published package: @kryptosai/mcp-observatory 1.41.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.
- mcp-omnisearch - Spec Support Unverified
Scott Spence
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-prepare-transactions - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-prepare-transactions. Resolved from the published package: @cryptoapis-io/mcp-prepare-transactions 0.4.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.
-
mcp-probe-kit - Current Spec Verifiedmybolide
Distributed as npm:mcp-probe-kit. Resolved from the published package: mcp-probe-kit 4.0.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
mcp-seatbelt - Spec Support UnverifiedKryptosAI
Distributed as npm:@kryptosai/mcp-seatbelt. Spec revision support not yet verified.
-
mcp-server - Earlier Revisionextentos.com
Distributed as npm:@extentos/mcp-server. Resolved from the published package: @extentos/mcp-server 0.11.60 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server - Earlier Revisionaibtcdev
Distributed as npm:@aibtc/mcp-server. Resolved from the published package: @aibtc/mcp-server 1.68.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.
-
mcp-server - Earlier Revisioncap-js
Distributed as npm:@cap-js/mcp-server. Resolved from the published package: @cap-js/mcp-server 0.0.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server - Earlier Revisionconfigcat
Distributed as npm:@configcat/mcp-server. Resolved from the published package: @configcat/mcp-server 0.1.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server - Earlier Revisioncontextium-io
Distributed as npm:@contextium/mcp-server. Resolved from the published package: @contextium/mcp-server 1.10.12 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server - Earlier Revisioniris-eval
Distributed as npm:@iris-eval/mcp-server. Resolved from the published package: @iris-eval/mcp-server 0.5.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.
-
mcp-server - Earlier Revisionmapbox
Listed with a remote endpoint. Resolved from the published package: @mapbox/mcp-server 0.14.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.
-
mcp-server - Earlier RevisionOilpriceAPI
Distributed as npm:oilpriceapi-mcp. Resolved from the published package: oilpriceapi-mcp 3.2.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.
-
mcp-server - Earlier Revisionroamzy-io
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
mcp-server - Spec Support Unverifiedtelleroutlook
Distributed as npm:@wasmagent/mcp-server. Spec revision support not yet verified.
-
mcp-server - Earlier RevisionUI5
Distributed as npm:@ui5/mcp-server. Resolved from the published package: @ui5/mcp-server 0.2.18 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server - Earlier RevisionUpstash
Distributed as npm:@upstash/mcp-server. Resolved from the published package: @upstash/mcp-server 0.2.7 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- mcp-server - Earlier Revision
vectros-ai
Distributed as npm:@vectros-ai/mcp-server. Resolved from the published package: @vectros-ai/mcp-server 0.15.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.
-
mcp-server - Earlier Revisionsocialneuron.com
Distributed as npm:@socialneuron/mcp-server. Resolved from the published package: @socialneuron/mcp-server 2.0.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.
-
mcp-server-auth - Earlier RevisionTotesMagotes
Distributed as npm:@expensebot/mcp-server-auth. Resolved from the published package: @expensebot/mcp-server-auth 0.6.22 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server-browserbase - Earlier Revisionbrowserbase
Distributed as npm:@browserbasehq/mcp-server-browserbase. Resolved from the published package: @browserbasehq/mcp-server-browserbase 2.4.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.
-
mcp-server-chart - Earlier Revisionantvis
Distributed as npm:@antv/mcp-server-chart. Resolved from the published package: @antv/mcp-server-chart 0.9.10 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server-scf - Earlier Revisionscfcontrolsplatform.app
Distributed as npm:mcp-server-scf. Resolved from the published package: mcp-server-scf 2.0.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.
-
mcp-server-sfmc - Earlier RevisionJoernBerkefeld
Distributed as npm:mcp-server-sfmc. Resolved from the published package: mcp-server-sfmc 2.9.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.
-
mcp-server-tauri - Earlier Revisionhypothesi
Distributed as npm:@hypothesi/tauri-mcp-server. Resolved from the published package: @hypothesi/tauri-mcp-server 0.12.0 depends on @modelcontextprotocol/sdk@0.6.1, whose artifact implements 2024-11-05. This records what the artifact implements, not what a deployment negotiates.
-
mcp-server-trello - Earlier Revisiondelorenj
Distributed as npm:@delorenj/mcp-server-trello. Resolved from the published package: @delorenj/mcp-server-trello 1.8.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.
-
mcp-simulate - Earlier RevisionCryptoAPIs-io
Distributed as npm:@cryptoapis-io/mcp-simulate. Resolved from the published package: @cryptoapis-io/mcp-simulate 0.3.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.
-
mcp-sitecore-server - Earlier RevisionAntonytm
Distributed as npm:@antonytm/mcp-sitecore-server. Resolved from the published package: @antonytm/mcp-sitecore-server 1.4.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- mcp-ssh-manager - Spec Support Unverified
Jérémy Christillin
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.
-
mcp-uptime-kuma - Earlier RevisionDavidFuchs
Distributed as npm:@davidfuchs/mcp-uptime-kuma. Resolved from the published package: @davidfuchs/mcp-uptime-kuma 0.11.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mcp-whoisxmlapi - Spec Support Unverifiedwhois-api-llc
Distributed as npm:@whoisxmlapidotcom/mcp-whoisxmlapi. Spec revision support not yet verified.
-
mcp-wikibooks-cookbook - Earlier Revisionsmeet666
Distributed as npm:mcp-wikibooks-cookbook. Resolved from the published package: mcp-wikibooks-cookbook 1.3.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.
-
mcpcap - Spec Support Unverifiedmcpcap
MCP server for analyzing PCAP network capture files, distributed on PyPI and run locally. Registry record and PyPI agree on 0.9.6. Hand check 2026-08-25: no MCP revision statement in README, docs or release notes; PyPI requires fastmcp>=2.12.2,<2.15.0, a third-party framework the SDK chain does not cover. Last release v0.9.6 on 2026-03-17.
- MCPHub - Spec Support Unverified
Saman
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.
-
mdedit.ai - Earlier Revisionmangoappstudio
Listed with a remote endpoint. Resolved from the published package: @mdedit/mcp-server 0.2.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
mdk-mcp-server - Earlier RevisionSAP
Distributed as npm:@sap/mdk-mcp-server. Resolved from the published package: @sap/mdk-mcp-server 0.4.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.
-
MediaWiki MCP Server - Spec Support UnverifiedProfessionalWiki
Distributed as mcpb:https://github.com/ProfessionalWiki/MediaWiki-MCP-Server/releases/download/v0.16.0/MediaWiki-MCP-Server.mcpb. Spec revision support not yet verified.
-
Meertrack - Earlier Revisionmeertrack.com
Listed with a remote endpoint. Resolved from the published package: @meertrack/mcp 2.2.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.
-
melta UI - Earlier Revisiontsubotax
Distributed as npm:melta-ds-mcp. Resolved from the published package: melta-ds-mcp 1.6.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.
-
memoir - Earlier Revisioncamgitt
Distributed as npm:memoir-cli. Resolved from the published package: memoir-cli 3.12.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.
-
Memorix - Earlier RevisionAVIDS2
Distributed as npm:memorix. Resolved from the published package: memorix 1.7.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
memory - Earlier RevisionVelixarAi
Distributed as npm:velixar-mcp-server. Resolved from the published package: velixar-mcp-server 1.6.6 depends on @modelcontextprotocol/sdk@1.21.0, whose artifact implements 2025-06-18. This records what the artifact implements, not what a deployment negotiates.
-
memorykit - Earlier Revisionrapozoantonio
Distributed as npm:memorykit-mcp-server. Resolved from the published package: memorykit-mcp-server 1.4.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
memorylens-mcp - Spec Support UnverifiedMarcelRoozekrans
Distributed as npm:memorylens-mcp. Spec revision support not yet verified.
-
mendapi - Spec Support Unverifiedmendapi.com
Distributed as npm:mendapi. Spec revision support not yet verified.
-
mergewarden - Earlier Revisionsjh9714
Distributed as npm:mergewarden-mcp. Resolved from the published package: mergewarden-mcp 0.10.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.
-
meta - Earlier Revisionmikusnuz
Distributed as npm:@mikusnuz/meta-mcp. Resolved from the published package: @mikusnuz/meta-mcp 2.1.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.
-
meta-ads - Earlier Revisionmikusnuz
Distributed as npm:@mikusnuz/meta-ads-mcp. Resolved from the published package: @mikusnuz/meta-ads-mcp 1.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.
-
Metro MCP - Earlier Revisionsteve228uk
Distributed as npm:metro-mcp. Resolved from the published package: metro-mcp 0.13.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
microcharts - Earlier Revisionganapativs
Distributed as npm:@microcharts/mcp. Resolved from the published package: @microcharts/mcp 0.1.16 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Microsoft 365 Calendar - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-microsoft-calendar. Resolved from the published package: @mindstone/mcp-server-microsoft-calendar 0.2.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.
-
Microsoft 365 Files - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-microsoft-files. Resolved from the published package: @mindstone/mcp-server-microsoft-files 0.2.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.
-
Microsoft 365 Mail - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-microsoft-mail. Resolved from the published package: @mindstone/mcp-server-microsoft-mail 0.3.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.
-
Microsoft 365 MCP Server - Earlier RevisionSofteria
Distributed as npm:@softeria/ms-365-mcp-server. Resolved from the published package: @softeria/ms-365-mcp-server 0.145.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.
-
Microsoft 365 SharePoint - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-microsoft-sharepoint. Resolved from the published package: @mindstone/mcp-server-microsoft-sharepoint 0.2.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.
- Microsoft Advertising MCP Server - Spec Support Unverified
Microsoft
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.
-
Microsoft Fabric MCP Server - Spec Support UnverifiedMicrosoft
Distributed as nuget:Microsoft.Fabric.Mcp. Spec revision support not yet verified.
-
Microsoft Teams API - Earlier RevisionMaxim-Mazurok
Distributed as npm:teams-api. Resolved from the published package: teams-api 1.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Mindwtr - Spec Support Unverifieddongdongbh
Distributed as npm:mindwtr-mcp. Spec revision support not yet verified.
-
mirroir-mcp - Spec Support Unverifiedjfarcand
Distributed as npm:mirroir-mcp. Spec revision support not yet verified.
-
Mneme - Spec Support Unverifiedpatsa2561-art
Distributed as npm:mneme-ai. Spec revision support not yet verified.
-
Mnemoverse Memory - Earlier Revisionmnemoverse
Listed with a remote endpoint. Resolved from the published package: @mnemoverse/mcp-memory-server 0.8.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.
-
mobai-mcp - Earlier RevisionMobAI-App
Distributed as npm:mobai-mcp. Resolved from the published package: mobai-mcp 2.6.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 Device MCP - Earlier Revisionsrmorete
Distributed as npm:@srmorete/mobile-device-mcp. Resolved from the published package: @srmorete/mobile-device-mcp 0.1.10 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 RevisionMobile Next
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.
-
Modellix Agent Canvas - Earlier RevisionModellix
Distributed as npm:@modellix/agent-canvas. Resolved from the published package: @modellix/agent-canvas 0.1.17 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
MongoDB MCP Server - Earlier RevisionMongoDB
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.
- MSSQL MCP Reader - Spec Support Unverified
ConnorBritain
Distributed as npm:@connorbritain/mssql-mcp-reader. Community: the publisher is the personal GitHub account ConnorBritain and the server fronts Microsoft SQL Server, which the publisher does not operate. The read-only tier of the publisher's two-package split. Registry record (v0.3.1, updated 2026-02-18) trails npm (0.6.1, 2026-08-04). No MCP revision statement found (checked 2026-08-27).
- MSSQL MCP Server (ConnorBritain) - Spec Support Unverified
ConnorBritain
Distributed as npm:@connorbritain/mssql-mcp-server. Community: the publisher is the personal GitHub account ConnorBritain and the server fronts Microsoft SQL Server, which the publisher does not operate. The registry record (v0.4.5, updated 2026-02-18) trails npm (0.7.0, 2026-08-04) by three minor versions. No MCP revision statement found in the README (checked 2026-08-27).
-
MTG MCP Server - Spec Support Unverifiedj4th
Distributed as pypi:mtg-mcp-server. Spec revision support not yet verified.
-
mulmocast-vision - Earlier Revisionisamu
Distributed as npm:mulmocast-vision. Resolved from the published package: mulmocast-vision 1.0.12 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
musescore-mcp - Earlier Revisionchrischall
Distributed as npm:@chrischall/musescore-mcp. Resolved from the published package: @chrischall/musescore-mcp 0.15.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.
-
Mux MCP Server - Earlier RevisionMux
Mux's official MCP server for its video API. A 2026-08-14 probe of mcp.mux.com rejected 2026-07-28 by name (supported versions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) and completed a legacy initialize handshake at 2025-11-25, answering as serverInfo "mux" 14.1.0. Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
mzizi-mcp - Earlier Revisionnyuchi
Listed with a remote endpoint. Resolved from the published package: @nyuchi/mzizi-mcp 0.9.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.
-
n8n MCP Community - Earlier Revisiondrzamarian
Distributed as npm:n8n-mcp-community. Resolved from the published package: n8n-mcp-community 0.3.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.
-
Nano Banana - Earlier Revisionmindstone
Distributed as npm:@mindstone/mcp-server-nano-banana. Resolved from the published package: @mindstone/mcp-server-nano-banana 0.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.
- nano-pay - Current Spec Verified
feeless402.com
Distributed as pypi:feeless402. Resolved from the published package: feeless402 0.2.3 depends on mcp@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
Nauro - Earlier Revisionnauro.ai
Distributed as pypi:nauro. Resolved from the published package: nauro 1.14.1 depends on mcp@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
NEAT - Earlier Revisionneat-technologies
Distributed as npm:@neat.is/mcp. Resolved from the published package: @neat.is/mcp 0.9.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.
-
Netlify MCP Server - Current Spec VerifiedNetlify
Netlify's first-party MCP server, distributed as the npm package @netlify/mcp and documented for stdio use. Netlify's engineering blog states the server already supports the 2026-07-28 specification. A remote endpoint is named in that blog post but is absent from both the docs and the repository README, so it is not recorded here as a verified endpoint.
-
neurodivergent-memory - Earlier Revisionjmeyer1980
Distributed as npm:neurodivergent-memory. Resolved from the published package: neurodivergent-memory 0.3.9 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- NEXO Brain - Spec Support Unverified
Wazion Apps
Distributed as npm:nexo-brain. First-party: the package is the local runtime core of the publisher's own NEXO Desktop product, per the repository's own statement. The registry record (v1.5.2, updated 2026-03-29) trails npm (7.38.7, 2026-06-28) by six major versions. No MCP revision statement found (checked 2026-08-27).
-
next-devtools-mcp - Earlier RevisionVercel
Distributed as npm:next-devtools-mcp. Resolved from the published package: next-devtools-mcp 0.4.0 depends on @modelcontextprotocol/sdk@1.25.2, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
next-finance - Earlier Revisionpaivapiovesan
Distributed as npm:next-finance-mcp. Resolved from the published package: next-finance-mcp 0.9.151 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
nextjs-cache-handler-mcp - Earlier Revisionleejpsd
Distributed as npm:@leejpsd/nextjs-cache-handler-mcp. Resolved from the published package: @leejpsd/nextjs-cache-handler-mcp 0.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
nexus-legal - Earlier Revisiondjtellado
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
NFT Metadata API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
NotebookLM MCP - Earlier Revisionroomi-fields
Distributed as npm:@roomi-fields/notebooklm-mcp. Resolved from the published package: @roomi-fields/notebooklm-mcp 3.0.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.
-
Notion MCP - Current Spec VerifiedNotion
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.
-
notion-mcp-server - Earlier Revisionawkoy
Distributed as npm:notion-mcp-server. Resolved from the published package: notion-mcp-server 2.13.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.
-
npm-sentinel-mcp - Current Spec VerifiedNekzus
Distributed as npm:@nekzus/mcp-server. Resolved from the published package: @nekzus/mcp-server 1.26.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.
-
NVIDIA Elements - Current Spec VerifiedNVIDIA
Distributed as npm:@nvidia-elements/cli. Resolved from the published package: @nvidia-elements/cli 2.1.10 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
observability-mcp - Earlier RevisionThoTischner
Distributed as npm:@thotischner/observability-mcp. Resolved from the published package: @thotischner/observability-mcp 3.9.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Obsidian Brain - Earlier Revisionsweir1
Distributed as npm:obsidian-brain. Resolved from the published package: obsidian-brain 1.7.24 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Obsidian Hybrid Search - Earlier Revisionflowing-abyss
Distributed as npm:obsidian-hybrid-search. Resolved from the published package: obsidian-hybrid-search 0.15.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.
-
obsidian-sync-mcp - Spec Support Unverifiedes617
Distributed as npm:obsidian-sync-mcp. Spec revision support not yet verified.
-
OCR Text Extraction API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
octen-mcp - Earlier RevisionOcten-Team
Distributed as npm:octen-mcp. Resolved from the published package: octen-mcp 0.4.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Octocode MCP - AI Context Platform - Earlier Revisionbgauryy
Distributed as npm:octocode-mcp. Resolved from the published package: octocode-mcp 18.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- oe-mcp - Spec Support Unverified
openenterprise-info
Distributed as npm:@openenterprise/oe-mcp. Spec revision support not yet verified.
-
ofw-mcp - Earlier Revisionchrischall
Distributed as npm:ofw-mcp. Resolved from the published package: ofw-mcp 2.10.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Oh My Posh Configurator - Earlier Revision
jamesmontemagno
Distributed as npm:ohmyposh-configurator. Resolved from the published package: ohmyposh-configurator 1.1.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.
-
omnicord - Earlier RevisionOrygnsCode
Distributed as npm:@orygn/omnicord. Resolved from the published package: @orygn/omnicord 1.3.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.
-
omophub-mcp - Earlier RevisionOMOPHub
Distributed as npm:@omophub/omophub-mcp. Resolved from the published package: @omophub/omophub-mcp 1.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
One - Earlier Revisionwithone.ai
Listed with a remote endpoint. Resolved from the published package: @withone/mcp 1.2.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.
-
one-search-mcp - Earlier Revisionyokingma
Distributed as npm:one-search-mcp. Resolved from the published package: one-search-mcp 1.2.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.
-
onepassword-agent-mcp - Earlier Revisiongambadio
Distributed as npm:onepassword-agent-mcp. Resolved from the published package: onepassword-agent-mcp 0.3.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
OPA MCP - Earlier RevisionOrygnsCode
Distributed as npm:@orygn/opa-mcp. Resolved from the published package: @orygn/opa-mcp 0.3.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.
-
Open State: Camping - Parks Canada - Spec Support UnverifiedJCrossman
Distributed as npm:@open-state/camping. Spec revision support not yet verified.
-
open-compute (computer-use) - Spec Support Unverifiedlukisch
Distributed as npm:open-compute-mcp. Spec revision support not yet verified.
-
openrouter-multimodal - Earlier Revisionstabgan
Distributed as npm:@stabgan/openrouter-mcp-multimodal. Resolved from the published package: @stabgan/openrouter-mcp-multimodal 4.5.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.
-
OpenTakeoff - Earlier RevisionKentucky-ai
Distributed as npm:opentakeoff-mcp. Resolved from the published package: opentakeoff-mcp 0.9.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.
-
Opik MCP Server - Earlier Revisioncomet-ml
Distributed as npm:opik-mcp. Resolved from the published package: opik-mcp 2.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
orchex - Earlier Revisionwundam
Distributed as npm:@wundam/orchex. Resolved from the published package: @wundam/orchex 1.0.0-rc.32 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Òtítọ́ - Spec Support UnverifiedBASHBOP
Distributed as npm:@bashbop/otito. Spec revision support not yet verified.
-
otterkit - Earlier Revisionuseotterkit
Distributed as npm:otterkit. Resolved from the published package: otterkit 0.47.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.
-
outlook-assistant - Earlier Revisionlittlebearapps
Distributed as npm:@littlebearapps/outlook-assistant. Resolved from the published package: @littlebearapps/outlook-assistant 3.9.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.
-
Packwright MCP - Current Spec Verifiedrithwikbabu
Distributed as npm:@rithwikbabu/packwright-mcp. Resolved from the published package: @rithwikbabu/packwright-mcp 0.5.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.
-
pagebolt - Earlier RevisionCustodia-Admin
Distributed as npm:pagebolt-mcp. Resolved from the published package: pagebolt-mcp 1.16.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.
- PageSpeed Insights MCP - Spec Support Unverified
ruslanlap
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.
-
Paparats – Local Semantic Code Search MCP - Spec Support UnverifiedIBazylchuk
Distributed as npm:@paparats/cli. Spec revision support not yet verified.
- paper-mcp - Earlier Revision
MCPServings
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
PAPI: Persistent Adaptive Project Intelligence - Earlier Revisiongetpapi
Listed with a remote endpoint. Resolved from the published package: @papi-ai/server 0.7.83 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Parseable - Earlier Revisionparseablehq
Distributed as npm:@parseable/parseable-mcp-server. Resolved from the published package: @parseable/parseable-mcp-server 0.2.16 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Password Strength Analyzer API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Patchloom - Spec Support Unverifiedpatchloom
Distributed as cargo:patchloom. Spec revision support not yet verified.
-
Paybond MCP Server - Spec Support Unverifiednonameuserd
Distributed as npm:@paybond/kit. Spec revision support not yet verified.
-
Paydirt - Earlier RevisionPaydirt-AI
Distributed as npm:paydirt-mcp. Resolved from the published package: paydirt-mcp 2.3.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.
-
PDF Reader MCP - Spec Support UnverifiedSylphxAI
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.
-
pepita - Earlier Revisionmcp.pepita.dev
Listed with a remote endpoint. Resolved from the published package: @pepitahq/mcp 0.22.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.
-
Person Enrichment API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
photoshop-mcp - Earlier Revisionalisaitteke
Distributed as npm:@alisaitteke/photoshop-mcp. Resolved from the published package: @alisaitteke/photoshop-mcp 1.6.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.
-
pica - Earlier Revisionwithpica
Distributed as npm:@withpica/mcp-server. Resolved from the published package: @withpica/mcp-server 2.95.3 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
PII Detector API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
- pinkpixel-dev-web-scout-mcp - Spec Support Unverified
Pink Pixel
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.
-
pixelcheck - Earlier Revisionxcodethink
Distributed as npm:pixelcheck. Resolved from the published package: pixelcheck 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.
-
Planify - Earlier Revisionplanifyapps.com
Distributed as npm:@planifyapps/mcp. Resolved from the published package: @planifyapps/mcp 0.2.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.
-
PlayByKey Music Theory - Earlier Revisionplaybykey.com
Distributed as npm:@playbykey/theory-mcp. Resolved from the published package: @playbykey/theory-mcp 2.0.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.
-
Playwright MCP - Spec Support UnverifiedMicrosoft
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.
- playwright-stealth - Earlier Revision
pulsemcp.com
Distributed as npm:playwright-stealth-mcp-server. Resolved from the published package: playwright-stealth-mcp-server 0.2.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.
-
plur - Current Spec Verifiedplur-ai
Distributed as npm:@plur-ai/mcp. Resolved from the published package: @plur-ai/mcp 0.18.0 depends on @modelcontextprotocol/server@2.0.0-beta.4, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
pm-claude-skills - Spec Support Unverifiedmohitagw15856
Distributed as npm:pm-claude-skills. Hand check 2026-08-25: the product is a plain-markdown skills library (its README counts 1153 SKILL.md files) with two custom MCP adapters that use no MCP SDK; the stdio adapter echoes the client's requested protocolVersion with a '2024-11-05' fallback, which grounds no revision. No revision statement in docs.
- pointsyeah - Earlier Revision
pulsemcp.com
Distributed as npm:pointsyeah-mcp-server. Resolved from the published package: pointsyeah-mcp-server 0.2.9 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
polarmcp - Earlier Revisiondavidmosiah
Distributed as npm:polar-mcp-unofficial. Resolved from the published package: polar-mcp-unofficial 0.5.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
posterly - Earlier Revisionawpthorp
Listed with a remote endpoint. Resolved from the published package: posterly-mcp-server 0.35.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.
-
postfast-mcp - Earlier Revisionpeturgeorgievv-factory
Distributed as npm:postfast-mcp. Resolved from the published package: postfast-mcp 0.5.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.
-
postman-mcp-server - Earlier Revisionpostman.com
Listed with a remote endpoint. Resolved from the published package: @postman/postman-mcp-server 2.12.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 RevisionMicrosoft
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 MCP Server - Spec Support Unverified
Mervin Praison
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.
-
Prediction Markets API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Prerender Buddy - Earlier Revisionkopachlager
Distributed as npm:@prerenderbuddy/mcp. Resolved from the published package: @prerenderbuddy/mcp 0.1.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
prism-coder - Earlier Revisiondcostenco
Distributed as npm:prism-mcp-server. Resolved from the published package: prism-mcp-server 20.14.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.
- prodlint - Earlier Revision
prodlint
Distributed as npm:prodlint. Resolved from the published package: prodlint 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.
-
projscan - Spec Support Unverifiedabhiyoheswaran1
Distributed as npm:projscan. Spec revision support not yet verified.
-
PubNub MCP Server - Earlier Revisionpubnub
Distributed as npm:@pubnub/mcp. Resolved from the published package: @pubnub/mcp 2.3.10 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Pump SDK MCP Server - Earlier Revision
nirholas
Distributed as npm:pump-fun-mcp. Resolved from the published package: pump-fun-mcp 1.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
PumpFun Claims Bot - Earlier Revisionnirholas
Distributed as npm:pumpfun-claims-bot. Resolved from the published package: pumpfun-claims-bot 1.0.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.
-
pushci - Spec Support Unverifiedfinsavvyai
Distributed as npm:pushci. Spec revision support not yet verified.
-
python-mcp - Spec Support Unverifiedfiles.com
Distributed as pypi:files-com-mcp. Spec revision support not yet verified.
-
q-ring - Earlier RevisionI4cTime
Distributed as npm:@i4ctime/q-ring. Resolved from the published package: @i4ctime/q-ring 0.16.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.
- Qase Test Management - Earlier Revision
qase.io
Listed with a remote endpoint. Resolved from the published package: @qase/mcp-server 2.2.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
QR Code Generator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
- quantakrypto pqc-tools - Spec Support Unverified
quantakrypto
Listed with a remote endpoint. Spec revision support not yet verified.
-
quickbooks-mcp - Earlier Revisionlaf-rge
Distributed as npm:quickbooks-mcp. Resolved from the published package: quickbooks-mcp 0.9.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.
-
ramp-kit - Earlier Revisionarmandocodecr
Distributed as npm:@ramp-kit/mcp. Resolved from the published package: @ramp-kit/mcp 0.1.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Raven - Earlier Revision
ravenmcp.ai
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
REA - Current Spec Verifiedmorluto
Distributed as npm:rea-agents. Resolved from the published package: rea-agents 3.1.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.
-
RealAgent MCP - Spec Support Unverifiedzhangxueliang1218
Distributed as npm:realagent-mcp. Spec revision support not yet verified.
-
redacta-mcp - Earlier Revisionnickjlamb
Distributed as npm:redacta-mcp. Resolved from the published package: redacta-mcp 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.
-
reddit-mcp-buddy - Earlier Revisionkaranb192
Distributed as npm:reddit-mcp-buddy. Resolved from the published package: reddit-mcp-buddy 1.1.14 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
reddit-mcp-server - Spec Support Unverifiedjordanburke
Distributed as npm:reddit-mcp-server. Spec revision support not yet verified.
-
Reelier - Earlier Revisionseldonframe
Distributed as npm:reelier. Resolved from the published package: reelier 0.32.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.
-
ref-tools-mcp - Earlier Revisionref-tools
Distributed as npm:ref-tools-mcp. Resolved from the published package: ref-tools-mcp 3.0.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.
-
Regex-LE - Spec Support Unverifiednolindnaidoo
Distributed as npm:regex-le-mcp. Spec revision support not yet verified.
-
remem - Spec Support Unverifiedmajiayu000
Distributed as npm:@remem-ai/remem. Spec revision support not yet verified.
-
Rendobar - Earlier Revisionrendobar.com
Listed with a remote endpoint. Resolved from the published package: @rendobar/mcp 1.11.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.
-
repovine - Earlier Revisionlegann
Distributed as npm:repovine. Resolved from the published package: repovine 0.1.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.
-
Research Report API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
review-assist-mcp - Spec Support Unverifieduditk2
Distributed as npm:review-assist-mcp. Spec revision support not yet verified.
-
rigour - Earlier Revisionrigour-labs
Distributed as npm:@rigour-labs/mcp. Resolved from the published package: @rigour-labs/mcp 5.5.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.
-
ris - Earlier Revisionphilrox
Distributed as npm:ris-mcp-ts. Resolved from the published package: ris-mcp-ts 1.7.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.
-
rise-mcp - Earlier Revisiongzlo
Distributed as npm:rise-mcp. Resolved from the published package: rise-mcp 1.17.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.
-
rivemcp - Earlier Revisionparadoxsyn
Distributed as npm:rivemcp. Resolved from the published package: rivemcp 1.13.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
robrain - Spec Support Unverifiedadelinamart
Distributed as npm:robrain. Spec revision support not yet verified.
- ROS 2 MCP Server - Spec Support Unverified
WiseVision
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.
-
Roslyn CodeLens - Spec Support UnverifiedMarcelRoozekrans
Distributed as npm:roslyn-codelens-mcp. Spec revision support not yet verified.
-
rsdoctor - Spec Support Unverifiedyifancong
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.
- Run402 - Earlier Revision
run402.com
Endpoint probe negotiated 2025-06-18; support for 2026-07-28 not confirmed.
-
runapi-mcp - Earlier Revisionrunapi-builder
Listed with a remote endpoint. Resolved from the published package: @runapi.ai/mcp 0.11.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.
-
ruv-swarm - Spec Support Unverifiedruvnet
Distributed as npm:ruv-swarm. Hand check 2026-08-25: no MCP revision statement in the monorepo or ruv-swarm READMEs or the MCP docs set; npm ruv-swarm 1.0.20 declares no MCP SDK dependency and was last published 2025-09-10, while the repository (ruvnet/ruv-FANN) last pushed 2026-08-09.
-
Safari MCP Server - Spec Support UnverifiedApple
Apple ships an MCP server inside Safari, delivered through the safaridriver binary, exposing 17 tools for web development and debugging. No Apple page names any MCP specification revision, transport, license or source repository, so spec support is recorded as unverified rather than inferred from the announcement date.
-
safari-mcp - Earlier Revisionachiya-automation
Distributed as npm:safari-mcp. Resolved from the published package: safari-mcp 2.16.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Safe Docx - Spec Support UnverifiedUseJunior
Distributed as npm:@usejunior/safe-docx. Spec revision support not yet verified.
-
SAGE Wrapper - Spec Support UnverifiedPsYcGoD
Distributed as pypi:psycgod-sage. Spec revision support not yet verified.
-
salesforce-metadata-mcp - Earlier Revisionsemwalajay83-sem
Distributed as npm:salesforce-metadata-mcp. Resolved from the published package: salesforce-metadata-mcp 2.12.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.
-
samarth-gtm-mcp - Earlier Revisionsamarthanalytics-sj
Distributed as npm:samarth-gtm-mcp. Resolved from the published package: samarth-gtm-mcp 1.473.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.
-
samsung-health-mcp - Earlier Revisiondavidmosiah
Distributed as npm:samsung-health-mcp-unofficial. Resolved from the published package: samsung-health-mcp-unofficial 0.7.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.
-
SAP HANA CLI - Spec Support UnverifiedSAP-samples
Distributed as npm:hana-cli. Spec revision support not yet verified.
-
SAP MCP Server - Earlier Revisionmcp.sap.oobeprotocol.ai
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
sap-adt-mcp - Earlier Revisionyzonur
Distributed as npm:sap-adt-mcp. Resolved from the published package: sap-adt-mcp 0.8.58 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Sapiens Sintéticos - Earlier Revisionsapiensinteticos.com
Listed with a remote endpoint. Resolved from the published package: sapiens-mcp 1.57.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.
- savvly - Earlier Revision
savvly.com
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
- Scavio - Earlier Revision
scavio-ai
Listed with a remote endpoint. Resolved from the published package: @scavio/mcp-server 0.13.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.
-
Scholar Feed - Spec Support UnverifiedYGao2005
Distributed as npm:scholar-feed-mcp. Spec revision support not yet verified.
-
Scholar Sidekick - Earlier Revisionmlava
Distributed as npm:scholar-sidekick-mcp. Resolved from the published package: scholar-sidekick-mcp 0.8.8 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Scrape-LE - Spec Support Unverifiednolindnaidoo
Distributed as npm:scrape-le-mcp. Spec revision support not yet verified.
-
screenpipe - Earlier Revisionscreenpipe
Distributed as npm:screenpipe-mcp. Resolved from the published package: screenpipe-mcp 0.19.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.
-
screenplaywriter-mcp - Earlier Revisionmrfentmen
Distributed as npm:screenplaywriter-mcp. Resolved from the published package: screenplaywriter-mcp 1.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Screenshot & PDF Capture API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Search Console MCP - Earlier Revisionsaurabhsharma2u
Distributed as npm:search-console-mcp. Resolved from the published package: search-console-mcp 2.0.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.
-
Search1API - Current Spec Verifiedsuperagents-lab
Listed with a remote endpoint. Resolved from the published package: search1api-mcp 0.5.4 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
SearXNG Search - Earlier Revisionihor-sokoliuk
Distributed as npm:mcp-searxng. Resolved from the published package: mcp-searxng 1.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.
-
seekstone - Earlier Revisionshaqmughal
Distributed as npm:seekstone. Resolved from the published package: seekstone 0.14.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.
-
sem - Spec Support UnverifiedAtaraxy-Labs
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.
-
Semiotic - Earlier Revisionnteract
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Sendinel - Earlier Revisionsendinel.ai
Listed with a remote endpoint. Resolved from the published package: @sendinel/mcp-server 1.0.10 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Sentiment Analyzer API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Sentry MCP Server - Earlier RevisionSentry
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.
-
SEO Tools: A-Parser bridge - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-aparser. Resolved from the published package: seo-tools-mcp-aparser 1.7.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.
-
SEO Tools: Google Search Console - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-gsc. Resolved from the published package: seo-tools-mcp-gsc 1.7.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.
-
SEO Tools: XMLRiver SERP (Google + Yandex) - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-xmlriver. Resolved from the published package: seo-tools-mcp-xmlriver 1.7.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.
-
SEO Tools: XMLStock SERP (Google + Yandex) - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-xmlstock. Resolved from the published package: seo-tools-mcp-xmlstock 1.7.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.
-
SEO Tools: Yandex Wordstat - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-wordstat. Resolved from the published package: seo-tools-mcp-wordstat 1.7.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.
-
SEO Tools: Yandex.Metrica - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-metrika. Resolved from the published package: seo-tools-mcp-metrika 1.7.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.
-
SEO Tools: Yandex.Webmaster - Earlier Revisionantohins
Distributed as npm:seo-tools-mcp-ywm. Resolved from the published package: seo-tools-mcp-ywm 1.7.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.
-
server - Earlier Revisionmcp.zype.com
Listed with a remote endpoint. Resolved from the published package: @zype-com/mcp 0.6.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.
-
ServiceNow MCP Server (NowAIKit) - Earlier Revisionaartiq
Distributed as npm:nowaikit. Resolved from the published package: nowaikit 4.12.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.
-
sfcc-dev-mcp - Earlier Revisiontaurgis
Distributed as npm:sfcc-dev-mcp. Resolved from the published package: sfcc-dev-mcp 1.1.0 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
sharedoc-mcp - Earlier RevisionAugustusW
Distributed as npm:sharedoc-mcp. Resolved from the published package: sharedoc-mcp 2.2.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.
- Shiplight MCP - Spec Support Unverified
Shiplight
Distributed as npm:@shiplightai/mcp. First-party: the ai.shiplight registry namespace is domain-verified and the server fronts Shiplight's own agent-testing platform. No public repository; the registry record and npm package carry no repo URL. No MCP revision statement found (checked 2026-08-27) on shiplight.ai or in the package README.
-
shipmail-mcp - Current Spec Verifiedshipmail-to
Listed with a remote endpoint. Resolved from the published package: shipmail-mcp 0.7.3 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
ShipStatic - Earlier Revisionshipstatic.com
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
- SigRank - Token Efficiency Leaderboard - Earlier Revision
SunrisesIllNeverSee
Distributed as npm:sigrank. Resolved from the published package: sigrank 0.0.222 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Simmer - Earlier Revisionadlai88
Distributed as npm:simmer-mcp. Resolved from the published package: simmer-mcp 3.5.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.
-
simplenote-mcp - Earlier RevisionAutomattic
Distributed as npm:@automattic/simplenote-mcp. Resolved from the published package: @automattic/simplenote-mcp 2.0.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.
- SiYuan - Spec Support Unverified
SiYuan
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.
-
slack - Earlier Revisionpulsemcp.com
Distributed as npm:slack-workspace-mcp-server. Resolved from the published package: slack-workspace-mcp-server 0.0.7 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Slack MCP Server - Earlier Revision
jtalk22
Listed with a remote endpoint. Resolved from the published package: @jtalk22/slack-mcp 4.9.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.
-
slimdex-mcp - Earlier RevisionSiddhukaushik
Distributed as npm:slimdex-mcp. Resolved from the published package: slimdex-mcp 1.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.
-
Smart Reader MCP - Earlier RevisionSylphxAI
Distributed as npm:@sylphx/smart-reader-mcp. Resolved from the published package: @sylphx/smart-reader-mcp 0.2.11 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
SmartBear MCP - Current Spec Verifiedsmartbear.com
Two product-specific remote endpoints are listed in the registry, for Bugsnag and for Zephyr. Both require authorization, so the spec revision is not yet verified. Resolved from the published package: @smartbear/mcp 0.37.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.
- Snyk MCP Server - Earlier Revision
Snyk
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.
-
Social Profile Enrichment API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
socraticode - Earlier Revisiongiancarloerra
Distributed as npm:socraticode. Resolved from the published package: socraticode 1.12.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.
- Spacefast - Earlier Revision
spacefast
Listed with a remote endpoint. Resolved from the published package: spacefast 0.0.24 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
SPARDA - Earlier Revisionzyx77550
Distributed as npm:sparda-mcp. Resolved from the published package: sparda-mcp 0.71.3 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- Splunk MCP Server - Earlier Revision
Splunk
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.
-
sportiq-mcp - Spec Support UnverifiedNinjabeam20
Distributed as pypi:sportiq-mcp. Spec revision support not yet verified.
-
Spot Advanced Swap Orders - Spec Support Unverifiedorbs-network
Distributed as npm:@orbs-network/spot. Spec revision support not yet verified.
-
SQL Preview - Earlier Revisionfadnavismehul
Distributed as npm:sql-preview. Resolved from the published package: sql-preview 0.6.28 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- ssh-mcp - Spec Support Unverified
Tufan Tunç
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.
-
SSL Checker API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Stata MCP Server - Spec Support Unverifiedaliveranme
Distributed as npm:@aliveranme/stata-mcp. Spec revision support not yet verified.
-
State Memory MCP - Earlier Revisionputervision
Distributed as npm:@putervision/state-memory-mcp. Resolved from the published package: @putervision/state-memory-mcp 1.0.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.
-
Steam MCP Server - Current Spec VerifiedGrinv
Distributed as npm:steam-games-mcp. Resolved from the published package: steam-games-mcp 0.13.1 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
stickies - Earlier Revisiondumbspacecookie
Distributed as npm:stickies-mcp. Resolved from the published package: stickies-mcp 0.14.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Stock Price API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
storefront-mcp - Earlier RevisionMaarmapa
Distributed as npm:storefront-mcp. Resolved from the published package: storefront-mcp 1.0.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.
- Storybook MCP Addon - Spec Support Unverified
Storybook
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.
-
strava-mcp - Earlier Revisiondavidmosiah
Distributed as npm:strava-mcp-unofficial. Resolved from the published package: strava-mcp-unofficial 0.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
sub-agents-mcp - Earlier Revisionshinpr
Distributed as npm:sub-agents-mcp. Resolved from the published package: sub-agents-mcp 0.12.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.
-
Substack MCP Server - Earlier Revisionconorbronsdon
Distributed as npm:@conorbronsdon/substack-mcp. Resolved from the published package: @conorbronsdon/substack-mcp 0.6.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Supabase MCP Server - Earlier RevisionSupabase
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.
-
superlocalmemory - Spec Support Unverifiedvarun369
Distributed as npm:superlocalmemory. Spec revision support not yet verified.
-
Svelte MCP - Current Spec Verifiedsvelte.dev
Endpoint probe confirmed support for 2026-07-28 via server/discover.
-
sverklo - Earlier Revisionsverklo
Distributed as npm:sverklo. Resolved from the published package: sverklo 0.29.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Syncline MCP Server (Go) - Spec Support Unverifiedkekwanu.com
Distributed as npm:@kekwanulabs/syncline-mcp-server-go. Spec revision support not yet verified.
-
t2000 - Spec Support Unverifiedmission69b
Distributed as npm:@t2000/mcp. Spec revision support not yet verified.
-
tachibot-mcp - Spec Support UnverifiedbyPawel
Distributed as npm:tachibot-mcp. Spec revision support not yet verified.
- Tap - Earlier Revision
LeonTing1010
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
tashan - Spec Support Unverifiedtashan.sh
Distributed as npm:tashan-cli. Spec revision support not yet verified.
-
tavily-mcp - Earlier Revisiontavily-ai
Distributed as npm:tavily-mcp. Resolved from the published package: tavily-mcp 0.2.22 depends on @modelcontextprotocol/sdk@1.26.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
teamcity - Earlier RevisionDaghis
Distributed as npm:@daghis/teamcity-mcp. Resolved from the published package: @daghis/teamcity-mcp 2.12.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.
-
Telnyx MCP Server - Earlier RevisionTelnyx
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.
-
testrail-mcp-server - Earlier Revisionuarlouski
Distributed as npm:@uarlouski/testrail-mcp-server. Resolved from the published package: @uarlouski/testrail-mcp-server 2.4.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.
-
Text Classifier API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Text to Speech API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
ThumbGate - Spec Support UnverifiedIgorGanapolsky
Distributed as npm:thumbgate. Spec revision support not yet verified.
-
TikTok for Business MCP Server - Spec Support UnverifiedTikTok
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.
-
time-mcp - Earlier Revisionyokingma
Distributed as npm:time-mcp. Resolved from the published package: time-mcp 1.0.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Titen Memory - Spec Support UnverifiedRamaAditya49
Distributed as npm:titen-memory. Spec revision support not yet verified.
-
TMDB MCP Server - Current Spec VerifiedGrinv
Distributed as npm:tmdb-mcp. Resolved from the published package: tmdb-mcp 0.11.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.
- Toggl MCP Server - Spec Support Unverified
Toggl
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).
-
Token Holders API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Token Price API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
token-optimizer-mcp - Earlier Revisionooples
Distributed as npm:@ooples/token-optimizer-mcp. Resolved from the published package: @ooples/token-optimizer-mcp 5.7.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.
-
Toon Memory - Spec Support UnverifiedLuiggiVal08
Distributed as npm:toon-memory. Spec revision support not yet verified.
-
touchdesigner-mcp-server - Current Spec Verified8beeeaaat
Distributed as npm:touchdesigner-mcp-server. Resolved from the published package: touchdesigner-mcp-server 2.0.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.
-
Trackly CLI - Earlier Revisiontrackly-app
Listed with a remote endpoint. Resolved from the published package: trackly-cli 0.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.
-
Transloadit Media Processing - Earlier Revisiontransloadit
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Trust Score API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
trvl - Spec Support UnverifiedMikkoParkkola
Distributed as oci:ghcr.io/mikkoparkkola/trvl:1.20.0. Spec revision support not yet verified.
-
Twitter Scraper API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
TwitterAPIs - Earlier RevisionTwitterAPIs
Distributed as npm:@twitterapis/mcp. Resolved from the published package: @twitterapis/mcp 0.9.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.
-
Uindow - Spec Support Unverifieduindow
Distributed as npm:@uindow/cli. Spec revision support not yet verified.
-
Umbra - Earlier Revisionelberacasa
Distributed as npm:@elberacasa/umbra. Resolved from the published package: @elberacasa/umbra 1.8.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.
-
Umbraco-CMS-MCP-Dev - Earlier Revisionumbraco
Distributed as npm:@umbraco-cms/mcp-dev. Resolved from the published package: @umbraco-cms/mcp-dev 18.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- UnClick - Earlier Revision
malamutemayhem
Distributed as npm:@unclick/mcp-server. Resolved from the published package: @unclick/mcp-server 0.3.128 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
unleash-mcp - Earlier Revisiongetunleash.io
Distributed as npm:@unleash/mcp. Resolved from the published package: @unleash/mcp 0.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.
-
Unsplash MCP Server - Earlier Revisionhanoak
Distributed as npm:@hanoak/unsplash-mcp-server. Resolved from the published package: @hanoak/unsplash-mcp-server 1.2.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.
-
User Agent Parser API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
UUID Generator API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Vaaya - Earlier Revisionvaaya.ai
Listed with a remote endpoint. Resolved from the published package: @vaaya/mcp 0.6.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.
-
variflight-mcp - Earlier Revisionvariflight
Distributed as npm:@variflight-ai/variflight-mcp. Resolved from the published package: @variflight-ai/variflight-mcp 1.0.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.
-
Vector Search API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
verbative-memory - Spec Support Unverifiedverbative
Distributed as npm:verbative-memory. Spec revision support not yet verified.
-
Vercel MCP - Current Spec VerifiedVercel
Vercel's first-party hosted MCP server: docs search, project and deployment management, log analysis, and Web Analytics queries. Serves the stateless 2026-07-28 revision and 2025-era clients from the same endpoint, with OAuth authorization.
-
Vessel Browser - Current Spec Verifiedunmodeled-tyler
Distributed as npm:@quanta-intellect/vessel-browser. Resolved from the published package: @quanta-intellect/vessel-browser 0.1.195 depends on @modelcontextprotocol/server@2.0.0, whose artifact implements 2026-07-28. This records what the artifact implements, not what a deployment negotiates.
-
vg-resource-mcp - Earlier Revisionmrfentmen
Distributed as npm:vg-resource-mcp. Resolved from the published package: vg-resource-mcp 1.0.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
vibedate - Earlier Revisionpooriaarab
Distributed as npm:vibedate. Resolved from the published package: vibedate 0.9.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.
-
vibeshare-live - Spec Support Unverifiedpooriaarab
Distributed as npm:vibeshare-live. Spec revision support not yet verified.
-
vibesharing - Earlier Revisionerova
Distributed as npm:@vibesharingapp/mcp-server. Resolved from the published package: @vibesharingapp/mcp-server 0.16.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.
-
Video Reader MCP - Earlier RevisionSylphxAI
Distributed as npm:@sylphx/video-reader-mcp. Resolved from the published package: @sylphx/video-reader-mcp 0.1.7 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- virustotal - Spec Support Unverified
BurtTheCoder
Distributed as npm:@burtthecoder/mcp-virustotal. Spec revision support not yet verified.
-
Visual Memory MCP - Earlier Revisionputervision
Distributed as npm:@putervision/vision-memory-mcp. Resolved from the published package: @putervision/vision-memory-mcp 1.0.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.
-
vnsh - Earlier Revisionraullenchai
Distributed as npm:vnsh-mcp. Resolved from the published package: vnsh-mcp 1.8.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
Wallet Portfolio Tracker API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
warhammer-oracle - Earlier Revisiongregario
Distributed as npm:warhammer-oracle. Resolved from the published package: warhammer-oracle 0.2.59 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
warp-agent-mcp - Earlier Revisionwarpfreight
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Wayback Machine - Earlier RevisionMearman
Distributed as npm:mcp-wayback-machine. Resolved from the published package: mcp-wayback-machine 3.7.1 depends on @modelcontextprotocol/sdk@1.29.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
wc26 - Earlier Revisionjordanlyall
Distributed as npm:wc26-mcp. Resolved from the published package: wc26-mcp 0.3.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.
-
wcagc - accessibility scanning - Earlier RevisionWCAG-Compliance
Listed with a remote endpoint. Resolved from the published package: @wcagc/mcp 0.7.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.
-
Weather MCP Server - Spec Support Unverifiedisdaniel
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.
- Weather MCP Server (dangahagan) - Spec Support Unverified
dangahagan
Distributed as npm:@dangahagan/weather-mcp. Community: the server aggregates free public weather APIs the publisher does not operate. The README states zero API keys are required, which grounds auth none. No MCP revision statement found (checked 2026-08-27).
-
Weavatrix - Spec Support Unverifiedsergii-ziborov
Distributed as npm:weavatrix. Spec revision support not yet verified.
-
Web Scraper to Markdown API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Web Search API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
webcomponents-mcp-server - Earlier RevisionUI5
Distributed as npm:@ui5/webcomponents-mcp-server. Resolved from the published package: @ui5/webcomponents-mcp-server 0.1.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
webcomponents-react-mcp-server - Earlier RevisionUI5
Distributed as npm:@ui5/webcomponents-react-mcp. Resolved from the published package: @ui5/webcomponents-react-mcp 2.25.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.
-
WebCrypt MCP Server - Earlier Revisionputervision
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.
-
WebPeel - Earlier RevisionJakeLiuMe
Distributed as npm:webpeel. Resolved from the published package: webpeel 0.22.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.
-
Website Auditor - Earlier RevisionSpikeyCoder
Distributed as npm:website-auditor-mcp. Resolved from the published package: website-auditor-mcp 1.0.19 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
wellness-nourish - Earlier Revisiondavidmosiah
Distributed as npm:wellness-nourish. Resolved from the published package: wellness-nourish 0.8.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- What's Inherited - Earlier Revision
stcmain
Distributed as npm:whats-inherited-mcp. Resolved from the published package: whats-inherited-mcp 0.1.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- What's Loaded - Earlier Revision
stcmain
Distributed as npm:whats-loaded-mcp. Resolved from the published package: whats-loaded-mcp 0.2.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
- What's Running - Earlier Revision
stcmain
Distributed as npm:whats-running-mcp. Resolved from the published package: whats-running-mcp 0.1.6 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
whoop-mcp - Earlier Revisiondavidmosiah
Distributed as npm:whoop-mcp-unofficial. Resolved from the published package: whoop-mcp-unofficial 0.6.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.
-
wigolo - Earlier RevisionKnockOutEZ
Distributed as npm:wigolo. Resolved from the published package: wigolo 0.2.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.
-
withingsmcp - Earlier Revisiondavidmosiah
Distributed as npm:withings-mcp-unofficial. Resolved from the published package: withings-mcp-unofficial 0.5.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.
-
witness - Spec Support UnverifiedIngTian
Distributed as npm:@witness-ai/opencode. Spec revision support not yet verified.
-
Word Counter API - Earlier RevisionBr0ski777
Endpoint probe negotiated 2024-11-05; support for 2026-07-28 not confirmed.
-
Workfile - Spec Support Unverifiedillodev
Distributed as npm:@illodev/workfile. Spec revision support not yet verified.
-
XActions - Earlier Revisionnirholas
Distributed as npm:xactions. Resolved from the published package: xactions 3.5.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.
-
xdebug - Earlier Revisionkpanuragh
Distributed as npm:xdebug-mcp. Resolved from the published package: xdebug-mcp 1.3.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.
-
xlsx-for-ai - Earlier Revisionsenoff
Distributed as npm:xlsx-for-ai. Resolved from the published package: xlsx-for-ai 4.0.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.
-
XRPL-Utilities - Earlier RevisionXRPL-Utilities
Distributed as npm:@xrpl-utilities/mcp. Resolved from the published package: @xrpl-utilities/mcp 0.2.195 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
XRPName - Earlier RevisionXRPDomains
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
-
Yahoo Finance - Spec Support Unverifieddanishashko
Distributed as npm:yahoo-finance-mcp-server. Spec revision support not yet verified.
-
yandex-direct-mcp - Spec Support Unverifiedai-hub-open
Distributed as npm:@ai-hub-open/yandex-direct-mcp. Spec revision support not yet verified.
-
Yaw MCP - Spec Support UnverifiedYawLabs
Distributed as npm:@yawlabs/mcp. First-party: the server is YawLabs' own product (yaw.sh/mcp documents it as "A CLI that runs MCP servers on your machine"). An orchestrator that fronts other MCP servers from one connection; local-first, no account. No MCP revision statement found on yaw.sh/mcp or in the README (checked 2026-08-27).
-
YawLabs Postgres MCP - Spec Support UnverifiedYawLabs
Distributed as npm:@yawlabs/postgres-mcp. Community: the YawLabs organization does not operate PostgreSQL, which the server fronts. Read-only by default with writes behind an env var, per the README. No MCP revision statement found (checked 2026-08-27).
-
YouTube Data - Earlier Revisionkirbah
Distributed as npm:@kirbah/mcp-youtube. Resolved from the published package: @kirbah/mcp-youtube 1.1.13 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
yuque-mcp - Earlier Revisionyuque
Distributed as npm:yuque-mcp. Resolved from the published package: yuque-mcp 1.0.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.
-
zendesk-mcp-server - Earlier Revisionfruggr
Distributed as npm:@fruggr/zendesk-mcp-server. Resolved from the published package: @fruggr/zendesk-mcp-server 2.18.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.
-
zenrows-mcp - Earlier RevisionZenRows
Distributed as npm:@zenrows/mcp. Resolved from the published package: @zenrows/mcp 2.2.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.
-
zigbee2mqtt-mcp - Earlier Revisionalexpfau
Distributed as npm:zigbee2mqtt-mcp. Resolved from the published package: zigbee2mqtt-mcp 0.7.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.
- Ziggs - Earlier Revision
ZiggsAI
Listed with a remote endpoint. Resolved from the published package: @ziggs-ai/ziggs-mcp 0.11.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.
-
zkverify - Earlier Revisionzkarchitect
Distributed as npm:zkverify-mcp. Resolved from the published package: zkverify-mcp 0.3.2 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
-
zola-mcp - Earlier Revisionchrischall
Distributed as npm:zola-mcp. Resolved from the published package: zola-mcp 1.7.5 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.