Remote MCP servers, ranked by how often they answer
Every guide here ranks by one measurement: how often this site's scheduled connection test reached a server in the last 30 days. A connection test sends the MCP handshake and asks for the tool list, with no key. Reaching a server means it answered, or answered that it needs a key.
It does not test what the tools do, whether they do it correctly, where your data goes, or whether the server is safe to use. A server that is always up can still be the wrong one to connect to.
- Scheduled tests, last 30 days
- 4,704
- Servers tested
- 4,702
- With 5 or more tests
- 0
- Left out, under 5 tests
- 4,702
The guides
No category has enough measured servers yet.
4,705 connection tests have been recorded so far (4,704 of them scheduled), the first on 30 September 2026 at 14:51 UTC. A server is ranked once it has 5 scheduled tests inside 30 days, and a category is published once 3 servers in it are ranked. Until then there is no guide to publish, and this page will not print one built on less.
How a guide is built
- Only scheduled tests count. A visitor's test is shown on the server's page and never counted here, so nobody can raise a rate by testing a server while it is up.
- A test counts when it reached the server or failed to. One this site declined to send is not a result about the server.
- A server needs 5 scheduled tests in the last 30 days. The 4,702 with fewer are left out of every guide.
- Order: the share of tests that reached it, then the median handshake time, then the number of tests.
- A category is published once 3 servers in it are ranked.
What a guide is not
Not a verification. A server in the free directory publishes no source and nothing about it has been read; a catalogue listing's own page says what was read and at which commit. Categories for directory entries come from the catalogue's keyword rules run over the registry's own description, and can be wrong.
Read from the tests table at 7 October 2026 at 03:38 UTC.