Connect Vin Recall and your agent gets 2 tools, among them check_recalls, decode_vin. It answers at https://vin-recall-mcp.zenithserver.duckdns.org/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 23 October 2026, succeeded.
Decodes US VINs and looks up open NHTSA safety recall campaigns for a vehicle.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_recalls | List open safety recall campaigns for a vehicle by VIN, using the NHTSA Recalls database. Decodes the VIN internally to get make/model/year, then looks up campaigns for that vehicle configuration. Important: results are recall campaigns iss Inputs: vin |
decode_vin | Decode a 17-character US vehicle VIN into make, model, year, body class, engine cylinders, fuel type, drive type, and assembly plant country, using the NHTSA vPIC database. Covers US-market vehicles built from 1981 onward (the 17-character Inputs: vin |
Every block below points at https://vin-recall-mcp.zenithserver.duckdns.org/mcp. Pick your client and copy.
claude mcp add --transport http vin-recall https://vin-recall-mcp.zenithserver.duckdns.org/mcp
{
"mcpServers": {
"vin-recall": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"]
}
}
}{
"mcpServers": {
"vin-recall": {
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"servers": {
"vin-recall": {
"type": "http",
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"context_servers": {
"vin-recall": {
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"mcpServers": {
"vin-recall": {
"serverUrl": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"mcpServers": {
"vin-recall": {
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}name: Vin Recall
version: 0.0.1
schema: v1
mcpServers:
- name: Vin Recall
type: streamable-http
url: https://vin-recall-mcp.zenithserver.duckdns.org/mcp{
"mcpServers": {
"vin-recall": {
"httpUrl": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"mcpServers": {
"vin-recall": {
"type": "http",
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}{
"mcpServers": {
"vin-recall": {
"url": "https://vin-recall-mcp.zenithserver.duckdns.org/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvin-recall-mcp.zenithserver.duckdns.org%2Fmcp&type=streamable_http&id=vin-recall&name=Vin%20Recall
It answered our last check on 23 October 2026 in 691 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
2, as returned by the server's own tools/list on 18 September 2026: check_recalls, decode_vin.
It answered our last check on 23 October 2026 in 691 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vin-recall-mcp.zenithserver.duckdns.org/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.pratikmehkarkar. Endpoint host: vin-recall-mcp.zenithserver.duckdns.org. ARD identifier: urn:air:io.github.pratikmehkarkar:mcp:vin-recall-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.