Remote MCP · Endpoint

Calcgrid MCP server

Yes, as of 18 minutes ago: the server returned an HTTP error.

DownLast checked 18 minutes ago

Server URL

https://tttkmbb.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.tttkmbb/calcgrid
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
64 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
China working-day data, UK bank holidays, IANA time zones and deterministic business deadlines.
Listing
From the official MCP registry (active).
Recent checks of Calcgrid
CheckedResultHandshake
18 minutes agoFailed - the server returned an HTTP error—
9 days agoHandshake completed656 ms
9 days agoHandshake completed222 ms
11 days agoHandshake completed297 ms
12 days agoHandshake completed467 ms
13 days agoHandshake completed304 ms
14 days agoHandshake completed78 ms
14 days agoHandshake completed344 ms
16 days agoHandshake completed315 ms
19 days agoHandshake completed624 ms
21 days agoHandshake completed335 ms
24 days agoHandshake completed914 ms
26 days agoHandshake completed438 ms
28 days agoHandshake completed356 ms

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

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