Remote MCP · Endpoint

Privi Call MCP server

Yes, as of 57 minutes ago: the server returned an HTTP error.

DownLast checked 57 minutes ago

Server URL

https://privi-call.onrender.com/mcp

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

Registry name
io.github.canoydario847-cloud/privi-call
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
One number per AI agent: route MCP calls to any agent, every call sealed in an on-chain log.
Listing
From the official MCP registry (active).
Recent checks of Privi Call
CheckedResultHandshake
57 minutes agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed60 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed60 ms
15 days agoHandshake completed52 ms
17 days agoHandshake completed54 ms
18 days agoHandshake completed61 ms
18 days agoHandshake completed44 ms
20 days agoHandshake completed92 ms
22 days agoHandshake completed63 ms
25 days agoHandshake completed229 ms
27 days agoHandshake completed60 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 Privi Call and makes no claim about it beyond what these checks measured.