Call For Me
REMOTE · CALL-FOR-ME.FLY.DEV · SCANNED AUG 3
Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability33
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 555 tokens (~277/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · call-for-me.fly.dev
claude mcp add --transport http kimjin8-call-for-me 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 50
First indexed and scored.
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 3 Aug 2026 · Probed https://call-for-me.fly.dev/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 503153e73302e4a0c89ebb83c4a741aac04 |
| SANs: *.fly.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://call-for-me.fly.dev/mcp/ | Verified | 200 | |
| http (plaintext) | http://call-for-me.fly.dev/mcp/ | HTTPS enforced | 301 | https://call-for-me.fly.dev/mcp/ |
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.
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.