get_more_tools11 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 |
|---|---|---|
| metagraphed
https://api.metagraph.sh/mcp |
answers-mcp | 243 |
| clipform-mcp-server
https://mcp.clipform.io |
answers-mcp | 34 |
| batru-mcp
https://batru.gg/mcp |
answers-mcp | 33 |
| elc-partnership-builder
https://www.engineeringleaders.io/mcp/partnership |
answers-mcp | 12 |
| eng-leadership-toolkit
https://www.marian.coach/mcp |
answers-mcp | 11 |
| mentoring-inquiry-builder
https://www.marian.coach/mcp/mentoring |
answers-mcp | 10 |
| elc-trade
https://www.engineeringleaders.io/mcp/trade |
answers-mcp | 8 |
| elc-conference-mcp-tickets
https://mcp.elc-conference.io/mcp |
answers-mcp | 8 |
| Weav Customer Service
https://weav.com/mcp |
answers-mcp | 6 |
| Redpanda Docs MCP
https://docs.redpanda.com/mcp |
answers-mcp | 5 |
| elc-toolkit
https://www.engineeringleaders.io/mcp |
answers-mcp | 5 |
11 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.