Back to the tool index

server_time

11 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
mock-mcp-server
https://obol-mcp.fly.dev/mcp
answers-mcp 3
mock-mcp-server
https://solidus-mcp.fly.dev/mcp
answers-mcp 3
mock-mcp-server
https://us-law-mcp.vercel.app/mcp
answers-mcp 3
mock-mcp-server
https://aegisgov-contracts.vercel.app/mcp
answers-mcp 3
mock-mcp-server
https://image-generator-x402-production.up.railway.app/mcp
answers-mcp 3
mock-mcp-server
https://kta-oracle.vercel.app/mcp
answers-mcp 3
mock-mcp-server
https://kta-oracle.vercel.app/sse
answers-mcp 3
mock-mcp-server
https://organic-text-mcp.vercel.app/api/mcp
answers-mcp 3
mock-mcp-server
https://agent-memory-production-6506.up.railway.app/sse
answers-mcp 3
mock-mcp-server
https://mcp-server-production-38c9.up.railway.app/sse
answers-mcp 3
mock-mcp-server
https://atlas-sooty-delta.vercel.app/api/mcp/mcp
answers-mcp 3

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