Remote MCP · Endpoint

call4me MCP server

No — it is up, but it requires credentials. call4me answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://call4.me/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.github.skeptrunedev/call4me
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MCP server for making phone calls: your agent books, cancels, asks and waits on hold for you.
Listing
From the official MCP registry (active).
Recent checks of call4me
CheckedResultHandshake
1 hour agoCredentials required—
2 days agoCredentials required—
4 days agoCredentials required—
7 days agoCredentials required—
9 days agoCredentials required—
11 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
19 days agoCredentials required—
20 days agoCredentials required—
23 days agoCredentials required—
24 days agoCredentials required—

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