Remote MCP · Endpoint

NexHealth MCP by usefulapi MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://nexhealth.usefulapi.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.usefulapi/nexhealth
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
16 tools
Uptime, last 30 days
50.0% from 14 checks
Described by its publisher as
Read and write NexHealth appointments, patients, providers and locations.
Website
https://usefulapi.io/nexhealth/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of NexHealth MCP by usefulapi
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed480 ms
4 days agoHandshake completed303 ms
6 days agoHandshake completed188 ms
8 days agoHandshake completed395 ms
10 days agoHandshake completed1.32 s
12 days agoHandshake completed368 ms
14 days agoHandshake completed192 ms
15 days agoFailed - the check failed for an unclassified reason—
16 days agoFailed - the check failed for an unclassified reason—
17 days agoFailed - the check failed for an unclassified reason—
20 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

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

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