list_sites14 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.
| server | result when we called it | tools |
|---|---|---|
| mcp-typescript server on vercel
https://shiply.now/mcp |
answers-mcp | 114 |
| orbiteos
https://mcp.orbiteos.cloud/sse |
answers-mcp | 61 |
| spook-seo-tools
https://www.tryspook.com/api/mcp |
answers-mcp | 59 |
| vibedeploy
https://mcp.vibedeploy.be/mcp |
answers-mcp | 39 |
| dataecho
https://dataecho.ai/mcp |
answers-mcp | 26 |
| synchronity-mcp
https://api.synchronity.app/mcp |
answers-mcp | 26 |
| valet
https://api.valet.dev/mcp |
answers-mcp | 16 |
| Staats
https://api.staats.ai/functions/v1/mcp |
answers-mcp | 15 |
| webdex
https://iskat.io/mcp |
answers-mcp | 14 |
| foliora
https://www.foliora.ai/mcp |
answers-mcp | 13 |
| sitectrl
https://mcp.sitectrl.ai/mcp |
answers-mcp | 12 |
| devdome-analytics
https://analytics.devdome.com/mcp |
answers-mcp | 10 |
| revenuescope-mcp
https://mcp.revenuescope.jp/api/mcp |
answers-mcp | 10 |
| agentready
https://www.agentready.it.com/api/mcp |
answers-mcp | 8 |
14 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.