Methodology & corrections

How every fact on this site is computed · current data as of 2026-06-30.

Data sources

Facts are computed from public metadata: the Official MCP Registry (server list, CC0 1.0 public-domain metadata) and the public npm registry (package metadata + download counts). No package is installed, imported, booted, or executed to produce these factual pages — every value is read from public metadata only.

What each field means

npm downloads (last 30 days)last-30-day total from the npm downloads API

Registry record updatedage of the server's record in the Official MCP Registry

Resolves on npmwhether the declared package resolves on the public npm registry

Last publishedage of the latest published npm version

MCP SDK declared@modelcontextprotocol/sdk version in the published package.json

SDK driftminor versions between the declared SDK and the latest minor (1.29.0) as of 2026-06-30

What we deliberately do NOT claim here

These free pages state facts. They do not assert whether a server is secure, safe, or advisable, and they do not predict runtime behaviour. Install-and-boot results against the 2026-07-28 stateless spec, tools/list schema validation, advisory matches, and change-over-time history require actually running each server in an isolated environment — that verified-behaviour work is the Pro tier.

"Not detectable" vs "not yet scanned"

Not detectable from package.json means the server WAS scanned and no @modelcontextprotocol/sdk dependency was found (it may be bundled or a workspace dependency). Not yet scanned means the server is catalogued but its package metadata has not been read yet. Neither is treated as a negative finding.

The dated series

Every fact carries an as-of date (2026-06-30) and the scan re-runs over time, so each server accumulates a dated history. 1086 servers are catalogued; 300 are SDK-scanned so far. The version history — how a server's declared SDK and status change across scans — is recorded forward from the first observation.

Corrections & appeals

Spot a fact you believe is wrong, or want your server re-scanned? Email corrections@mcpcompat.io with the package name and the correction. Because every field is reproducible from public metadata, corrections are checked against the same sources and, if confirmed, reflected on the next scan.