Remote MCP · Endpoint

Uncertainty Calculator MCP server

No. Uncertainty Calculator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://uncertaintycalculator.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.quentintruong/uncertainty-calculator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Evaluate mathematical expressions and propagate measurement uncertainty.
Listing
From the official MCP registry (active).
Recent checks of Uncertainty Calculator
CheckedResultHandshake
1 hour agoHandshake completed74 ms
20 hours agoHandshake completed90 ms
1 day agoHandshake completed74 ms
2 days agoHandshake completed93 ms
4 days agoHandshake completed73 ms
7 days agoHandshake completed72 ms
9 days agoHandshake completed70 ms
12 days agoHandshake completed76 ms
14 days agoHandshake completed71 ms
16 days agoHandshake completed81 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed74 ms
22 days agoHandshake completed71 ms
23 days agoHandshake completed89 ms
25 days agoHandshake completed99 ms

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

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