Citing
How to cite ProtocolProbe
Everything here is published under CC-BY-4.0: reuse it, and credit ProtocolProbe with a link and the date the facts were checked.
A figure from a report
Every figure in The MCP registry vs. reality has its own permanent link and a ready “Cite this figure” line with the number, its base, the registry snapshot (2026-10-04) and the check date (2026-10-06). Copy that line as it is.
One server's facts
Link the server's page (https://protocolprobe.com/mcp/servers/<namespace>/<name>) and give the date shown there. Through the API, every record carries its own attribution and retrievedFrom; every response also carries:
Compiled by ProtocolProbe (https://protocolprobe.com). Reuse under CC BY 4.0: credit ProtocolProbe with each record's `page` link and `asOf` date.The whole dataset
An archived copy of every server's facts on Zenodo, with a permanent DOI. Cite all versions with this DOI (it always leads to the latest):
ProtocolProbe. ProtocolProbe: MCP server facts from the official MCP registry [Data set]. Zenodo. https://doi.org/10.5281/zenodo.23386799doi.org/10.5281/zenodo.23386799 (all versions) · this version, registry snapshot 2026-10-04: doi.org/10.5281/zenodo.23386800
What not to cite as ours
Text quoted from others is not ours to license: the publisher's registry title, description and status message, quotes from the publisher's website (pricing), deprecation messages from npm or PyPI, statements quoted from a repository's security policy, the tool descriptions in toolFacts (each is the publisher's first sentence), and tool, resource and package names.
No security verdict is published for a named server; please do not describe our facts as a safety rating.
The record-check count (“N of M record checks met”) and the ranks (“#N of M packages by monthly downloads”) are facts read from public records on a stated date, not a safety rating or a recommendation. Cite them with that date and the page link; how they are made is in the methodology.