Call For Me
REMOTE · CALL-FOR-ME.FLY.DEV · SCANNED SEP 9
Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Call For Me MCP server?
Call For Me is a hosted endpoint at https://call-for-me.fly.dev/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 · call-for-me.fly.dev
claude mcp add --transport http kimjin8-call-for-me 'https://call-for-me.fly.dev/mcp/'
{
"mcpServers": {
"kimjin8-call-for-me": {
"url": "https://call-for-me.fly.dev/mcp/"
}
}
} {
"servers": {
"kimjin8-call-for-me": {
"type": "http",
"url": "https://call-for-me.fly.dev/mcp/"
}
}
} [mcp_servers.kimjin8-call-for-me] url = "https://call-for-me.fly.dev/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kimjin8-call-for-me": {
"type": "remote",
"url": "https://call-for-me.fly.dev/mcp/",
"enabled": true
}
}
} openclaw mcp add kimjin8-call-for-me --url 'https://call-for-me.fly.dev/mcp/' --transport streamable-http
mcp_servers:
kimjin8-call-for-me:
url: "https://call-for-me.fly.dev/mcp/" {
"McpServers": {
"kimjin8-call-for-me": {
"Transport": "http",
"Url": "https://call-for-me.fly.dev/mcp/"
}
}
} assistant mcp add kimjin8-call-for-me -t streamable-http -u 'https://call-for-me.fly.dev/mcp/'
{
"mcpServers": {
"kimjin8-call-for-me": {
"type": "http",
"url": "https://call-for-me.fly.dev/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 9 Sept 2026 · Probed https://call-for-me.fly.dev/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of call-for-me.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://call-for-me.fly.dev/mcp/ | Unreachable | ||
| http (plaintext) | http://call-for-me.fly.dev/mcp/ | HTTPS enforced |
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 →
get_call_status ~238
Poll the status of a call previously placed with place_call. Returns a CallOutcome with one of these statuses (in roughly likely order): queued/placing/ringing/connected — call still in progress, poll again in a few seconds completed — call finished cleanly, structured result available partial — call finished but some questions unanswered voicemail — recipient was voicemail; identified message left no_answer — recipient never picked up busy — recipient line was busy invalid_number — number is not in service rejected_ai — recipient declined to talk to A.I. (do not retry) needs_user_input — recipient needs info only the user can provide online_only — recipient said the task can only be done online timed_out — call exceeded max duration carrier_failure — telephony provider error (safe to retry later) api_error — internal failure (safe to retry) Always carries a free-form `exit_reason` string suitable for showing the user.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | The call_id returned by place_call. |
No output schema declared.
No examples provided.
place_call ~317
Place an outbound phone call to a US business or person. The A.I. assistant on the call will identify itself as A.I., follow your instructions, and return a structured outcome via get_call_status. USE THIS TOOL WHEN: the user wants to make a phone call, contact a business by phone, ask about hours/pricing/availability, book a reservation, gather info that's not online, follow up on a service request, or do any task that requires talking to a human on the phone. LIMITATIONS: - US phone numbers only (E.164 starting with +1). International is not yet supported. - English language only. - Cannot call emergency services (911, 988, etc.) — these will be rejected. - The A.I. will NOT commit to bookings/payments without user confirmation unless safety.must_confirm_with_user is explicitly set to false. - Default 5-minute call duration cap. Returns immediately with a call_id. Poll get_call_status(call_id) for the result.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| instructions | string | yes | The conversation goals/script the AI should follow. Agent owns this. We wrap it with mandatory safety layer (disclosure, hangup, voicemail, graceful-exit rubric). Be specific — what to ask, what tone… |
| output_schema | – | – | JSON Schema for the structured outcome you want extracted from the transcript. |
| safety | – | – | – |
| target | – | yes | – |
| user | – | yes | – |
No output schema declared.
No examples provided.
What is the Call For Me MCP server?
Call For Me is an MCP server listed in the public MCP registry as io.github.kimjin8/call-for-me. Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm. This page covers its hosted endpoint (https://call-for-me.fly.dev/mcp/).
Is the Call For Me MCP server safe to use?
Call For Me scores 0 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 For Me MCP server expose?
Call For Me exposes 2 tools: place_call, get_call_status. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Does the Call For Me MCP server require authentication?
Its publisher declares that Call For Me requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Call For Me MCP server still maintained?
Call For Me has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 2 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.