io.github.microsoft
playwright-mcp
Observed
11 versions
11 artifacts
Sources: MCP Registry, Cline, Docker
What existed.
What shipped.
What changed.
Registries show you what exists today. MCPSearch preserves the history — every server, every version, every artifact, every change.
- Sep 25, 2026v1.1.2
a3f5…9c2 - Aug 14, 2026v1.1.1
4b7e…6d1 - Jul 03, 2026v1.1.0
9f2a…3e8 - May 18, 2026v1.0.0
c1d4…7a9
- New version observed
- Artifact changedSame version. Different bytes.
- Tag moved
- No longer listed
A live record for one server, its recent versions with their hashes, and the four kinds of change the record watches for: a new version observed, an artifact changed under an existing version, a repository tag moved, and a server no longer listed.
- 77,771MCP servers observed
- 438,757versions recorded
- 596,916artifacts archived
- 6.31 TBof stored bytes
Why a record
A registry answers one question. A record answers three.
What existed?
Servers and versions previously observed, including ones that may no longer appear in any current listing. Nothing leaves the record when a publisher removes it from theirs.
What shipped?
Where an artifact was retrievable, its bytes are stored and addressed by the SHA-256 of those bytes. The hash is the identity, so a stored object cannot disagree with its own address.
What changed?
Versions, artifacts, listings and repository refs are re-observed daily. When an answer differs from yesterday's, the difference is what gets recorded.
The record
Every day since the first crawl
Servers observed, one point per day, from the record's own published series. The step in mid-August is 34,000 GitHub repositories finishing a backfill, not a sudden arrival of servers.
The event
Same version. Different bytes.
A published version is meant to be immutable. When it is not, a record is the only place the difference survives.
sha256 73af…91c2
sha256 92cd…ab18
A changed hash is a fact, not a verdict. It establishes that the observed bytes differ. It does not establish the cause, and MCPSearch does not infer one. Illustrative values, not a real observation.
Method
How the record is built
- ObservedA server appears in a tracked source.
- Version recordedEach version observed is written with the date first seen.
- Artifact archivedWhere a published artifact is retrievable, its bytes are stored.
- SHA-256 recordedThe hash of those bytes becomes the artifact's identity.
- Observed againTomorrow the same question is asked, and any difference is recorded.
Sources observed daily
- Official MCP Registry
- GitHub
- Docker catalogue
- Smithery
- Cline
- npm
- PyPI
Limits
What this record cannot tell you
Stated plainly, because a record that overstates itself is worth less than one that does not.
- It cannot reconstruct history from before collection began.
- Catalogue coverage can be incomplete, and where a source will not show everything, the shortfall is recorded beside the listing.
- Hosted servers may publish no retrievable artifact, so there are no bytes to verify.
- First observed is when this record first saw a version, which is not necessarily when it was published.
- No longer listed does not mean deleted, and it does not mean abandoned.
The portal
The record is open to read
Every server held here has a page: when it was first observed, which versions were recorded, which artifacts were archived and what has changed since. No account, no charge.