search_filings10 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 |
|---|---|---|
| slacking-biz
https://slacking.biz/mcp |
answers-mcp | 75 |
| tw-market-data
https://mcp.twmarketdata.com/mcp |
answers-mcp | 41 |
| pipeworx-gateway
https://gateway.pipeworx.io/sec-xbrl/mcp |
answers-mcp | 39 |
| pipeworx-gateway
https://gateway.pipeworx.io/senate-lobbying/mcp |
answers-mcp | 34 |
| edgrapi
https://api.edgrapi.com/mcp |
answers-mcp | 15 |
| FilingAPI
https://mcp.filingapi.dev/mcp |
answers-mcp | 10 |
| nordic-public-data-mcp
https://mcp.aidatanorge.no/mcp |
answers-mcp | 7 |
| sec-intel
https://filings.dropwatchhq.com/mcp |
answers-mcp | 5 |
| SEC Filings Agent Marketplace
https://sec-filings-mcp-1065601264332.us-central1.run.app/mcp |
answers-mcp | 3 |
| edinet-mcp
https://edinet-mcp.easakura.workers.dev/mcp |
answers-mcp | 2 |
10 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.