Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Call Me

REMOTE · CALLMEMCP.COM

Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text.

Available components

+3 this week 65 Trust /100

Last scanned (2 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1770 tokens (~221/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Oct 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “hang_up”, which the server declares destructive security
    • New tool “say”, which the server declares destructive security
    • Tool “call” rewrote its description, which is the text the model reads security
    • Schema quality: 1233 → 1770 ▼ functional
    • “call” added an optional parameter “keep_open” cosmetic
    • “call” added an optional parameter “language” cosmetic
  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +1
    • Stability: unverified → 0.10 ▲ functional
  • 4 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://callmemcp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=callmemcp.com CN=YE1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA384 5ed5fbccfa95bdb8978207cf62bf8632f4d
SANs: callmemcp.com, www.callmemcp.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of callmemcp.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
callmemcp.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://callmemcp.com/mcp Verified 200
http (plaintext) http://callmemcp.com/mcp HTTPS enforced 301 https://callmemcp.com/mcp
MCP tools · 8 exposed · ~882 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call ~281

Ring the human's iPhone, read `question` aloud word for word, and return what they say back. It does not have to be a question: an update or a summary of the day ahead works too, up to 2000 characters (about two minutes of speech). Waits up to ~30s; if the result comes back status "ringing" or "in_call", follow up with poll_result. On a local client, read `to` from `~/.aiphone/config.json` → `user_number`; this hosted server cannot read that file itself. It is a Call Me app number, not a regular phone number. If missing, returns setup_required with the App Store link. Pass a previous session_token to stay in the same thread on their phone. keep_open=true makes it a conversation: after their answer the line stays up for `say` until you `hang_up`. `language` ("tr", "de", ...) is the language you are speaking; the call's own short lines follow it. Default English.

NameTypeReqDescription
from_labelstring––
keep_openboolean––
languagestring––
questionstringyes–
session_token–––
to–––

No output schema declared.

No examples provided.

hang_up ~71

End a call you placed. In a keep_open conversation `goodbye` is spoken first (e.g. "Thanks, I'll get on it."); leave it empty to just hang up.

NameTypeReqDescription
call_idintegeryes–
goodbyestring––
session_tokenstringyes–

No output schema declared.

No examples provided.

poll_result ~76

Check on a call that was still ringing or in progress. Waits up to ~25s for it to settle; returns the final status and transcript once the call ends, the human declines, or the ring times out ("missed").

NameTypeReqDescription
call_idintegeryes–
session_tokenstringyes–

No output schema declared.

No examples provided.

say ~151

In a call placed with keep_open=true, speak `text` to the human and return what they answer, in the same shape as `call`. Only after their previous answer is in. Waits up to ~30s; on "in_call", follow up with poll_result. "open": false means the call has ended. Pass `language` only to switch the language of the call's own lines; empty keeps it. Anything they said while you were thinking comes back as "said_while_waiting".

NameTypeReqDescription
call_idintegeryes–
languagestring––
session_tokenstringyes–
textstringyes–

No output schema declared.

No examples provided.

set_thread_title ~60

Name this session's conversation thread on the human's phone (e.g. the project or task you are working on). Shown as the thread title in the app.

NameTypeReqDescription
session_tokenstringyes–
titlestringyes–

No output schema declared.

No examples provided.

setup ~25

Return first-setup instructions and a clickable App Store download link when no number is available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

text ~112

Send a one-way text to the human's phone (push notification, no ring). On a local client, read `to` from `~/.aiphone/config.json` → `user_number`; this hosted server cannot read that file itself. If missing, returns setup_required with the App Store link. Pass a previous session_token to stay in the same thread.

NameTypeReqDescription
bodystringyes–
from_labelstring––
session_token–––
to–––

No output schema declared.

No examples provided.

wait_for_reply ~106

Wait for the human to send something back to this session — texts and voicemail transcripts arrive here. Long-polls up to wait_s (max 30s); returns {events, cursor}. Pass the returned cursor next time to only see new events. An empty events list just means nothing yet — poll again if you are still waiting.

NameTypeReqDescription
cursorinteger––
session_tokenstringyes–
wait_sinteger––

No output schema declared.

No examples provided.

Install

How do I install the Call Me MCP server?

Call Me is a hosted endpoint at https://callmemcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · callmemcp.com

# add to Claude Code
claude mcp add --transport http com-callmemcp-call-me 'https://callmemcp.com/mcp'
Common questions

What is the Call Me MCP server?

Call Me is an MCP server listed in the public MCP registry as com.callmemcp/call-me. Your AI rings your iPhone, speaks its question, and gets your spoken answer back as text. This page covers its hosted endpoint (https://callmemcp.com/mcp).

Is the Call Me MCP server safe to use?

Call Me scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Call Me MCP server expose?

Call Me exposes 8 tools: setup, call, poll_result, say, hang_up, and 3 more. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.

Does the Call Me MCP server require authentication?

No. We connected to Call Me without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Call Me MCP server still maintained?

Call Me is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.