Back to the tool index

search_services

18 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
lobex
https://lobex.app/mcp
answers-mcp 26
vibesprings
https://vibesprings.net/mcp
answers-mcp 25
fiatdock
https://fiatdock.com/mcp
answers-mcp 18
crossfin
https://crossfin.dev/api/mcp
answers-mcp 16
kirah-local-services
https://kirah.ai/api/mcp-registry-v1
answers-mcp 10
agentwork
https://agent-work-api.agentwork-market.workers.dev/mcp
answers-mcp 10
nAIm
https://mcp.naim.janis7ewski.org/sse
answers-mcp 7
nAIm
https://mcp.naim.janis7ewski.org/mcp
answers-mcp 7
botfriendly
https://www.botfriendly.xyz/api/mcp
answers-mcp 7
servana
https://servana.ai/api/mcp
answers-mcp 5
fixidu
https://mcp.fixidu.com/mcp
answers-mcp 5
sipiteno-mcp
https://sipiteno.com/api/mcp
answers-mcp 5
kirah-local-services-directory
https://kirah.ai/api/mcp-directory-v1
answers-mcp 5
issoh-co-jp
https://www.issoh.co.jp/mcp
answers-mcp 5
hooddue
https://hooddue.artificl.us/mcp
answers-mcp 5
vouchtrail
https://vouchtrail.com/mcp
answers-mcp 3
kansei-link
https://kansei-link-mcp-production-b054.up.railway.app/mcp
answers-mcp 3
YloService
https://yloservice.com/mcp
answers-mcp 1

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