Back to the tool index

list_endpoints

17 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
echorelay-mcp
https://mcp.echorelay.dev
answers-mcp 79
relin-mcp
https://relin.app/mcp
answers-mcp 52
reelfy-agent-tools
https://api.reelfy.online/mcp
answers-mcp 24
MCP Energy Data
https://entsoemcp.com/mcp
answers-mcp 14
HookPulse
https://hookpulse.net/mcp
answers-mcp 14
nordic-data-mcp
https://nordic-data-mcp-production.up.railway.app/mcp/auth
answers-mcp 11
ai-rook
https://agents.ai-rook.com/mcp
answers-mcp 10
steamwebapi
https://mcp.steamwebapi.com/mcp
answers-mcp 10
branch-app-group
https://docs.branchapp.com/mcp
answers-mcp 8
prism
https://enrich.gocreativeai.com/mcp
answers-mcp 5
omnicall
https://omnicall.gocreativeai.com/mcp
answers-mcp 5
predict
https://predict.gocreativeai.com/mcp
answers-mcp 5
MarketCheck Docs
https://developers.marketcheck.com/api/docs-mcp
answers-mcp 5
Solana API & WebSocket Docs
https://mcp.vybenetwork.xyz
answers-mcp 5
Solana API & WebSocket Docs
https://docs.vybenetwork.com/mcp
answers-mcp 5
BenjiPays
https://benjipays.readme.io/mcp
answers-mcp 4
BenjiPays
https://developer.benjipays.com/mcp
answers-mcp 4

17 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.