io.usefulapi/openphone
REMOTE · OPENPHONE.USEFULAPI.IO · SCANNED OCT 4
Send and read OpenPhone messages, calls, contacts and phone numbers.
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 → Why this is hard to score →
Endpoint Security89
- 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1949 tokens (~121/item across 16 items; 16 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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
How do I install the io.usefulapi/openphone MCP server?
io.usefulapi/openphone 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'
{
"mcpServers": {
"io-usefulapi-openphone": {
"url": "https://openphone.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-openphone": {
"type": "http",
"url": "https://openphone.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-openphone] url = "https://openphone.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-openphone": {
"type": "remote",
"url": "https://openphone.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-openphone --url 'https://openphone.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-openphone:
url: "https://openphone.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-openphone": {
"Transport": "http",
"Url": "https://openphone.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-openphone -t streamable-http -u 'https://openphone.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-openphone": {
"type": "http",
"url": "https://openphone.usefulapi.io/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.
- 4 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.13 ▲ functional
- 3 Oct 26 −30
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. 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
- 2 Oct 26 −12
- Authorization: pass → unverified ▼ security
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- First check of Authorization: partial security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +55
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
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 4 Oct 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| 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. | present | 57355 | 8 | Verified |
| usefulapi.io. | 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 realm="OAuth", resource_metadata="https://openphone.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://openphone.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://openphone.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://openphone.usefulapi.io/mcp |
| Authorisation server | https://openphone.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://openphone.usefulapi.io/mcp | HTTPS enforced | 301 | https://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.
What is the io.usefulapi/openphone MCP server?
io.usefulapi/openphone is an MCP server 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 io.usefulapi/openphone MCP server safe to use?
io.usefulapi/openphone scores 78 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 io.usefulapi/openphone MCP server expose?
io.usefulapi/openphone 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 io.usefulapi/openphone MCP server require authentication?
Yes. io.usefulapi/openphone 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 io.usefulapi/openphone MCP server still maintained?
io.usefulapi/openphone is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.