Remote MCP · Endpoint

recallsapi.com US recalls MCP server

No. recallsapi.com US recalls answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.recallsapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.recallsapi/recallsapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
44 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Is it recalled? US recalls from 9 agencies by UPC, model, NDC, VIN or lot. Its API also takes x402.
Listing
From the official MCP registry (active).
Recent checks of recallsapi.com US recalls
CheckedResultHandshake
2 hours agoHandshake completed44 ms
20 hours agoHandshake completed71 ms
2 days agoHandshake completed80 ms
4 days agoHandshake completed83 ms
6 days agoHandshake completed84 ms
9 days agoHandshake completed73 ms
11 days agoHandshake completed115 ms
13 days agoHandshake completed80 ms
15 days agoHandshake completed349 ms
17 days agoHandshake completed85 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed106 ms
23 days agoHandshake completed84 ms
24 days agoHandshake completed108 ms

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

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 recallsapi.com US recalls and makes no claim about it beyond what these checks measured.