Know exactly what changed.
MCPSearch keeps a permanent daily record of every Model Context Protocol server, the versions it published, and the exact bytes each one shipped. When a package moves, the history is already there.
Coverage, as of right now.
Every figure below is read from the live archive when this page loads.
The record grows every day.
One snapshot per day, appended, never rewritten. History cannot be reconstructed after the fact, which is the entire reason to keep it.
The same total shown above, by day. The step is when the archive began holding repositories published outside the registry, not when those repositories appeared.
Look up any server.
Search the registry index by name, publisher or package, and open a result to see every version it has published. Repositories found outside the registry are archived already and join this index shortly.
Why it matters.
A version number is not a guarantee.
The same version can be republished with different contents, and a tag can be moved to point at different code. We record the bytes, so the difference is visible rather than assumed.
Registries show you today.
Public registries publish what exists now. What a package contained last quarter, or what a since deleted server shipped, is not something you can go back and fetch.
Your agents run this code.
Model Context Protocol servers execute with real access to real systems. Knowing precisely what they contained, on any given day, is a security question before it is a convenience.
Talk to us.
For access to the historical record, integration questions, or anything else. We read every message.