mcpbeat Sign in

aitocall MCP Server

by hodoolabs Your server? Claim it
answering

aitocall is answering right now. Last checked 14 min ago.

AI calls to South Korean numbers (+82), results and transcripts. 한국 번호 전용. Account & OAuth required.

Uptime history 50 days of history · worst day 95%
50 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
494 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check aitocall 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 14 min ago.

run in your terminal
claude mcp add aitocall --transport http https://www.aitocall.com/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://www.aitocall.com/api/mcp
~/.codex/config.toml
[mcp_servers.aitocall]
url = "https://www.aitocall.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "aitocall": {
      "url": "https://www.aitocall.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "aitocall": {
      "type": "http",
      "url": "https://www.aitocall.com/api/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://www.aitocall.com/api/mcp streamable-http sign-in 465 ms 14 min ago

Alternatives to aitocall

same job, measured the same way
Patch MCP
by patchmcp

AI phone calls from your verified number, with answers, transcripts and recordings.

52 tools answering
Sayw
by sayw

Manage Instagram automations, inbox, leads and Reel transcripts. Requires an invited Sayw account.

answering
Handset
by handset-hq

A business phone system for AI agents: send texts, place calls, read transcripts, buy numbers.

37 installs/wk local only
Call2Me
by call2me

Place real phone calls, read transcripts, run a live interpreter and buy numbers.

76 tools answering
Phone Bud
by phone-bud

AI voice agents that make real phone calls: one number or a short list, with transcripts and notes.

answering
FN2 AI
by fn2

Stock, earnings and macro research with scheduled agents. FN2 account and OAuth required.

answering
didlogic
by didlogic

Your didlogic account in AI assistants: numbers, SIP accounts, routing, SMS, calls and billing.

answering
DialMCP
by dialmcp

Let AI agents place real phone calls from your verified number, with transcripts and recordings.

56 installs/wk answering

aitocall — questions

Answers built from our own checks of this server.

Why is there no tool list for aitocall?
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 aitocall working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 494 ms. The bar chart above shows every period we have measured.
How do I connect aitocall?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 aitocall?
No API key is involved. aitocall 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 aitocall?
It answers our handshake in 494 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.