Remote MCP · Endpoint

Calcgrid MCP server

No. Calcgrid answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

https://tttkmbb.com/mcp

The last check completed an MCP handshake.

Registry name
com.tttkmbb/calcgrid
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
356 ms
Tools exposed
64 tools
Uptime, last 30 days
100% from 16 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
55 minutes agoHandshake completed356 ms
2 days agoHandshake completed360 ms
4 days agoHandshake completed354 ms
6 days agoHandshake completed42 ms
7 days agoHandshake completed317 ms
9 days agoHandshake completed336 ms
10 days agoHandshake completed604 ms
11 days agoHandshake completed375 ms
14 days agoHandshake completed261 ms
15 days agoHandshake completed589 ms
17 days agoHandshake completed286 ms
18 days agoHandshake completed889 ms
19 days agoHandshake completed214 ms
21 days agoHandshake completed201 ms
22 days agoHandshake completed218 ms
22 days agoHandshake completed258 ms

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

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.