Back to the tool index

semantic_search

13 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
ccpedia
https://ccpedia.xyz/mcp
answers-mcp 88
DC Hub Intelligence
https://dchub.cloud/mcp/officialregistry
answers-mcp 83
DC Hub Intelligence
https://dchub.cloud/mcp
answers-mcp 83
DC Hub Intelligence
https://dchub.cloud/mcp/registry
answers-mcp 83
agendaforge-mcp
https://mcp.agendaforge.app/mcp
answers-mcp 55
blobpedia
https://blobpedia.org/mcp
answers-mcp 44
whiteintel-mcp-server
https://whiteintel.dev/api/mcp
answers-mcp 24
3gpp-spec-server
https://mcp.specproof.ai/
answers-mcp 17
zoning-signal
https://zoningsignal.com/mcp
answers-mcp 17
teppek
https://mcp.teppek.com/mcp
answers-mcp 16
redm-mcp
https://redm-mcp.fivem.no/mcp
answers-mcp 10
wem-marketplace
https://wem3.ai/api/mcp
answers-mcp 9
roboparts
https://roboparts.cc/mcp
answers-mcp 9

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