search_icons10 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 |
|---|---|---|
| pipeworx-gateway
https://gateway.pipeworx.io/iconify/mcp |
answers-mcp | 34 |
| svgicons-mcp
https://svgicons.com/mcp |
answers-mcp | 12 |
| infyicon
https://infyicon.com/mcp |
answers-mcp | 8 |
| digche-icons
https://digche.vercel.app/api/mcp |
answers-mcp | 6 |
| StatelessServer
https://design.googleapis.com/mcp |
answers-mcp | 5 |
| supericons
https://mcp.supericons.dev/mcp |
answers-mcp | 5 |
| iconserve
https://iconserve.icons-for-agents.workers.dev/mcp |
answers-mcp | 3 |
| iconserve
https://icons-for-agents.site/mcp |
answers-mcp | 3 |
| iconlab
https://iconlab.op0.workers.dev/mcp |
answers-mcp | 3 |
| iconlab
https://iconlab.skillkit.run/mcp |
answers-mcp | 3 |
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.