Remote MCP · Endpoint

Canvas Medical 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://canvas-medical.usefulapi.io/mcp

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

Registry name
io.usefulapi/canvas-medical
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search and read a patient chart over the Canvas FHIR R4 API. Read-only.
Listing
From the official MCP registry (active).
Recent checks of Canvas Medical MCP by usefulapi
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoHandshake completed293 ms
4 days agoHandshake completed531 ms
6 days agoHandshake completed296 ms
8 days agoHandshake completed366 ms
10 days agoHandshake completed224 ms
12 days agoHandshake completed231 ms
14 days agoHandshake completed296 ms
15 days agoHandshake completed221 ms
16 days agoHandshake completed250 ms
17 days agoHandshake completed151 ms
20 days agoHandshake completed203 ms
22 days agoHandshake completed172 ms
23 days agoHandshake completed249 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 13 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Canvas Medical MCP by usefulapi and makes no claim about it beyond what these checks measured.