Remote MCP · Endpoint

Plateop vehicle check MCP server

No. Plateop vehicle check answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://check.plateop.com/mcp

The last check completed an MCP handshake.

Registry name
com.plateop/plateop-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
438 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free used-car facts from the official register (NL, GB, IL, IS, DK) with source and date.
Listing
From the official MCP registry (active).
Recent checks of Plateop vehicle check
CheckedResultHandshake
4 hours agoHandshake completed438 ms
10 days agoHandshake completed368 ms
11 days agoHandshake completed433 ms
11 days agoHandshake completed386 ms
13 days agoHandshake completed360 ms
14 days agoHandshake completed383 ms
15 days agoHandshake completed370 ms
16 days agoHandshake completed371 ms
17 days agoHandshake completed363 ms
19 days agoHandshake completed457 ms
22 days agoHandshake completed435 ms
24 days agoHandshake completed393 ms
26 days agoHandshake completed391 ms
29 days agoHandshake completed359 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 Plateop vehicle check and makes no claim about it beyond what these checks measured.