Back to the tool index

get_schema

14 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
rationalbloks-backend
https://mcp.rationalbloks.com/mcp
answers-mcp 48
rarasnet-http
https://raras.org/api/mcp
answers-mcp 20
webhook-studio
https://webhook-studio.com/mcp
answers-mcp 17
clipkit
https://www.clipkit.dev/mcp
answers-mcp 15
Israel Business Intelligence MCP
https://israel-counterparty-intelligence.vercel.app/mcp
answers-mcp 13
insurance-advisor
https://whylingxi.cn/mcp
answers-mcp 9
TickerDB
https://mcp.tickerdb.com/mcp
answers-mcp 9
codecraft
https://codecraft-ashy-seven.vercel.app/mcp
answers-mcp 9
energetica-data
https://energetica.ar/api/mcp
answers-mcp 8
filingpulse
https://mcp.filingpulse.io/mcp
answers-mcp 7
structforge
https://structforge.askqa.app/mcp
answers-mcp 6
agent-papers
https://agentpapers.dev/api/mcp
answers-mcp 6
ClinicMarketIQ Public Data
https://clinicmarketiq-public-mcp.rotgar-fizkl.workers.dev/mcp
answers-mcp 6
reogrid-studio
https://api-studio.reogrid.net/studio/mcp
answers-mcp 4

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