Remote MCP · Endpoint

VIN Decoder + Safety Recalls (NHTSA) MCP server

No. VIN Decoder + Safety Recalls (NHTSA) answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://vin-decode-production.up.railway.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.pcp183/vin-decode
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
123 ms
Tools exposed
1 tool
Uptime, last 30 days
7.1% from 14 checks
Described by its publisher as
Decode a VIN and list NHTSA recalls for that model (US data). $0.003/call via x402.
Listing
From the official MCP registry (active).
Recent checks of VIN Decoder + Safety Recalls (NHTSA)
CheckedResultHandshake
13 minutes agoHandshake completed123 ms
10 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 2 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with VIN Decoder + Safety Recalls (NHTSA) and makes no claim about it beyond what these checks measured.