MCP directory · probed every 30 min
Pick MCP servers that actually answer.
Probebase lists MCP servers and agent tools and tests every one on a schedule: does it answer, how fast, and did its tool list change since the last check.
- CH1Upanswered
initialize - CH2Up · authanswered 401 / 403, sign-in required
- CH3Downno answer within 12 s
- CH4Pendingwaiting for its first probe
01
On the bench
Servers with the best record over the last seven days.
No servers listed yet
A server shows up here once it has answered its first probe. Submit yours and it can be the first.
02
What every probe records
We connect the way an agent would, then hang up. Tools are never called.
-
CH1
Does it answer
requestresultA full MCP handshake. A server that asks for sign-in still counts as answering.
- Handshake
initialize→notifications/initialized- Transports
- Streamable HTTP, legacy HTTP + SSE
- 401 / 403
- counts as answering
-
CH2
How fast
round trip12 sTime from our request to the server’s reply, kept for every check so you see the trend, not one lucky ping.
- Measured
initializeround trip- Timeout
- 12 s
- History
- every check, kept 90 days
-
CH3
Did the tools change
+ added− removed~ changedThe tool list is fingerprinted on each check. Any difference lands in the listing’s change log.
- Request
tools/list, all pages, up to 500 tools- Fingerprint
- SHA-256 of the list, every check
- Change log
- added · removed · changed
03
A live badge for your README
Submit your server’s URL. Its listing page gives you a Markdown badge that shows the current state from the latest probe.
04
Probing, politely
Checks are light enough that no server owner should notice them.
- Requests per check
initialize,notifications/initialized,tools/list, then the session is closed- Interval
- Every 30 minutes per server
- Tool calls
- Never
- Identifies as
ProbebaseBot/1.0- Redirects
- Not followed; list the final URL
- Timeout
- 12 seconds, replies over 1 MB are cut off