Remote MCP · Endpoint

NBMEcalc MCP MCP server

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

UpLast checked 1 hour ago

Server URL

https://nbmecalc-mcp.chenxuanshimo.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.jiankn/nbmecalc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
709 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Remote MCP server for deterministic educational practice-assessment score conversions.
Listing
From the official MCP registry (active).
Recent checks of NBMEcalc MCP
CheckedResultHandshake
1 hour agoHandshake completed709 ms
2 days agoHandshake completed815 ms
4 days agoHandshake completed1.46 s
6 days agoHandshake completed978 ms
8 days agoHandshake completed883 ms
10 days agoHandshake completed1.32 s
11 days agoHandshake completed1.34 s
13 days agoHandshake completed1.63 s
14 days agoHandshake completed1.57 s
15 days agoHandshake completed410 ms
18 days agoHandshake completed1.09 s
19 days agoHandshake completed824 ms
21 days agoHandshake completed1.03 s
22 days agoHandshake completed745 ms
23 days agoHandshake completed832 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 NBMEcalc MCP and makes no claim about it beyond what these checks measured.