decode_vin8 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/nhtsa/mcp |
answers-mcp | 37 |
| carrepaircostestimator
https://carrepaircostestimator.com/mcp |
answers-mcp | 7 |
| nhtsa
https://mcp.olyport.com/nhtsa/mcp |
answers-mcp | 6 |
| fabtally-valid
https://valid.fabtally.com/mcp |
answers-mcp | 5 |
| com.usecarscout/mcp
https://mcp.usecarscout.com/mcp |
answers-mcp | 3 |
| VIN Recall MCP
https://vin-recall-mcp.zenithserver.duckdns.org/mcp |
answers-mcp | 2 |
| checkmyvin
https://checkmyvin.net/api/mcp |
answers-mcp | 2 |
| VinData MCP
https://vindata-mcp.vindata.workers.dev/mcp |
answers-mcp | 1 |
8 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.