Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Widely

REMOTE · MCP.WIDELY-MOBILE.COM

Connect your communications to your AI.

+3 this week 65 Trust /100

Last scanned (2 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Communication

Recent critical change

Authorization (22 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 6775 tokens (~92/item across 73 items; 73 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management39
  • Stability check failed: schema churn in the 14 days we've observed: 4 tool removals, 1 breaking changes, 0 auth/transport breaks, 18 additions. See how to fix → Fail
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 74 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 24 Oct 26 +30
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “check_call_rate” was removed ▼ security
    • Tool “delete_account_steps” was removed ▼ security
    • Tool “get_account_balance” was removed ▼ security
    • Tool “list_pbx” was removed ▼ security
    • Injection markers: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (update_forwarding) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “cancel_call_task”, which the server declares destructive security
    • New tool “set_call_handling”, which the server declares destructive security
    • Tool “account_closure_options” rewrote its description, which is the text the model reads security
    • Tool “ask_support” rewrote its description, which is the text the model reads security
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • Tool “quote_call” rewrote its description, which is the text the model reads security
    • Tool “request_speak” rewrote its description, which is the text the model reads security
    • Schema quality: 73 → 92 ▼ functional
    • “request_speak” added a required parameter “brief”, so existing callers break ▼ functional
    • “request_speak” dropped the required parameter “task” ▼ functional
    • Tool coverage: 29% → 43% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Destructive annotations: All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • New tool “accept_errands_terms” functional
    • New tool “create_call_task” functional
    • New tool “describe_errand_template” functional
    • New tool “get_call_task” functional
    • New tool “list_call_tasks” functional
    • New tool “quote_call_task” functional
    • New tool “set_assistant_name” functional
    • “request_speak” reworded the description of “destination” cosmetic
    • “request_speak” reworded the description of “identity_id” cosmetic
    • “request_speak” dropped the optional parameter “connect_user” cosmetic
    • “request_speak” made “destination” optional cosmetic
    • Tool “account_closure_options” changed its title: Stop charges or close an account → Account closure options cosmetic
    • Tool “quote_call” changed its title: Quote a call → Call rate cosmetic
  • 23 Oct 26 −29
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.40 → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 22 Oct 26 0
    • Authorization: unverified → fail ▼ critical
  • 21 Oct 26 +1
    • Authorization: fail → unverified ▼ security
  • 20 Oct 26 0
    • Authorization: unverified → fail ▼ critical
  • 19 Oct 26 +28
    • Injection markers: unverified → pass ▲ security
    • Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (update_forwarding) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.30 ▲ functional
  • 18 Oct 26 −27
    • Stability: 0.23 → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Oct 26 +27
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “delete_receptionist_hours”, which the server declares destructive security
    • New tool “delete_receptionist_knowledge”, which the server declares destructive security
    • New tool “delete_receptionist_location”, which the server declares destructive security
    • New tool “update_whatsapp_ai”, which the server declares destructive security
    • New tool “upsert_receptionist_knowledge”, which the server declares destructive security
    • New tool “upsert_receptionist_location”, which the server declares destructive security
    • New tool “upsert_receptionist_profile”, which the server declares destructive security
    • Tool “upsert_hours” rewrote its description, which is the text the model reads security
    • Schema quality: 4265 → 4998 ▼ functional
    • Tool coverage: 39% → 29% ▼ functional
    • Destructive annotations: 67% → 83% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • New tool “get_receptionist_facts” functional
    • “upsert_hours” added an optional parameter “ivr_config_id” cosmetic
    • “upsert_receptionist” added an optional parameter “default_language” cosmetic
    • “upsert_receptionist” added an optional parameter “description” cosmetic
Diagnostics

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 24 Oct 2026 · Probed https://mcp.widely-mobile.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.widely-mobile.com CN=YE2,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA384 61c42ffb57acec6a74b3bde4560a8a457f3
SANs: mcp.widely-mobile.com
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.widely-mobile.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
widely-mobile.com. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.widely-mobile.com/mcp Verified 200
http (plaintext) http://mcp.widely-mobile.com/mcp HTTPS enforced 301 https://mcp.widely-mobile.com/mcp
MCP tools · 73 exposed · ~6,587 tokens

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 →

Tool Tokens
request_transcript ~35

Asks Widely to transcribe a recording that has no text yet. Pro plan.

NameTypeReqDescription
call_idstringyes–

No output schema declared.

No examples provided.

run_esim_connection_check ~80

Asks this user's Widely app to check the eSIM and returns a request_id. A result of no_install_yet means the profile may have been installed from a QR and the Widely app is not on that phone. An APN is not included.

NameTypeReqDescription
device_idstring––
sim_idstring––

No output schema declared.

No examples provided.

search_calls ~169

Finds phone calls on this Widely seat by date range, direction, contact name, or number. Returns one row per phone call, with direction, duration, outcome, the identity used, and whether a transcript or recording exists.

NameTypeReqDescription
contactstring–Saved contact name to match.
daysinteger–Look back this many days (default 30).
directionstring––
limitinteger–Max rows to return.
linestring––
missed_onlyboolean––
numberstring–Phone number or trailing digits.
querystring–Words from a stored transcript. Pro.
sincestring–ISO 8601 start (inclusive).
untilstring–ISO 8601 end (exclusive).

No output schema declared.

No examples provided.

search_contacts ~37

Finds saved contacts on this seat by name. Returns names and phone numbers.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

search_help ~38

Returns public product facts and in-app menu names for a question. No sign-in. Does not return a price.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

search_messages ~88

Searches this user's Widely, SMS, and WhatsApp threads by keyword and date. Returns message text with sender and thread. Support and assistant threads are excluded.

NameTypeReqDescription
conversation_idstring––
daysinteger–Look back this many days (default 30).
limitinteger–Max rows to return.
querystring–Keyword to match in message text.

No output schema declared.

No examples provided.

search_numbers ~108

Find Widely phone numbers available for a country and an optional city, with the monthly price. Use this when a local number is needed. No sign-in. This does not purchase a number.

NameTypeReqDescription
citystring––
countrystringyesTwo-letter country code or country name.
currencystring–GBP, EUR, USD, or ILS. Omit for the rate-checker default.
number_typestring–local, mobile, or toll-free.

No output schema declared.

No examples provided.

send_message ~74

Sends an SMS or a Widely message to a phone number or saved contact. Pro plan. Sending happens on this request.

NameTypeReqDescription
identity_idstring–Optional identity id when the grant is limited to specific numbers.
textstring–Message text.
tostring–Phone number or saved contact name.

No output schema declared.

No examples provided.

set_assistant_name ~51

Sets the name the assistant uses on AI calls (Widely AI assistant settings → Assistant's name). Calls are refused until a name is set or passed in the brief.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

set_call_handling ~103

Sets what happens when this seat declines a call, does not answer it, or is busy: voicemail, busy, decline, end, or ai_receptionist. ai_receptionist rings the seat first, then hands the call to the AI receptionist or phone menu in menu_id (Business).

NameTypeReqDescription
actionstringyes–
menu_idstring–AI receptionist or phone menu id, for ai_receptionist.
whenstringyes–

No output schema declared.

No examples provided.

set_number_routing ~123

Points a number at ring_me, personal_assistant, a receptionist, a menu, a queue, voicemail, busy, or decline. An optional closed target uses the opening hours. A shared line, receptionist, menu, or queue needs Business.

NameTypeReqDescription
auto_recordboolean––
closed_targetstring––
closed_target_idstring––
numberstring––
number_idstring––
targetstring––
target_idstring––
time_group_idstring––

No output schema declared.

No examples provided.

submit_product_note ~117

Sends Widely a note about a missing capability, a complaint, or a use case to build. No account is required. reply_url, when it is https, receives each desk reply. Returns conversation_id. Passing that id on a later request adds to the same thread.

NameTypeReqDescription
conversation_idstring–Continue this thread instead of opening a new one.
kindstring––
reply_urlstring–Public https URL that receives each reply.
textstringyes–
titlestring––

No output schema declared.

No examples provided.

subscribe_events ~86

Sets the https URL that receives call.started, call.ended, and speak.completed for this seat. events chooses which of those names to receive. Omitting events receives all three. An empty webhook_url stops delivery.

NameTypeReqDescription
eventsarray–Names to receive. Omit or empty for all of them.
webhook_urlstring–Public https URL, or empty to stop.

No output schema declared.

No examples provided.

uk_divert_number ~26

Returns the UK shared Always-forward destination and the dial code. No sign-in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_forwarding ~60

Points a verified number at a business number on this seat, or stops forwarding when forward_to is empty. Pro plan.

NameTypeReqDescription
forward_tostring–A business number on this seat, or empty to stop.
identity_idstring––

No output schema declared.

No examples provided.

update_whatsapp_ai ~80

Pause, resume, choose who can see the WhatsApp chats, or set the webhook that answers first. Setting a webhook returns the signing secret once.

NameTypeReqDescription
clear_webhookboolean––
did_idstringyes–
monitor_idsarray––
pauseboolean––
webhook_urlstring––

No output schema declared.

No examples provided.

upsert_hours ~104

Creates or edits a timezone-aware opening-hours schedule and optionally attaches it to an AI receptionist. Informational receptionist hours do not change DID routing. day is 0 for Monday through 6 for Sunday; start and end are HH:MM. Date-bounded is_closed windows are exceptions.

NameTypeReqDescription
idstring––
ivr_config_idstring––
namestring––
timezonestring––
windowsarray––

No output schema declared.

No examples provided.

upsert_menu ~103

Creates or edits a press-1 menu. The account owner needs Business. A key can ring a person, ring a queue, or send the caller to an AI receptionist. A direct person target and every queue agent also need Business.

NameTypeReqDescription
enabledboolean––
greetingstring––
idstring––
keysarray–Press-1 choices. Sending keys replaces the menu's choices.
namestring––

No output schema declared.

No examples provided.

upsert_queue ~90

Creates or edits a queue. The account owner and every queue member need Business. A queue rings only members who are signed in and available.

NameTypeReqDescription
auto_recordboolean––
idstring––
max_wait_secondsinteger––
member_idsarray––
namestring––
overflowstring––
strategystring––

No output schema declared.

No examples provided.

upsert_receptionist ~158

Creates or edits an AI receptionist. The account owner needs Business. It speaks with the caller and does not transfer the live conversation to a person.

NameTypeReqDescription
default_languagestring––
descriptionstring––
enabledboolean––
greetingstring––
idstring––
knowledgestring––
languagesarray––
namestring––
voicestring–Voice the receptionist speaks with: one of alloy, ash, ballad, cedar, coral, echo, marin, sage, shimmer, verse (default marin), or a custom voice id made in the Widely app, which starts with voice_.…

No output schema declared.

No examples provided.

upsert_receptionist_knowledge ~83

Adds or revises a knowledge entry for one receptionist. The next WhatsApp reply and the next phone call both use it.

NameTypeReqDescription
bodystringyes–
categorystring––
dataobject––
idstring––
ivr_config_idstringyes–
titlestringyes–

No output schema declared.

No examples provided.

upsert_receptionist_location ~167

Stores a business address plus directions, parking, public transport, accessibility, location contacts, coordinates, and timezone.

NameTypeReqDescription
accessibilitystring––
addressstring––
citystring––
country_codestring––
directionsstring––
emailstring––
idstring––
is_primaryboolean––
ivr_config_idstringyes–
latitudenumber––
longitudenumber––
namestring––
parkingstring––
phonestring––
postal_codestring––
public_transportstring––
regionstring––
timezonestring––

No output schema declared.

No examples provided.

upsert_receptionist_profile ~111

Creates or edits the business identity, IANA timezone, contact details, and human-escalation instructions used on phone and WhatsApp.

NameTypeReqDescription
business_namestring––
emailstring––
escalation_instructionsstring––
is_activeboolean––
ivr_config_idstringyes–
phonestring––
timezonestring–IANA timezone such as Asia/Jerusalem.
websitestring––

No output schema declared.

No examples provided.

Install

How do I install the Widely MCP server?

Widely is a hosted endpoint at https://mcp.widely-mobile.com/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.widely-mobile.com

# add to Claude Code
claude mcp add --transport http com-widely-mobile-widely 'https://mcp.widely-mobile.com/mcp'
Common questions

What is the Widely MCP server?

Widely is an MCP server listed in the public MCP registry as com.widely-mobile/widely. Connect your communications to your AI. This page covers its hosted endpoint (https://mcp.widely-mobile.com/mcp).

Is the Widely MCP server safe to use?

Widely scores 65 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 Widely MCP server expose?

Widely exposes 73 tools: list_identities, search_calls, get_call, get_transcript, get_recording, and 68 more. Their descriptions and schemas cost roughly 6,587 tokens of context every time the server is loaded.

Does the Widely MCP server require authentication?

No. We connected to Widely without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Widely MCP server still maintained?

Widely is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.