sanctions_screen11 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.
| server | result when we called it | tools |
|---|---|---|
| Dynamic Feed
https://dynamicfeed.ai/mcp |
answers-mcp | 94 |
| x402-endpoints
https://x402-endpoints.onrender.com/mcp/ |
answers-mcp | 52 |
| healthparse-gateway
https://api.healthparse.io/mcp |
answers-mcp | 42 |
| Ohmyfin Banking Intelligence
https://mcp.ohmyfin.ai/mcp |
answers-mcp | 34 |
| pipeworx-gateway
https://gateway.pipeworx.io/sanctions-screening/mcp |
answers-mcp | 34 |
| temsor API
https://api.temsor.com/mcp |
answers-mcp | 31 |
| synthora-mcp
https://mcp.hergertsynthora.com/mcp |
answers-mcp | 30 |
| uk_due_diligence_mcp
https://uk-due-diligence-mcp.fly.dev/mcp |
answers-mcp | 19 |
| sausage-trust
https://x402.professorsausages.com/mcp/trust |
answers-mcp | 12 |
| AMLOracle
https://tooloracle.io/aml/mcp/ |
answers-mcp | 12 |
| x402-endpoints
https://x402-solana-cva8.onrender.com/mcp/ |
answers-mcp | 10 |
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.