Back to the tool index

estimate_cost

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
meta-council
https://meta-council.com/mcp
answers-mcp 150
uwear
https://api.uwear.ai/mcp
answers-mcp 67
PowerSun
https://powersun.vip/mcp
answers-mcp 27
lumify-mcp
https://lumify.ai/mcp
answers-mcp 25
meacheal-supply-chain
https://api.meacheal.ai/mcp
answers-mcp 20
x402-agentic-router
https://amalgix.io/mcp
answers-mcp 8
studiosphere-pulse
https://mcp.studiosphere.space/mcp
answers-mcp 8
ranomics-mcp
https://mcp.ranomics.com/mcp
answers-mcp 7
Philadelphia Restoration
https://mcp.philadelphiarestoration.org/mcp
answers-mcp 7
modelmeter
https://modelmeter.xyz/mcp
answers-mcp 7
quotefirst
https://quotefirst.ai/api/mcp
answers-mcp 6
ai-token-counter
https://api.lazy-mac.com/ai-token-counter/mcp
answers-mcp 4
api-response-cost-analyzer-mcp
https://api.lazy-mac.com/api-response-cost-analyzer/mcp
answers-mcp 4
pennyocr
https://mcp.pennyocr.com
answers-mcp 2

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.