Remote MCP · Endpoint

Call2Me MCP server

No. Call2Me answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.call2me.app/mcp

The last check completed an MCP handshake.

Registry name
app.call2me/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
350 ms
Tools exposed
74 tools
Uptime, last 30 days
81.3% from 16 checks
Described by its publisher as
Place real phone calls, read transcripts, run a live interpreter and buy numbers.
Listing
From the official MCP registry (active).
Recent checks of Call2Me
CheckedResultHandshake
1 hour agoHandshake completed350 ms
6 hours agoHandshake completed310 ms
2 days agoHandshake completed300 ms
4 days agoHandshake completed516 ms
7 days agoHandshake completed300 ms
9 days agoHandshake completed302 ms
11 days agoHandshake completed295 ms
13 days agoHandshake completed294 ms
15 days agoHandshake completed293 ms
17 days agoHandshake completed297 ms
19 days agoHandshake completed291 ms
21 days agoHandshake completed296 ms
23 days agoHandshake completed310 ms
24 days agoFailed - the server returned an HTTP error—
25 days agoFailed - the server returned an HTTP error—
27 days agoFailed - the server returned an HTTP error—

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

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