get_schedule9 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 |
|---|---|---|
| SimpleFunctions
https://simplefunctions.dev/api/mcp/mcp |
answers-mcp | 108 |
| Laravel MCP Server
https://api.ceki.me/mcp/agent |
answers-mcp | 50 |
| pipeworx-gateway
https://gateway.pipeworx.io/f1/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/nhl/mcp |
answers-mcp | 35 |
| pipeworx-gateway
https://gateway.pipeworx.io/themeparks/mcp |
answers-mcp | 35 |
| turnale
https://mcp.turnale.app |
answers-mcp | 30 |
| my-tv-channel
https://my-tv-channel.com/api/mytvchannel/mcp |
answers-mcp | 19 |
| footdigest
https://footdigest.com/mcp |
answers-mcp | 14 |
| JKTJJ MCP Server
https://mcp.jktjj.com/mcp |
answers-mcp | 13 |
9 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.