Remote MCP · Endpoint

MRIPrices MCP server

No. MRIPrices answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mriprices.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.mriprices/mriprices
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
521 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cash-pay MRI prices at 5,419 US hospitals.
Website
https://mriprices.fyi/
Listing
From the official MCP registry (active).
Recent checks of MRIPrices
CheckedResultHandshake
2 hours agoHandshake completed521 ms
1 day agoHandshake completed219 ms
3 days agoHandshake completed185 ms
3 days agoHandshake completed93 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed110 ms
7 days agoHandshake completed431 ms
10 days agoHandshake completed1.65 s
12 days agoHandshake completed130 ms
15 days agoHandshake completed186 ms
17 days agoHandshake completed87 ms
19 days agoHandshake completed356 ms
21 days agoHandshake completed135 ms
23 days agoHandshake completed100 ms
25 days agoHandshake completed189 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.

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