Skip to content
External endpointresponds

Call Me

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

Endpoint URL
https://serdaroztetik.com/aiphone/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
708 ms
Response record
2 of 2 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.serdaroztetik/call-me

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
call-me
Capability keys
experimental, prompts, resources, tools
Tool names
call, poll_result, text, wait_for_reply, set_thread_title
Instructions excerpt

/call-me rings a real human's iPhone and returns what they said. - The human installs the /call-me iOS app (https://apps.apple.com/app/id6789575165) and reads their 10-digit /call-me number from it. Ask for the number once and remember it; it is not a real phone number. - `call` rings the phone and waits ~30 seconds. status "completed" carries the spoken answer as text. status "ringing" means nobody picked up yet: pass the returned call_id to `poll_result` (each poll waits up to ~25s; an unanswered ring resolves as "missed" within about a minute, so one or two polls settle it). - Every result carries a session_token. Reuse it in later `call`/`text` calls so they land in the same conversation thread on the phone, and pass it to `wait_for_reply` to receive what the human sends back (texts, voicemail transcripts) after a missed call or a text. - `text` sends a one-way message — use it for notifications that need no answer, or as the fallback when a call comes back "missed" or "declined

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 241ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 708ms