Remote MCP · Endpoint

com.medigami/mcp MCP server

No. com.medigami/mcp answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.medigami.com/public/mcp

The last check completed an MCP handshake.

Registry name
com.medigami/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
182 ms
Tools exposed
87 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Medigami: medical bill error scan, denial decoding, appeal deadlines, hospital price lookup
Website
https://medigami.com/mcp
Listing
From the official MCP registry (active).
Recent checks of com.medigami/mcp
CheckedResultHandshake
9 hours agoHandshake completed182 ms
2 days agoHandshake completed182 ms
4 days agoHandshake completed169 ms
5 days agoHandshake completed193 ms
7 days agoHandshake completed173 ms
8 days agoHandshake completed187 ms
9 days agoHandshake completed186 ms
12 days agoHandshake completed179 ms
13 days agoHandshake completed180 ms
15 days agoHandshake completed189 ms
16 days agoHandshake completed196 ms
17 days agoHandshake completed196 ms
19 days agoHandshake completed175 ms
19 days agoHandshake completed227 ms
20 days agoHandshake completed227 ms
21 days agoHandshake completed205 ms
22 days agoHandshake completed198 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.medigami/mcp and makes no claim about it beyond what these checks measured.