Call2Me
REMOTE · MCP.CALL2ME.APP
Place real phone calls, read transcripts, run a live interpreter and buy numbers.
Available components
Last scanned (22 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Communication
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 Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5511 tokens (~69/item across 79 items; 79 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "call2me_get_auto_charge" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 80 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −1
- New tool “call2me_campaign_action”, which the server declares destructive security
- New tool “call2me_create_notification_target”, which the server declares destructive security
- New tool “call2me_create_sip_trunk”, which the server declares destructive security
- New tool “call2me_delete_campaign”, which the server declares destructive security
- New tool “call2me_delete_knowledge_base”, which the server declares destructive security
- New tool “call2me_delete_notification_target”, which the server declares destructive security
- New tool “call2me_delete_sip_trunk”, which the server declares destructive security
- New tool “call2me_delete_widget”, which the server declares destructive security
- New tool “call2me_register_phone_number”, which the server declares destructive security
- New tool “call2me_send_chat_message”, which the server declares destructive security
- New tool “call2me_send_sms”, which the server declares destructive security
- New tool “call2me_set_webhook”, which the server declares destructive security
- Tool “call2me_update_agent” rewrote its description, which is the text the model reads security
- Schema quality: 2393 → 5511 ▼ functional
- Destructive annotations: 9 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "call2me_get_auto_charge" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. functional
- New tool “call2me_add_campaign_contacts” functional
- New tool “call2me_add_knowledge_base_sources” functional
- New tool “call2me_create_campaign” functional
- New tool “call2me_create_knowledge_base” functional
- New tool “call2me_create_topup_link” functional
- New tool “call2me_create_widget” functional
- New tool “call2me_duplicate_agent” functional
- New tool “call2me_get_agent_stats” functional
- New tool “call2me_get_auto_charge” functional
- New tool “call2me_get_call_recording” functional
- New tool “call2me_get_campaign” functional
- New tool “call2me_get_campaign_results” functional
- New tool “call2me_get_chat” functional
- New tool “call2me_get_knowledge_base” functional
- New tool “call2me_get_schedule” functional
- New tool “call2me_get_usage_analytics” functional
- New tool “call2me_get_webhook” functional
- New tool “call2me_get_widget” functional
- New tool “call2me_list_chats” functional
- New tool “call2me_list_knowledge_bases” functional
- New tool “call2me_list_notification_targets” functional
- New tool “call2me_list_sip_trunks” functional
- New tool “call2me_list_sms” functional
- New tool “call2me_list_transactions” functional
- New tool “call2me_list_voices” functional
- New tool “call2me_list_widgets” functional
- New tool “call2me_query_knowledge_base” functional
- New tool “call2me_start_chat” functional
- New tool “call2me_update_schedule” functional
- New tool “call2me_update_widget” functional
- “call2me_make_outbound_call” added an optional parameter “dynamic_variables” cosmetic
- “call2me_make_outbound_call” added an optional parameter “metadata” cosmetic
- “call2me_update_agent” added an optional parameter “knowledge_base_ids” cosmetic
- “call2me_update_agent” added an optional parameter “post_call_actions” cosmetic
- “call2me_update_agent” added an optional parameter “post_call_extraction” cosmetic
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 3 to 20. That category is still filling its 30-day observation window: 1 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.
- 4 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 79
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 16 Oct 2026 · Probed https://mcp.call2me.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.call2me.app | CN=YE1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5baa667ec5d2d1c7dabf945760809fd5e6f |
| SANs: mcp.call2me.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.call2me.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| call2me.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.call2me.app/.well-known/oauth-protected-resource", scope="call2me:read"
Bearer resource_metadata="https://mcp.call2me.app/.well-known/oauth-protected-resource", scope="call2me:read"Protected resource metadata
| Document | https://mcp.call2me.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.call2me.app |
| Authorisation server | https://auth.call2me.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.call2me.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.call2me.app/mcp | HTTPS enforced | 308 | https://mcp.call2me.app/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. 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 →
call2me_list_chats List text chats ~67
Lists text chat sessions with assistants. Pass agent_id to restrict to one assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Restrict to this assistant's chats. |
| limit | integer | – | How many records to return. |
| offset | integer | – | How many records to skip. |
No output schema declared.
No examples provided.
call2me_list_interpreter_calls List interpreter sessions ~50
Lists sessions run through an interpreter: duration, languages, status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many records to return. |
| offset | integer | – | How many records to skip. |
No output schema declared.
No examples provided.
call2me_list_interpreters List interpreters ~71
Lists the live interpreters on the account: name, language pair, bound number. An interpreter connects two people who each speak their own language, translating in real time.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many records to return. |
| offset | integer | – | How many records to skip. |
No output schema declared.
No examples provided.
call2me_list_knowledge_bases List knowledge bases ~52
Lists the knowledge bases (documents the assistants can search during calls). Pass agent_id to restrict to one assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Restrict to this assistant's knowledge bases. |
No output schema declared.
No examples provided.
call2me_list_notification_targets List notification targets ~52
Lists post-call notification targets (email, SMS, WhatsApp, webhook) of one assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The assistant id. Call call2me_list_agents first if unknown. |
No output schema declared.
No examples provided.
call2me_list_phone_numbers List phone numbers ~28
Lists the phone numbers on the account and which assistant each one is bound to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
call2me_list_schedules List scheduled calls ~48
Lists scheduled calls: when, which number, which assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many records to return. |
| offset | integer | – | How many records to skip. |
No output schema declared.
No examples provided.
call2me_list_sip_trunks List SIP trunks ~27
Lists the account's SIP trunks. Passwords are never returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
call2me_list_sms List SMS ~65
Lists sent and received SMS messages.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Only this direction. |
| limit | integer | – | How many records to return. |
| number | string | – | Only messages involving this phone number. |
| offset | integer | – | How many records to skip. |
No output schema declared.
No examples provided.
call2me_list_transactions List wallet transactions ~59
Lists wallet transactions (top-ups, call charges, number fees).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many records to return. |
| offset | integer | – | How many records to skip. |
| type | string | – | Filter by transaction type. |
No output schema declared.
No examples provided.
call2me_list_voices List voices ~73
Lists available text-to-speech voices; use a voice id when creating or updating an assistant. Filter by language, provider or gender.
| Name | Type | Req | Description |
|---|---|---|---|
| gender | string | – | Gender filter. |
| language | string | – | Language filter, e.g. tr-TR. |
| provider | string | – | Provider filter. |
No output schema declared.
No examples provided.
call2me_list_widgets List chat widgets ~42
Lists website chat/voice widgets. Pass agent_id to restrict to one assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Restrict to this assistant's widgets. |
No output schema declared.
No examples provided.
call2me_make_outbound_call Place a phone call ~190
Places a REAL phone call: the target number is dialled IMMEDIATELY and charged. Cannot be undone. Call this ONLY when the user explicitly asks for a call to be placed. agent_id and to_number are REQUIRED — never guess either one, never infer it from earlier conversation and never assign a default. Ask the user if anything is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Id of the assistant that will place the call. If unknown, call call2me_list_agents first. |
| dynamic_variables | object | – | Values for {{variables}} in the assistant prompt. |
| from_number | string | – | Caller id (one of the account's numbers). |
| metadata | object | – | Your own key/values stored on the call. |
| to_number | string | yes | Number to dial, E.164 (+905551234567). The user must supply it explicitly. |
No output schema declared.
No examples provided.
call2me_profile Account info ~45
Safe summary of the connected Call2Me account: email, name, account type. NEVER returns the API key. Use when the user asks which account they are connected to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
call2me_purchase_number Purchase number ~120
BUYS a phone number: the balance IS CHARGED and monthly rent starts. Cannot be undone. Call this ONLY when the user explicitly asks to buy and has picked the number themselves. NEVER guess the number — show options with call2me_search_numbers first and let the user choose. If the balance is insufficient, use call2me_checkout_number.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Assistant to bind the number to (optional). |
| phone_number | string | yes | The number the user CHOSE from the call2me_search_numbers result. |
No output schema declared.
No examples provided.
call2me_query_knowledge_base Search a knowledge base ~86
Runs a semantic search over one knowledge base and returns the best matching passages. Use to test what an assistant would retrieve.
| Name | Type | Req | Description |
|---|---|---|---|
| knowledge_base_id | string | yes | The knowledge base id. Call call2me_list_knowledge_bases first if unknown. |
| query | string | yes | The search question. |
| top_k | integer | – | How many passages to return. |
No output schema declared.
No examples provided.
call2me_register_phone_number Register own phone number ~114
Registers a phone number the user already owns together with the user's own SIP trunk (trunk_id is required). Does NOT buy a number. Never invent the number. Confirm the exact destination/value with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Assistant to bind (optional). |
| display_name | string | – | – |
| number | string | yes | Number in E.164, e.g. +905551234567. |
| trunk_id | string | yes | The user's own SIP trunk the number belongs to. |
No output schema declared.
No examples provided.
call2me_release_number Release number ~54
PERMANENTLY releases a phone number: it leaves the account, may be reassigned to someone else, and cannot be recovered. Incoming calls stop.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | The number to release. |
No output schema declared.
No examples provided.
call2me_search_numbers Search available numbers ~129
Lists purchasable phone numbers in a country. DOES NOT BUY — it only shows them. The country code is required; do not guess it, ask the user or call call2me_list_allowed_countries first.
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | string | – | Area code, if any. |
| country | string | yes | ISO country code, e.g. 'US', 'TR', 'GB'. |
| limit | integer | – | – |
| locality | string | – | City, if any. |
| phone_number_type | string | – | 'local' | 'toll-free' | 'mobile' |
No output schema declared.
No examples provided.
call2me_send_chat_message Send chat message ~81
Sends a message in a chat session and returns the assistant's reply. Each message is BILLED (about $0.01). Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The message text. |
| session_id | string | yes | The chat session id returned by call2me_start_chat or call2me_list_chats. |
No output schema declared.
No examples provided.
call2me_send_sms Send SMS ~84
Sends a REAL, charged SMS. Needs the sender number (one the account owns), the recipient and the text. Never invent numbers; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| from_number | string | yes | Sender, E.164, owned by the account. |
| text | string | yes | Message body. |
| to_number | string | yes | Recipient, E.164. |
No output schema declared.
No examples provided.
call2me_set_webhook Set webhook ~99
Sets or replaces the account webhook URL (events are POSTed there). The signing secret is never returned; supply your own webhook_secret if you need to know it, otherwise one is generated and hidden. All call events will be sent to this URL: Confirm the exact destination/value with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_secret | string | – | Optional signing secret (HMAC). |
| webhook_url | string | yes | HTTPS URL to receive events. |
No output schema declared.
No examples provided.
call2me_start_chat Start a text chat ~72
Starts a text chat session with an assistant and returns session_id. Starting is free; each message sent with call2me_send_chat_message is billed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The assistant id. Call call2me_list_agents first if unknown. |
| title | string | – | Optional session title. |
No output schema declared.
No examples provided.
call2me_start_interpreter_call Start interpreted call ~133
Places a REAL phone call: the target number is dialled IMMEDIATELY, both sides are connected through live translation, and the call is charged. Cannot be undone. Call this ONLY when the user explicitly asks. interpreter_id and target_number are REQUIRED — never guess either one.
| Name | Type | Req | Description |
|---|---|---|---|
| initiator_number | string | – | Number of the person starting the session. |
| interpreter_id | string | yes | Interpreter to use. If unknown, call call2me_list_interpreters first. |
| target_number | string | yes | Number to dial, E.164. The user must supply it explicitly. |
No output schema declared.
No examples provided.
call2me_unbind_number Unbind number ~42
Removes the number's assistant binding; calls to it are no longer answered. The number stays on the account.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | – |
No output schema declared.
No examples provided.
call2me_update_agent Update assistant ~157
Changes an existing assistant. Send only the fields the user named explicitly. Other API fields are accepted too, notably: knowledge_base_ids (attach knowledge bases), post_call_actions and post_call_extraction (post-call automation), voice_id, webhook_url, transfer_targets, begin_message, enable_recording.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The assistant to update. |
| knowledge_base_ids | array | – | Knowledge base ids the assistant searches (replaces the list). |
| language | string | – | – |
| name | string | – | – |
| post_call_actions | array | – | Actions to run after each call. |
| post_call_extraction | array | – | Data fields to extract from each call. |
| system_prompt | string | – | – |
No output schema declared.
No examples provided.
call2me_update_interpreter Update interpreter ~64
Changes an existing interpreter. Send only the fields the user named explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| interpreter_id | string | yes | – |
| name | string | – | – |
| source_language | string | – | – |
| target_language | string | – | – |
| transparency | string | – | – |
No output schema declared.
No examples provided.
call2me_update_schedule Update scheduled call ~103
Changes a scheduled call (time, timezone, contact name, recurrence). Send only the fields the user named.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_name | string | – | – |
| description | string | – | – |
| recurrence | string | – | – |
| recurrence_end_at | string | – | ISO 8601 date-time. |
| schedule_id | string | yes | The schedule id. |
| scheduled_at | string | – | New ISO 8601 date-time. |
| timezone | string | – | – |
No output schema declared.
No examples provided.
call2me_update_widget Update chat widget ~127
Changes widget settings. Send only the fields the user named.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Enable or disable the widget. |
| allowed_domains | array | – | – |
| auto_open | boolean | – | – |
| auto_open_delay_ms | integer | – | – |
| greeting_message | string | – | – |
| language | string | – | – |
| name | string | – | – |
| position | string | – | – |
| primary_color | string | – | – |
| voice_mode | string | – | – |
| widget_id | string | yes | The widget id. Call call2me_list_widgets first if unknown. |
No output schema declared.
No examples provided.
How do I install the Call2Me MCP server?
Call2Me is a hosted endpoint at https://mcp.call2me.app/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 · mcp.call2me.app
claude mcp add --transport http app-call2me-mcp 'https://mcp.call2me.app/mcp'
What is the Call2Me MCP server?
Call2Me is an MCP server listed in the public MCP registry as app.call2me/mcp. Place real phone calls, read transcripts, run a live interpreter and buy numbers. This page covers its hosted endpoint (https://mcp.call2me.app/mcp).
Is the Call2Me MCP server safe to use?
Call2Me scores 84 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 Call2Me MCP server expose?
Call2Me exposes 79 tools: call2me_profile, call2me_list_agents, call2me_get_agent, call2me_list_calls, call2me_get_call, and 74 more. Their descriptions and schemas cost roughly 5,423 tokens of context every time the server is loaded.
Does the Call2Me MCP server require authentication?
Yes. Call2Me asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Call2Me MCP server still maintained?
Call2Me is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.