OpenPhone MCP by usefulapi
REMOTE · OPENPHONE.USEFULAPI.IO
Send and read OpenPhone messages, calls, contacts and phone numbers.
Available components
Last scanned (9 minutes ago)
Scores higher than 3% of remote servers
Reachable. Last reached 22 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_new_contact” functional
- New prompt “catch_up_on_a_text_thread_with_a_contact” functional
- New prompt “look_up_a_contact” functional
- New prompt “review_calls_and_their_next_steps” functional
- New prompt “send_a_text_message_to_customers” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 +1
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
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 22 Nov 2026 · Probed https://openphone.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of openphone.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | 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 |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openphone.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/openphone/ |
| http (plaintext) | http://openphone.usefulapi.io/mcp | Inconclusive | 302 | http://openphone.usefulapi.io/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 →
openphone_create_contact Create a contact ~191
Create a new contact in the workspace. WRITE ACTION — this adds a persistent contact record. Emails and phoneNumbers are passed as simple string arrays and stored under default field labels. OpenPhone REST: POST /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The contact's company. |
| emails | array | – | Email addresses for the contact. |
| externalId | string | – | A unique id from an external system (1-75 chars). |
| firstName | string | yes | The contact's first name (required). |
| lastName | string | – | The contact's last name. |
| phoneNumbers | array | – | Phone numbers for the contact (E.164 recommended). |
| role | string | – | The contact's role / job title. |
| source | string | – | How the contact was created; defaults to 'public-api'. |
| sourceUrl | string | – | A link to the contact in the source system. |
No output schema declared.
No examples provided.
openphone_get_call Get a call ~59
Get a single call by its id (starts with 'AC') — direction, status, duration, participants and timestamps. OpenPhone REST: GET /calls/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The call id (starts with 'AC'). |
No output schema declared.
No examples provided.
openphone_get_call_recordings Get call recordings ~63
Get the recordings for a call by its id — each with a URL, duration, start time and status. OpenPhone REST: GET /call-recordings/{callId}.
| Name | Type | Req | Description |
|---|---|---|---|
| callId | string | yes | The call id (starts with 'AC'). |
No output schema declared.
No examples provided.
openphone_get_call_summary Get a call summary ~68
Get the AI-generated summary and next steps for a call by its id. Availability depends on your plan and whether the call was summarized. OpenPhone REST: GET /call-summaries/{callId}.
| Name | Type | Req | Description |
|---|---|---|---|
| callId | string | yes | The call id (starts with 'AC'). |
No output schema declared.
No examples provided.
openphone_get_call_transcript Get a call transcript ~64
Get the transcription for a call by its id — dialogue segments with speaker, text and timestamps, plus overall status and duration. OpenPhone REST: GET /call-transcripts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The call id (starts with 'AC'). |
No output schema declared.
No examples provided.
openphone_get_contact Get a contact ~57
Get a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The contact id. |
No output schema declared.
No examples provided.
openphone_get_contact_custom_fields Get contact custom fields ~48
List the workspace's contact custom-field definitions (name, key, type). Use the returned keys when creating contacts with custom fields. OpenPhone REST: GET /contact-custom-fields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
openphone_get_message Get a message ~48
Get a single message by its id (starts with 'AC'). OpenPhone REST: GET /messages/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The message id (starts with 'AC'). |
No output schema declared.
No examples provided.
openphone_list_calls List calls ~254
List calls between one of your OpenPhone numbers and a participant, newest first, optionally filtered by user and created date range. Returns direction, status, duration and timestamps. OpenPhone REST: GET /calls.
| Name | Type | Req | Description |
|---|---|---|---|
| createdAfter | string | – | Only calls created after as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| createdBefore | string | – | Only calls created before as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| maxResults | integer | – | Results per page, 1-100. Default 10. |
| pageToken | string | – | Pagination token from a previous response's nextPageToken. |
| participants | array | yes | A single participant phone number in E.164 format, e.g. '+15555555555' (required, exactly 1). |
| phoneNumberId | string | yes | An OpenPhone phone-number id (starts with 'PN'). Get it from openphone_list_phone_numbers. |
| userId | string | – | Scope results to a user's access (a user id starting with 'US'). From openphone_list_users. |
No output schema declared.
No examples provided.
openphone_list_contacts List contacts ~124
List contacts in the workspace, optionally filtered by external ids or sources. Returns each contact's default fields (name, company, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| externalIds | array | – | Filter to contacts with these external ids (from an integrated system). |
| maxResults | integer | – | Results per page, 1-50. Default 10. |
| pageToken | string | – | Pagination token from a previous response's nextPageToken. |
| sources | array | – | Filter to contacts created by these sources. |
No output schema declared.
No examples provided.
openphone_list_conversations List conversations ~318
List conversations (threads), most-recent activity first, optionally filtered by phone number(s), user, and created/updated date ranges. Each conversation has participants, assignee, and last-activity metadata. OpenPhone REST: GET /conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| createdAfter | string | – | Only conversations created after as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| createdBefore | string | – | Only conversations created before as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| excludeInactive | boolean | – | Exclude inactive conversations when true. |
| maxResults | integer | yes | Results per page, 1-100 (required). |
| pageToken | string | – | Pagination token from a previous response's nextPageToken. |
| phoneNumbers | array | – | Filter to conversations on these OpenPhone numbers (E.164 or 'PN...' ids), 1-100 items. |
| updatedAfter | string | – | Only conversations updated after as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| updatedBefore | string | – | Only conversations updated before as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| userId | string | – | Scope results to a user's access (a user id starting with 'US'). From openphone_list_users. |
No output schema declared.
No examples provided.
openphone_list_messages List messages ~246
List messages in a conversation between one of your OpenPhone numbers and one or more participants. Returns text, direction, status and timestamps. OpenPhone REST: GET /messages.
| Name | Type | Req | Description |
|---|---|---|---|
| createdAfter | string | – | Only messages created after as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| createdBefore | string | – | Only messages created before as an ISO-8601 datetime, e.g. '2026-07-01T00:00:00Z'. |
| maxResults | integer | – | Results per page, 1-100. Default 10. |
| pageToken | string | – | Pagination token from a previous response's nextPageToken. |
| participants | array | yes | Participant phone numbers in E.164 format (e.g. '+15555555555'), 1-10 items (required). |
| phoneNumberId | string | yes | An OpenPhone phone-number id (starts with 'PN'). Get it from openphone_list_phone_numbers. |
| userId | string | – | Scope results to a user's access (a user id starting with 'US'). From openphone_list_users. |
No output schema declared.
No examples provided.
openphone_list_phone_numbers List phone numbers ~86
List the OpenPhone numbers in the workspace (id, number, name, formatted number, assigned users, restrictions). Usually the first call — most other tools need a phoneNumberId. OpenPhone REST: GET /phone-numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | – | Scope results to a user's access (a user id starting with 'US'). From openphone_list_users. |
No output schema declared.
No examples provided.
openphone_list_users List users ~80
List workspace users (id, email, name, role). Use to find a userId for scoping other calls. OpenPhone REST: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| maxResults | integer | – | Results per page, 1-50. Default 10. |
| pageToken | string | – | Pagination token from a previous response's nextPageToken. |
No output schema declared.
No examples provided.
openphone_list_webhooks List webhooks ~51
List all webhooks configured in the workspace (id, url, events, status). Read-only inventory — this tool does not create or delete webhooks. OpenPhone REST: GET /webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
openphone_send_message Send a text message ~192
Send an SMS/text message from one of your OpenPhone numbers to up to 10 recipients. WRITE ACTION — this actually sends a real text message (which may incur carrier cost and requires approved A2P 10DLC registration). OpenPhone REST: POST /messages.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The message body, 1-1600 characters (required). |
| from | string | yes | The sending OpenPhone number — a phone-number id ('PN...') or E.164 number, e.g. '+15555555555' (required). |
| setInboxStatus | string | – | Set to 'done' to mark the conversation complete after sending. |
| to | array | yes | Recipients in E.164 format (or contact ids), 1-10 items (required). |
| userId | string | – | The sending user id ('US...'); defaults to the phone number's owner. |
No output schema declared.
No examples provided.
How do I install the OpenPhone MCP by usefulapi server?
OpenPhone MCP by usefulapi is a hosted endpoint at https://openphone.usefulapi.io/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 · openphone.usefulapi.io
claude mcp add --transport http io-usefulapi-openphone 'https://openphone.usefulapi.io/mcp'
What is the OpenPhone MCP by usefulapi server?
OpenPhone MCP by usefulapi is listed in the public MCP registry as io.usefulapi/openphone. Send and read OpenPhone messages, calls, contacts and phone numbers. This page covers its hosted endpoint (https://openphone.usefulapi.io/mcp).
Is the OpenPhone MCP by usefulapi server safe to use?
OpenPhone MCP by usefulapi scores 18 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 OpenPhone MCP by usefulapi server expose?
OpenPhone MCP by usefulapi exposes 16 tools: openphone_list_phone_numbers, openphone_list_users, openphone_list_contacts, openphone_get_contact, openphone_get_contact_custom_fields, and 11 more. Their descriptions and schemas cost roughly 1,949 tokens of context every time the server is loaded.
Does the OpenPhone MCP by usefulapi server require authentication?
Its publisher declares no required credentials for OpenPhone MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the OpenPhone MCP by usefulapi server still maintained?
OpenPhone MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the OpenPhone MCP by usefulapi server?
VerifyMCP ran 4 checks on OpenPhone MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about OpenPhone MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.