web_search22 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 |
|---|---|---|
| gapup-mcp
https://mcp.gapup.io/mcp |
answers-mcp | 279 |
| gapup-mcp
https://mcp.gapup.io |
answers-mcp | 279 |
| AgentServices
https://agentservices.to/mcp |
answers-mcp | 64 |
| com.wingmanprotocol.agent/gateway
https://agent.wingmanprotocol.com/mcp |
answers-mcp | 57 |
| com.wingmanprotocol.agent/gateway
https://wingmanprotocol.com/mcp |
answers-mcp | 57 |
| agentdata-nl
https://agentdata-api.sander-van-aard.workers.dev/mcp |
answers-mcp | 51 |
| pipeworx-gateway
https://gateway.pipeworx.io/brave-search/mcp |
answers-mcp | 33 |
| alya-hub
https://mydaughteralya.com/mcp |
answers-mcp | 32 |
| reelfy-agent-tools
https://api.reelfy.online/mcp |
answers-mcp | 24 |
| Toolsmith
https://toolcall.click/mcp |
answers-mcp | 22 |
| dacix-store
https://dacix.store/mcp |
answers-mcp | 19 |
| agent402
https://agent402.tools/mcp |
answers-mcp | 15 |
| skill-audit
https://eltociear-skill-audit.hf.space/mcp |
answers-mcp | 11 |
| srezai
https://srezai.ru/api/mcp |
answers-mcp | 10 |
| tokenguard
https://eltociear-tokenguard.hf.space/mcp |
answers-mcp | 9 |
| lmxcloud-mcp
https://mcp.lmxcloud.io/mcp |
answers-mcp | 9 |
| web-access-gateway
https://web-access-gateway.mattskowronis.workers.dev/mcp |
answers-mcp | 8 |
| texttostl
https://api.texttostl.com/mcp |
answers-mcp | 4 |
| agent-search-pro
https://aggregator-beta.vercel.app/mcp |
answers-mcp | 3 |
| agentsearch
https://agentsearch-mcp.vercel.app/mcp |
answers-mcp | 3 |
| forage
https://forage.cash/mcp |
answers-mcp | 2 |
| neurobird-search
https://search.neurobird.com/mcp |
answers-mcp | 2 |
22 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.