Ecosystem Reports / Maintainer guide · updated August 5, 2026
Your GitHub URL can change without changing your MCP server. MCP Queen keys the public evidence page and live grade badge to the namespaced Registry identity, so maintainers have a stable link to share while repository and endpoint evidence are checked separately.
Search by Registry name, product name, or capability. Open your evidence page, review the declared repository and endpoint, then copy the ready-made badge Markdown into your README.
Registry searches are counted as aggregate demand signals. MCP Queen does not require an account to view evidence or copy a badge.
The badge points to the Registry-keyed evidence page rather than directly to a repository. Replace <registry-name> with the full namespaced name shown on your evidence page:
[](https://mcpqueen.com/s/<registry-name>)
The badge reports current operational probe results. It is not a security, privacy, or data-quality certification.
A repository can be renamed, transferred, archived, made private, or deleted while the server name and remote endpoint continue to exist. A dated audit provides the size of that maintenance problem without treating a repository lookup as proof of endpoint health.
Twenty-one percent of this dated sample was not stable at its declared GitHub location. That is a sample result, not an estimate for the entire MCP ecosystem. An unavailable lookup also does not explain why a repository could not be read: deletion, privacy changes, access restrictions, and malformed or stale metadata can look the same from a public audit.
At , the audit traversed all 201 pages returned by the official Registry’s latest-version API: 20,014 latest records, including 19,802 marked active. Those active records contained 15,929 exact GitHub repository mappings representing 14,408 unique repositories.
We selected 200 unique repositories using the lowest SHA-256 hashes of a published seed plus each normalized owner/repository value. GitHub’s GraphQL API then returned the canonical repository name, archive state, disabled state, URL, and last push time. The method prevents hand-picking but does not make the result statistically representative.
Download the complete dated audit (JSON) · Official Registry documentation · GitHub GraphQL documentation
A repository URL is a mutable source-location claim. It is useful, but it is not a durable server identity, proof of current ownership, or evidence that a remote MCP endpoint works. Treating those concepts as interchangeable creates link rot and can silently attach old directory records to stale implementation locations.
The better model separates three things:
last checked timestamps and distinguish renamed, transferred, archived, unavailable, and malformed mappings.Server pages now make the boundary visible: the Registry name is the evidence key, the repository is labeled as a mutable Registry-declared mapping, and the operational endpoint remains separate. This does not yet claim complete alias history. The next step is continuously checking repository mappings and retaining dated transitions without changing operational grades.
Request a scoped portfolio evidence review covering Registry identity, repository mappings, endpoint health, and a maintainer badge rollout. The first step is a public-evidence scope check; no unsupported security or adoption claim is included.
This audit measures repository-reference state at one timestamp. It does not establish why a repository moved; measure endpoint availability, code quality, security, privacy, or compliance; or attribute intent to a maintainer. Missing evidence remains unknown.