openphone

Tools

16 tools: 14 read-only, 0 change data, 2 high risk (delete, pay, send or run code).

1 tool can send messages; they are listed first.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 3,265 tokens of tool definitions and a 695 ms handshake.

• high riskopenphone_send_messagesends messagesSend 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.
• high riskopenphone_create_contactCreate 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.
• read-onlyopenphone_list_phone_numbersList 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.
• read-onlyopenphone_list_usersList workspace users (id, email, name, role). Use to find a userId for scoping other calls. OpenPhone REST: GET /users.
• read-onlyopenphone_list_contactsList 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.
• read-onlyopenphone_get_contactGet a single contact by its id, including default fields (name, company, role, emails, phone numbers) and custom fields. OpenPhone REST: GET /contacts/{id}.
• read-onlyopenphone_get_contact_custom_fieldsList 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.
• read-onlyopenphone_list_conversationsList 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.
• read-onlyopenphone_list_messagesList 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.
• read-onlyopenphone_get_messageGet a single message by its id (starts with 'AC'). OpenPhone REST: GET /messages/{id}.
• read-onlyopenphone_list_callsList 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.
• read-onlyopenphone_get_callGet a single call by its id (starts with 'AC') - direction, status, duration, participants and timestamps. OpenPhone REST: GET /calls/{id}.
• read-onlyopenphone_get_call_summaryGet 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}.
• read-onlyopenphone_get_call_transcriptGet 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}.
• read-onlyopenphone_get_call_recordingsGet the recordings for a call by its id - each with a URL, duration, start time and status. OpenPhone REST: GET /call-recordings/{callId}.
• read-onlyopenphone_list_webhooksList 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.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 695 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Marketing, email and messaging, ranked by days answering.

What agents looked for

This week agents asked 7Maps for marketing, email and messaging servers 1 time; this server was shown 0 times and picked 0 times.

Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/openphone.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/openphone.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=openphone.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/openphone.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/openphone.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=openphone.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.