Remote MCP · Endpoint

Verzi Health MCP server

No. Verzi Health answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://mcp.verzi.health/mcp

The last check completed an MCP handshake.

Registry name
health.verzi/receipt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
38 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Medicare DME coverage by HCPCS code and date of service, with CMS citations and signed receipts.
Listing
From the official MCP registry (active).
Recent checks of Verzi Health
CheckedResultHandshake
56 minutes agoHandshake completed38 ms
3 days agoHandshake completed144 ms
12 days agoHandshake completed39 ms
13 days agoHandshake completed32 ms
15 days agoHandshake completed29 ms
15 days agoHandshake completed37 ms
17 days agoHandshake completed32 ms
18 days agoHandshake completed36 ms
18 days agoHandshake completed52 ms
20 days agoHandshake completed29 ms
22 days agoHandshake completed30 ms
25 days agoHandshake completed31 ms
27 days agoHandshake completed38 ms

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

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