call-me
Registry code: 2d4bec7b04a9a44a
/call-me rings a real human's iPhone and returns what they said.
- A Call Me number is all that is needed: no login, OAuth, or verification code. It is the 10-digit number from My Number in the app, not a regular telephone number.
- endpoint
- https://callmemcp.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is call-me live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is call-me free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does call-me have?
- 6 tools: poll_result, text, wait_for_reply, setup, set_thread_title, call.
- Is call-me safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
poll_result unknown 1h ago
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").
{ "type": "object", "title": "poll_resultArguments", "required": [ "call_id", "session_token" ], "properties": { "call_id": { "type": "integer", "title": "Call Id" }, "session_token": { "type": "string", "title": "Session Token" } } }arguments 18 linestext unknown never probed
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.
{ "type": "object", "title": "textArguments", "required": [ "body" ], "properties": { "to": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "To", "default": null }, "body": { "type": "string", "title": "Body" }, "from_label": { "type": "string", "title": "From Label", "default": "Someone's AI" }, "session_token": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Session Token", "default": null } } }arguments 42 lineswait_for_reply unknown 1h ago
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.
{ "type": "object", "title": "wait_for_replyArguments", "required": [ "session_token" ], "properties": { "cursor": { "type": "integer", "title": "Cursor", "default": 0 }, "wait_s": { "type": "integer", "title": "Wait S", "default": 25 }, "session_token": { "type": "string", "title": "Session Token" } } }arguments 23 linessetup unknown never probed
Return first-setup instructions and a clickable App Store download link when no number is available.
{ "type": "object", "title": "setupArguments", "properties": {} }arguments 5 linesset_thread_title unknown never probed
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.
{ "type": "object", "title": "set_thread_titleArguments", "required": [ "session_token", "title" ], "properties": { "title": { "type": "string", "title": "Title" }, "session_token": { "type": "string", "title": "Session Token" } } }arguments 18 linescall unknown never probed
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.
{ "type": "object", "title": "callArguments", "required": [ "question" ], "properties": { "to": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "To", "default": null }, "question": { "type": "string", "title": "Question" }, "from_label": { "type": "string", "title": "From Label", "default": "Someone's AI" }, "session_token": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "title": "Session Token", "default": null } } }arguments 42 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id2d4bec7b04a9a44a.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2d4bec7b04a9a44a/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2d4bec7b04a9a44a?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.