Remote MCP · Endpoint

MOT Check MCP server

No. MOT Check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://motcheck.io/mcp

The last check completed an MCP handshake.

Registry name
io.motcheck/mot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
172 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
UK vehicle lookup, MOT status and full MOT history from official DVSA data, by registration.
Website
https://motcheck.io/ai
Listing
From the official MCP registry (active).
Recent checks of MOT Check
CheckedResultHandshake
1 hour agoHandshake completed172 ms
9 days agoHandshake completed184 ms
10 days agoHandshake completed253 ms
11 days agoHandshake completed194 ms
12 days agoHandshake completed185 ms
14 days agoHandshake completed261 ms
14 days agoHandshake completed526 ms
15 days agoHandshake completed323 ms
17 days agoHandshake completed207 ms
19 days agoHandshake completed177 ms
21 days agoHandshake completed508 ms
24 days agoHandshake completed402 ms
26 days agoHandshake completed185 ms
28 days agoHandshake completed202 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with MOT Check and makes no claim about it beyond what these checks measured.