Method and limits
How the scan works
The scanner reads the list of listings from the public API of the official MCP Registry (/v0/servers?version=latest, 100 listings per page, cursor paging), at most one request per second, with a User-Agent that names this site. There are two kinds of pass: a full pass reads the latest version of every listing, and a pass over updated listings reads only the latest version of the listings published or changed since the previous scan (the API's updated_since parameter, with a margin of two hours). The list answer carries each listing's publisher metadata, so a listing is read again only when that metadata holds a declaration pointer (_meta["io.modelcontextprotocol.registry/publisher-provided"].addonDeclaration) or is present but malformed, or when the listing was shown in the previous result. The scan stops at the first HTTP 429 answer or after three failed registry requests in a row.
The registry holds tens of thousands of listings, and a full pass over the list took about 20 minutes at this rate on 19 November 2026. So a full pass runs from time to time, and the scans in between are passes over updated listings. A pointer can only appear in a newly published version, which such a pass reads. Every listing shown in the previous result is checked again in every scan, and one whose check finds that it names no declaration is moved to "No longer listed". The front page gives the time of the last scan and says which kind of pass it was.
For each listing with a pointer the scanner runs the logic of check-listing --fetch-tools from the public checker, imported from its published code. That check reads the listing by name and version, fetches the declaration the pointer names from the publisher's domain, compares its hash, name, version and remotes with the listing, looks up the key by DNS or at the domain's web server and verifies the signature and the time window, reads newer declarations for the same version next to it, and reads the tool list from the declared remote to compare it with the declaration in force. Every request is listed on the listing page.
A scan that does not finish, or whose result fails a sanity check (a full pass that read no listings, fewer than half the listings of the last full pass, or no publisher metadata at all), is not published: the previous result stays in place and the failure is shown on the front page. Each published scan is also kept as a dated file.
What a result shows
A result of verified or verified_newer_declaration shows, on the date of the check:
- the holder of the key named in the declaration signed exactly that content, and that key was published at the declared domain by the declared method;
- that domain proves the listing's namespace under the registry's rules;
- the listing the registry served names this declaration by its hash, the publisher's site served it, and its name, version and remotes equal the listing's;
- for
verified_newer_declaration, the declaration in force follows the named one under the same key and is the newest one the publisher's site served; - when the tool list was compared, the list the declared remote sent equals the declared one (for format 0.2, its two digests under mcp-tool-set-digest/1).
What a result does not show
- that the server, its publisher or any tool is harmless, honest or lawful;
- that the server returns these tools to every client, or that the tools behave as described;
- that the remote endpoints are operated by the publisher (a domain can declare an endpoint on another party's host);
- that a pay address belongs to the publisher, or that a payment request at call time matches;
- that this is the newest declaration the key holder signed (the publisher's site chooses which one it serves), or that no newer one exists beyond the two paths read;
- that another registry, mirror or client is given the same listing;
- that the tool list a client receives later, or under another protocol version or authorization, is the one compared;
- across a change of key, that the same holder signed both linked declarations.
Limits of the tool check
A server that asks for authorization leaves the tool list not compared, and the state stays verified or verified_newer_declaration; the listing page says so. A tool list can differ by MCP protocol version and authorization while the server changed nothing, so each page names the protocol version the check used. The digests of format 0.2 read some lists the same way (for example a missing description and an empty one), and when two tools share a name they do not pin which tool carries an annotation; the checker notes such lists.
Limits of this site
- Each result is a snapshot from one check on one day. A listing, a site or a server can change the next minute.
- Listing names, titles and descriptions are publisher text from the registry. They are shown escaped and shortened, and email addresses in them are removed.
- The registry does not check publisher metadata or remotes. A listing can point to anything; the check reports what it found.
- The registry asks host applications to read it through aggregators. This site reads the list at a low rate, at most one request per second, and reads single listings only for the listings it checks.
- No result here is a rating, a score or a recommendation.
Independence and AI assistance
Declared is independent of the Model Context Protocol project. It is not affiliated with or endorsed by the Model Context Protocol project or its registry. The authors of this site also publish the listing com.rtlpdf/arabic-pdf (rtlpdf.com), which the site lists and checks like every other listing. The site, the scanner and the checker were written with substantial AI assistance. The code, data and tests of this site are public: https://github.com/bcrypto0/declaredlist. The checker's code and tests are public: https://github.com/bcrypto0/addon-declaration.
Data
The full result of the last scan is at data.json. Every published scan is kept as a dated file in the site repository. The pages use no JavaScript, no cookies, no trackers and no outside requests.
Reporting a wrong result
If a result here does not match what the check finds for you, open an issue on the issues page of the site repository with the listing name, the version and the output of the command on its listing page (add --json). Problems with the checker or the spec go to the issues page of the public checker. The site does not accept or remove listings by request.
Last complete scan: 19 November 2026, 16:43 UTC.