Back to the tool index

health_check

12 servers reported a tool by this name when we called them. Names are chosen by whoever wrote the server, so two tools sharing a name do not have to do the same thing. We record what was reported, not what it does.

serverresult when we called ittools
tunnelmind-data-api
https://mcp-data.tunnelmind.ai/mcp
answers-mcp 93
V12 DFS Optimizer
https://v12dfs-production.up.railway.app/mcp
answers-mcp 34
birthstar
https://mcp.birthstar.ai/mcp
answers-mcp 30
datamerge-mcp
https://mcp.datamerge.ai
answers-mcp 23
booking-hotel-mcp
https://api.waysway.com/mcp
answers-mcp 20
synapse-layer
https://forge.synapselayer.org/api/mcp
answers-mcp 13
numbrU API
https://numbru-mcp-server.numbru.workers.dev
answers-mcp 11
clawfetch
https://mcp.clawfetch.ai/mcp
answers-mcp 10
meetbot-mcp
https://mcp.meet.bot
answers-mcp 8
x402-agentic-router
https://amalgix.io/mcp
answers-mcp 8
kimchisushi-agent-mcp
https://kimchi-sushi.com/mcp
answers-mcp 6
health
https://health.getvda.ai/mcp
answers-mcp 5

12 of these answered an MCP handshake on the day we checked. That is not a promise the tool works, only that the server was running and told us the tool existed.