mcpbeat Sign in

Call Me MCP Server

by getcallme Your server? Claim it
answering

Call Me is answering right now. Last checked 15 min ago.

Calls your phone when an AI task finishes or is blocked — hear it, say what's next.

Uptime history 51 days of history · worst day 90%
51 days agonow
100.0%
Uptime 24h
90 of 90 checks
Tools
hidden behind auth
394 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Call Me every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add call-me --transport http https://getcallme.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "call-me": {
      "url": "https://getcallme.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.call-me]
url = "https://getcallme.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "call-me": {
      "url": "https://getcallme.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "call-me": {
      "url": "https://getcallme.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://getcallme.app/mcp streamable-http sign-in 607 ms 15 min ago

Alternatives to Call Me

same job, measured the same way
Selfping
by selfping

Text your own phone when a run finishes or needs you. A key can only message its own number.

1 tools answering
I
Next.js Architecture MCP
by hasimkilic

Indexes your Next.js project so an agent finds the file that owns a task in one call.

429 installs/wk local only
C
Ailis
by honeycomb-tech-ailis

Ailis (アイリス): put to-dos from an AI chat on your iPhone lock screen as a card.

answering
AgentWork Outcome Router
by mitchellopzero

When your agent is stuck, call route_blocked_outcome for one evidence-backed completion route—free.

10 tools answering
Keel
by tdalbanmoreynas

Catches your AI coding agent when it games the tests - locked-test hashes, tamper detection.

local only
MCP Notify
by mrfqcentic

Minimal MCP server that plays a sound and shows a system banner when an AI agent finishes a task

28 installs/wk local only
PhoneCallFor.me
by phonecallfor

Outbound phone calls placed by an AI voice agent to book, ask, or confirm on your behalf.

answering
Har Forensics MCP
by aryanspv

Tells you what leaked in a .har capture, who's on the page, and what to strip. No network calls.

44 installs/wk local only

Call Me — questions

Answers built from our own checks of this server.

Why is there no tool list for Call Me?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Call Me working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 394 ms. The bar chart above shows every period we have measured.
How do I connect Call Me?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Call Me?
No API key is involved. Call Me answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Call Me?
It answers our handshake in 394 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.