Skip to content

Call Me MCP server

com.callmemcp/call-mecallmemcp.comstreamable-httpv1.0.1Scanned

Your AI rings your phone (iPhone or Android), speaks its question, gets your spoken answer as text.

9 tools: 6 can delete or cancel things, 1 change things and 2 only read.

Tools: 6 delete, 0 irreversible, 1 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Call Me MCP server can do

The Call Me MCP server is published by callmemcp.com, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (6 tools: call, play_audio, say, hang_up and 2 more) and create or change data (1 tool: poll_result). 2 tools only read.

6 tools bring in text other people can write (call, play_audio, say and 3 more); 1 tool can send data out of your system (text).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 22, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 6Claude Code: deny
  • callRing the human's phone (iPhone or Android), read `question` aloud word for word, and return what they say back as text.Reads text others writeNo findings

    Why it is in this group

    • The name "call" says "call": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Ring the human's phone (iPhone or Android), read `question` aloud word for word, and return what they say back as text. Waits up to ~30s. status "completed" carries their words in `transcript` (empty if they only listened). "ringing" (not picked up yet) or "in_call" (listening) means the call has not settled: pass call_id to poll_result until it does. An unanswered ring settles as "missed" within about a minute; "declined" means they refused it. Do not retry an unanswered call in a loop: send one `text` instead. The line stays open after their answer ("open": true): they hear a soft hold sound while you think, and a voice assistant tells them you are working on it. Reply with `say` (or `call` them again), finish with `hang_up`; after a short silence the line says goodbye and drops by itself. Anything they say while you work reaches you at once as a message (wait_for_reply) and again with their next answer as "said_while_waiting". The "language" and "language_name" fields report what the recognizer heard, as information only. `voice` picks who speaks (female first: bella, sarah, jessica, ...; male: roger, eric, brian, ...) and sticks for later calls. Reuse the returned session_token in later calls and texts so the phone keeps one thread. The `from` in the result is your own number: never call or text it. Missing `to` returns setup_required with download links.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Call the human
  • hang_upEnd a call you placed.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    End a call you placed. In an open conversation `goodbye` is spoken first; leave it empty to just hang up. A call that already ended reports its final status.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Hang up
  • play_audioBigger and longer audio goes here.Reads text others writeNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Bigger and longer audio goes here. Calls the human and plays a recording to them as a phone call: a podcast, a long narration you rendered, a voice memo, music. `source` is a link (YouTube, SoundCloud, a podcast page, or a direct .mp3/.m4a/.wav/.ogg/.flac/... link) or the audio_id of a file uploaded with `curl --data-binary @file.m4a "https://callmemcp.com/audio?to=<number>&filename=file.m4a"` (up to 300 MB / 3 hours, kept for a day). The voice says your `intro`, the title and the length, then asks if they want to listen now; on a yes the file plays as plain sound (no voice model) until it ends or they hang up. Returns once they answer the offer: status "playing" (they said yes), "completed" with listened:false (no, or nothing), or missed/declined. poll_result later reports listened_s and finished. Use `call` for text under ~2000 characters. `language` ("tr", "de") is the language of your intro; the offer and the call's own lines follow it.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Play long audio
  • sayIn a call whose result came back "open": true, speak `text` to the human and return what they answer, in the same shape as `call`.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    In a call whose result came back "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. `voice` switches who speaks from this line on (female first: bella, sarah, ...; male: roger, eric, ...); empty keeps it. Anything they say while you think reaches you at once as a message (wait_for_reply) and again with their answer as "said_while_waiting". End the call with `hang_up` once you are done.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Say the next line
  • set_thread_titleName this session's conversation thread on the human's phone (e.g.No findings

    Why it is in this group

    • The name "set_thread_title" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set thread title
  • textSend a one-way text to the human's phone (a push notification, no ring).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send a one-way text to the human's phone (a push notification, no ring). Use it for updates that need no answer, or as the fallback when a call comes back "missed" or "declined". delivered:false means it was saved to their history but no notification showed; `notice` says why. Their replies arrive through wait_for_reply. Missing `to` returns setup_required with the download links. Pass a previous session_token to stay in the same thread.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Text the human
Changes things 1Claude Code: ask
  • poll_resultCheck on a call that came back "ringing", "in_call" or "playing".No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check on a call that came back "ringing", "in_call" or "playing". Waits up to ~25s for it to settle, then returns the same shape as `call`: the final status and transcript once they answer, decline, or the ring times out ("missed", within about a minute). Still not settled: call it again. For play_audio calls it reports listened_s and finished. Rings nothing.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get call result
Only reads 2Show 2 read-only tools
  • setupReturn first-setup instructions and clickable App Store and Google Play download links, for when you do not have the human's Call Me number yet.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return first-setup instructions and clickable App Store and Google Play download links, for when you do not have the human's Call Me number yet. Show both links to the human as clickable links, then ask them to open My Number in the app and give you its 10 digits. Nothing is sent and nothing rings.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Set up Call Me
  • wait_for_replyWait for the human to send something back to this session — texts and voicemail transcripts arrive here.Reads text others writeNo findings

    Why it is in this group

    • The name "wait_for_reply" says "wait": a word for reading.

    What it can reach

    • untrusted-inputThe name "wait_for_reply" says "wait" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Wait for a text reply

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (6 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://callmemcp.com/mcp: tools/list returned 9 tools to an anonymous client, including call (destructive), play_audio (destructive), say (destructive), hang_up (destructive), text (destructive) and 2 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 6 to 7

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
    • Changed:callDeletes or cancelsdescriptioninputSchema
    • Changed:sayDeletes or cancelsdescription
  2. Tools1 added, 8 changed.+1 added~8 changedView diff
    • Added:play_audioDeletes or cancels
    • Changed:callDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:hang_upDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:poll_resultChanges thingsdescriptioninputSchemaannotations
    • Changed:sayDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:set_thread_titleDeletes or cancelsinputSchemaannotations
    • Changed:setupOnly readsdescriptionannotations
    • Changed:textDeletes or cancelsdescriptioninputSchemaannotations
    • Changed:wait_for_replyOnly readsinputSchemaannotations
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 7.View diff
    • Tools that change things, listed without credentials: 6 to 7

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http call-me https://callmemcp.com/mcp
claude mcp add --transport http call-me https://callmemcp.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__call-me__setup",
      "mcp__call-me__wait_for_reply"
    ],
    "ask": [
      "mcp__call-me__poll_result"
    ],
    "deny": [
      "mcp__call-me__call",
      "mcp__call-me__play_audio",
      "mcp__call-me__say",
      "mcp__call-me__hang_up",
      "mcp__call-me__text",
      "mcp__call-me__set_thread_title"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as call-me. Review it before you use it.

Capability tags behind 6 rules
  • mcp__call-me__call untrusted-input
  • mcp__call-me__play_audio untrusted-input
  • mcp__call-me__say untrusted-input
  • mcp__call-me__hang_up untrusted-input
  • mcp__call-me__text untrusted-input, outbound
  • mcp__call-me__wait_for_reply untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.callmemcp/call-me/verify?hash=3081d99e3debe97f0820b731eb22370cb564a11c4d79ae8864696a04536b1e6f" | jq -e '.changed == false'

Pinned hash 3081d99e3deb, from Nov 22, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.callmemcp/call-me/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.callmemcp/call-me
[![Anlyon Radar](https://radar.anlyon.com/badge/com.callmemcp/call-me.svg)](https://radar.anlyon.com/servers/com.callmemcp/call-me)

Source: MCP Registry · repository. Synced Nov 22, 2026, 02:17 UTC.

Call Me MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Call Me MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Call Me MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: call, play_audio, say, hang_up, text and set_thread_title.

Can the Call Me MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Call Me MCP server have?

9 tools: 6 destructive, 1 write, 2 read. call, play_audio, say, hang_up, text, set_thread_title, poll_result, setup and 1 more.

Does the Call Me MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Call Me MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): text.

Has the Call Me MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 22, 2026. Every change is on this page and in its Atom feed.