We tested every remote MCP server in the registry. One in ten is dead.
24,258 servers, each one connected to and asked what it offers. The first Tirekicker briefing says how many work, how many hide a login, and how quickly a listing goes stale. It is free to people on the waiting list.
Join the waiting listFree. The briefing is sent by email.
of servers listed more than six months ago
no longer work. For new listings it is 3%.
A listing tells you a server exists. It doesn't tell you it still works.
We connected to every remote server in the official registry on 5 October 2026 and recorded what happened. A few of the things we found:
The briefing has the full figures, eight findings, and a checklist of what to require before letting an agent depend on an MCP server.
What we do to every server
The same procedure for every server, run by software, with the raw output kept. No judgement calls and no favourites.
- Install it cleanA throwaway container with no credentials, capped memory and a hard time limit. Nothing carries over between servers.
- Start itWe record whether it starts, how long it takes, and what it prints if it doesn't.
- Ask what it offersWe complete the protocol handshake and request its tool list, then fingerprint that list.
- Do it againOne run is a snapshot. Re-running is what shows what broke, what recovered, and whose tools quietly changed. Two runs so far.
- We do not call any tool yet, so a server that starts may still have tools that fail.
- A server that needs an API key is reported as "needs key", not as broken. We test without credentials.
- This is not a security audit. Use a scanner for that, alongside this.
Get the briefing
Join the waiting list and we'll email you the briefing. Tell us which servers you rely on and you'll be first in line when re-testing and alerts open for early access.