Remote MCP · Endpoint

Chaiz MCP MCP server

No. Chaiz MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.chaiz.com/mcp

The last check completed an MCP handshake.

Registry name
com.chaiz/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
226 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Live vehicle warranty (service contract) quotes by VIN, plate, or make/model/year.
Listing
From the official MCP registry (active).
Recent checks of Chaiz MCP
CheckedResultHandshake
1 hour agoHandshake completed226 ms
2 days agoHandshake completed272 ms
4 days agoHandshake completed294 ms
5 days agoHandshake completed282 ms
7 days agoHandshake completed311 ms
8 days agoHandshake completed321 ms
9 days agoHandshake completed304 ms
12 days agoHandshake completed245 ms
13 days agoHandshake completed260 ms
15 days agoHandshake completed346 ms
16 days agoHandshake completed326 ms
17 days agoHandshake completed216 ms
18 days agoHandshake completed195 ms
19 days agoHandshake completed289 ms
20 days agoHandshake completed299 ms
21 days agoHandshake completed302 ms
22 days agoHandshake completed210 ms

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

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 Chaiz MCP and makes no claim about it beyond what these checks measured.