# io.usefulapi/openphone (remote · openphone.usefulapi.io)

Send and read OpenPhone messages, calls, contacts and phone numbers.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `openphone.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-openphone/openphone.md), [page](https://verifymcp.io/servers/io-usefulapi-openphone/openphone)

## Channel facts

- Endpoint: `https://openphone.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-openphone 'https://openphone.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-openphone": {
      "url": "https://openphone.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-openphone": {
      "type": "http",
      "url": "https://openphone.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-openphone]
url = "https://openphone.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-openphone": {
      "type": "remote",
      "url": "https://openphone.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-openphone --url 'https://openphone.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-openphone:
    url: "https://openphone.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-openphone": {
      "Transport": "http",
      "Url": "https://openphone.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-openphone -t streamable-http -u 'https://openphone.usefulapi.io/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 78, +43)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13

### 2026-10-03 (score 35, −30)

- [security regression] Stability: 0.07 → unverified
- [security regression] 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.
- [functional regression] 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

### 2026-10-02 (score 65, −12)

- [security regression] Authorization: pass → unverified
- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 77, +4)

- [security improvement] HTTPS: unverified → pass
- [security] First check of Authorization: partial
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 73, +55)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (16)

### `openphone_list_phone_numbers` (~86 tokens)

List phone numbers

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.

Input parameters:

- `userId` (string): Scope results to a user's access (a user id starting with 'US'). From openphone_list_users.

### `openphone_list_users` (~80 tokens)

List users

List workspace users (id, email, name, role). Use to find a userId for scoping other calls. OpenPhone REST: GET /users.

Input parameters:

- `maxResults` (integer): Results per page, 1-50. Default 10.
- `pageToken` (string): Pagination token from a previous response's nextPageToken.

### `openphone_list_contacts` (~124 tokens)

List contacts

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.

Input parameters:

- `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.

### `openphone_get_contact` (~57 tokens)

Get a contact

Get a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts/{id}.

Input parameters:

- `id` (string, required): The contact id.

### `openphone_get_contact_custom_fields` (~48 tokens)

Get contact custom fields

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.

### `openphone_list_conversations` (~318 tokens)

List conversations

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.

Input parameters:

- `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, required): 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.

### `openphone_list_messages` (~246 tokens)

List messages

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.

Input parameters:

- `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, required): Participant phone numbers in E.164 format (e.g. '+15555555555'), 1-10 items (required).
- `phoneNumberId` (string, required): 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.

### `openphone_get_message` (~48 tokens)

Get a message

Get a single message by its id (starts with 'AC'). OpenPhone REST: GET /messages/{id}.

Input parameters:

- `id` (string, required): The message id (starts with 'AC').

### `openphone_send_message` (~192 tokens)

Send a text message

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.

Input parameters:

- `content` (string, required): The message body, 1-1600 characters (required).
- `from` (string, required): 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, required): 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.

### `openphone_list_calls` (~254 tokens)

List calls

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.

Input parameters:

- `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, required): A single participant phone number in E.164 format, e.g. '+15555555555' (required, exactly 1).
- `phoneNumberId` (string, required): 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.

### `openphone_get_call` (~59 tokens)

Get a call

Get a single call by its id (starts with 'AC') — direction, status, duration, participants and timestamps. OpenPhone REST: GET /calls/{id}.

Input parameters:

- `id` (string, required): The call id (starts with 'AC').

### `openphone_get_call_summary` (~68 tokens)

Get a call summary

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}.

Input parameters:

- `callId` (string, required): The call id (starts with 'AC').

### `openphone_get_call_transcript` (~64 tokens)

Get a call transcript

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}.

Input parameters:

- `id` (string, required): The call id (starts with 'AC').

### `openphone_get_call_recordings` (~63 tokens)

Get call recordings

Get the recordings for a call by its id — each with a URL, duration, start time and status. OpenPhone REST: GET /call-recordings/{callId}.

Input parameters:

- `callId` (string, required): The call id (starts with 'AC').

### `openphone_list_webhooks` (~51 tokens)

List webhooks

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.

### `openphone_create_contact` (~191 tokens)

Create a contact

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.

Input parameters:

- `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, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-openphone/openphone#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 35
- 2026-10-02: 65
- 2026-10-01: 77
- 2026-09-30: 73
- 2026-09-29: 18

## Common questions

### 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.

## Links

- Remote endpoint: https://openphone.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-openphone/openphone.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-openphone/openphone.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-openphone/openphone