Remote MCP · Endpoint

MedBillAnalyzer MCP server

No. MedBillAnalyzer answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.medbillanalyzer.com/mcp/apps?via=mcp_registry

The last check completed an MCP handshake.

Registry name
com.medbillanalyzer/medbillanalyzer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
257 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Compares a medical bill with the insurer's Explanation of Benefits and lists where they disagree.
Listing
From the official MCP registry (active).
Recent checks of MedBillAnalyzer
CheckedResultHandshake
1 hour agoHandshake completed257 ms
1 day agoHandshake completed188 ms
2 days agoHandshake completed165 ms
3 days agoHandshake completed157 ms
4 days agoHandshake completed171 ms
5 days agoHandshake completed295 ms
6 days agoHandshake completed315 ms
9 days agoHandshake completed149 ms
11 days agoHandshake completed149 ms
14 days agoHandshake completed375 ms
16 days agoHandshake completed149 ms
18 days agoHandshake completed178 ms
20 days agoHandshake completed467 ms
22 days agoHandshake completed339 ms
24 days agoHandshake completed144 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 MedBillAnalyzer and makes no claim about it beyond what these checks measured.