Skip to content

OpenPhone MCP by usefulapi

io.usefulapi/openphoneusefulapi.iostreamable-httpv1.40.4Scanned

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

16 tools: 2 can delete or cancel things and 14 only read.

Tools: 2 delete, 0 irreversible, 0 write, 14 read.
  • Reads private data · 7
  • Reads text others write · 7
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the OpenPhone MCP by usefulapi can do

The OpenPhone MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (2 tools: openphone_send_message and openphone_create_contact). 14 tools only read.

7 tools read private data (openphone_list_users, openphone_list_contacts, openphone_get_contact and 4 more); 7 tools bring in text other people can write (openphone_list_users, openphone_get_contact, openphone_list_conversations and 4 more); 1 tool can send data out of your system (openphone_send_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Deletes or cancels 2Claude Code: deny
  • openphone_create_contactCreate a new contact in the workspace.No findings

    Why it is in this group

    • The name "openphone_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • openphone_send_messageSend an SMS/text message from one of your OpenPhone numbers to up to 10 recipients.Can send data outNo findings

    Why it is in this group

    • The name "openphone_send_message" says "send": a word for sending, and what is sent cannot be taken back.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "openphone_send_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Send a text message
    • destructiveHint: true
Only reads 14Show 14 read-only tools
  • openphone_get_callGet a single call by its id (starts with 'AC') — direction, status, duration, participants and timestamps.No findings

    Why it is in this group

    • The name "openphone_get_call" says "get": a word for reading.
    Description, as the server wrote it
    Get a single call by its id (starts with 'AC') — direction, status, duration, participants and timestamps. OpenPhone REST: GET /calls/{id}.

    Annotations the server declares

    • title: Get a call
    • readOnlyHint: true
  • openphone_get_call_recordingsGet the recordings for a call by its id — each with a URL, duration, start time and status.Reads text others writeNo findings

    Why it is in this group

    • The name "openphone_get_call_recordings" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get the recordings for a call by its id — each with a URL, duration, start time and status. OpenPhone REST: GET /call-recordings/{callId}.

    Annotations the server declares

    • title: Get call recordings
    • readOnlyHint: true
  • openphone_get_call_summaryGet the AI-generated summary and next steps for a call by its id.No findings

    Why it is in this group

    • The name "openphone_get_call_summary" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get a call summary
    • readOnlyHint: true
  • openphone_get_call_transcriptGet the transcription for a call by its id — dialogue segments with speaker, text and timestamps, plus overall status and duration.No findings

    Why it is in this group

    • The name "openphone_get_call_transcript" says "get": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get a call transcript
    • readOnlyHint: true
  • openphone_get_contactGet a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openphone_get_contact" says "get": a word for reading.

    What it can reach

    • private-dataThe name "openphone_get_contact" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Get a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts/{id}.

    Annotations the server declares

    • title: Get a contact
    • readOnlyHint: true
  • openphone_get_contact_custom_fieldsList the workspace's contact custom-field definitions (name, key, type).Reads private dataNo findings

    Why it is in this group

    • The name "openphone_get_contact_custom_fields" says "get": a word for reading.

    What it can reach

    • private-dataThe name "openphone_get_contact_custom_fields" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get contact custom fields
    • readOnlyHint: true
  • openphone_get_messageGet a single message by its id (starts with 'AC').Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openphone_get_message" says "get": a word for reading.

    What it can reach

    • private-dataThe name "openphone_get_message" says "get" and "message": it reads messages.
    • private-dataThe description's first sentence says "get" and "message": it reads messages.
    • untrusted-inputThe name "openphone_get_message" says "get" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Get a single message by its id (starts with 'AC'). OpenPhone REST: GET /messages/{id}.

    Annotations the server declares

    • title: Get a message
    • readOnlyHint: true
  • openphone_list_callsList calls between one of your OpenPhone numbers and a participant, newest first, optionally filtered by user and created date range.No findings

    Why it is in this group

    • The name "openphone_list_calls" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List calls
    • readOnlyHint: true
  • openphone_list_contactsList contacts in the workspace, optionally filtered by external ids or sources.Reads private dataNo findings

    Why it is in this group

    • The name "openphone_list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "openphone_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List contacts
    • readOnlyHint: true
  • openphone_list_conversationsList conversations (threads), most-recent activity first, optionally filtered by phone number(s), user, and created/updated date ranges.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openphone_list_conversations" says "list": a word for reading.

    What it can reach

    • private-dataThe name "openphone_list_conversations" says "list" and "conversation": it reads messages.
    • private-dataThe description's first sentence says "list" and "conversation": it reads messages.
    • untrusted-inputThe name "openphone_list_conversations" says "list" and "conversation": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List conversations
    • readOnlyHint: true
  • openphone_list_messagesList messages in a conversation between one of your OpenPhone numbers and one or more participants.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openphone_list_messages" says "list": a word for reading.

    What it can reach

    • private-dataThe name "openphone_list_messages" says "list" and "message": it reads messages.
    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe name "openphone_list_messages" says "list" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List messages
    • readOnlyHint: true
  • openphone_list_phone_numbersList the OpenPhone numbers in the workspace (id, number, name, formatted number, assigned users, restrictions).No findings

    Why it is in this group

    • The name "openphone_list_phone_numbers" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List phone numbers
    • readOnlyHint: true
  • openphone_list_usersList workspace users (id, email, name, role).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "openphone_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List workspace users (id, email, name, role). Use to find a userId for scoping other calls. OpenPhone REST: GET /users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true
  • openphone_list_webhooksList all webhooks configured in the workspace (id, url, events, status).Reads text others writeNo findings

    Why it is in this group

    • The name "openphone_list_webhooks" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List webhooks
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

49 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__openphone__openphone_send_message"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://openphone.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://openphone.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://openphone.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://openphone.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__openphone__openphone_list_phone_numbers",
      "mcp__openphone__openphone_list_users",
      "mcp__openphone__openphone_list_contacts",
      "mcp__openphone__openphone_get_contact",
      "mcp__openphone__openphone_get_contact_custom_fields",
      "mcp__openphone__openphone_list_conversations",
      "mcp__openphone__openphone_list_messages",
      "mcp__openphone__openphone_get_message",
      "mcp__openphone__openphone_list_calls",
      "mcp__openphone__openphone_get_call",
      "mcp__openphone__openphone_get_call_summary",
      "mcp__openphone__openphone_get_call_transcript",
      "mcp__openphone__openphone_get_call_recordings",
      "mcp__openphone__openphone_list_webhooks"
    ],
    "ask": [],
    "deny": [
      "mcp__openphone__openphone_send_message",
      "mcp__openphone__openphone_create_contact"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as openphone. Review it before you use it.

Capability tags behind 10 rules
  • mcp__openphone__openphone_list_users private-data, untrusted-input
  • mcp__openphone__openphone_list_contacts private-data
  • mcp__openphone__openphone_get_contact private-data, untrusted-input
  • mcp__openphone__openphone_get_contact_custom_fields private-data
  • mcp__openphone__openphone_list_conversations private-data, untrusted-input
  • mcp__openphone__openphone_list_messages private-data, untrusted-input
  • mcp__openphone__openphone_get_message private-data, untrusted-input
  • mcp__openphone__openphone_send_message outbound
  • mcp__openphone__openphone_get_call_recordings untrusted-input
  • mcp__openphone__openphone_list_webhooks untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/openphone/verify?hash=21fe585eccffda75859d1ac25e7726b72d0549a84deb0cea194e78cdd0cd323f" | jq -e '.changed == false'

Pinned hash 21fe585eccff, from Oct 25, 2026, 23:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/openphone/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/openphone
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/openphone.svg)](https://radar.anlyon.com/servers/io.usefulapi/openphone)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

OpenPhone MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OpenPhone MCP by usefulapi safe?

No scan can promise that. What its definitions show: 16 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OpenPhone MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: openphone_send_message and openphone_create_contact.

Can the OpenPhone MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OpenPhone MCP by usefulapi have?

16 tools: 2 destructive, 14 read. openphone_send_message, openphone_create_contact, openphone_list_phone_numbers, openphone_list_users, openphone_list_contacts, openphone_get_contact, openphone_get_contact_custom_fields, openphone_list_conversations and 8 more.

Does the OpenPhone MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the OpenPhone MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): openphone_send_message.

Has the OpenPhone MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.