Remote MCP · Endpoint

Recallroll MCP server

No. Recallroll answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://recallroll-api.cybermax-tools.workers.dev/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/recallroll-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
239 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
VIN recall API + MCP: VIN decode + every NHTSA recall, Do Not Drive first. $19/mo; 50 free/day.
Listing
From the official MCP registry (active).
Recent checks of Recallroll
CheckedResultHandshake
1 hour agoHandshake completed239 ms
2 days agoHandshake completed140 ms
4 days agoHandshake completed114 ms
6 days agoHandshake completed1.66 s
8 days agoHandshake completed413 ms
10 days agoHandshake completed105 ms
12 days agoHandshake completed123 ms
13 days agoHandshake completed81 ms
14 days agoHandshake completed363 ms
15 days agoHandshake completed91 ms
18 days agoHandshake completed84 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed89 ms
24 days agoHandshake completed84 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Recallroll and makes no claim about it beyond what these checks measured.