SuperPhone MCP by usefulapi
REMOTE · SUPERPHONE.USEFULAPI.IO
MCP server for SuperPhone — contacts, conversations, tags and consent-based text messages.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
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 5 Nov 2026 · Probed https://superphone.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 superphone.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://superphone.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/superphone/ |
| http (plaintext) | http://superphone.usefulapi.io/mcp | Inconclusive | 302 | http://superphone.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 →
superphone_add_contact_tags Add tags to contact ~114
WRITE: apply tags to a contact, by name (a new name creates the tag) or by tag id. Tags can drive automations in Superphone. Returns the contact with its tags. GraphQL mutations `addContactTagsByNames` / `addContactTags`.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Superphone contact id. |
| tag_ids | array | – | Tag ids (from superphone_get_contact). Give tag_names or tag_ids, not both. |
| tag_names | array | – | Tag names. |
No output schema declared.
No examples provided.
superphone_add_contribution Record a purchase (custom contribution) ~150
WRITE: record a purchase or donation against a contact (name, amount, date). It adds to the contact's total spent and cannot be undone with this server. Returns the new contribution. GraphQL mutation `createCustomContribution`.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in the account's currency. |
| contact_id | string | yes | Superphone contact id. |
| created_at | string | – | When it happened, ISO 8601 (2026-10-01T12:00:00Z or 2026-10-01). Default: now. |
| name | string | yes | What it was for, e.g. 'Gift card' or 'October order #1042'. |
No output schema declared.
No examples provided.
superphone_create_contact Create contact ~288
WRITE: create a contact (first name required; add a mobile number or email so it can be reached). Creating a contact does not send it a message. Returns the new contact. GraphQL mutation `createContact`.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Archive the contact. |
| birthday | string | – | Birthday as text, e.g. 1990-05-17. |
| city | string | – | City. |
| company | string | – | Company. |
| country | string | – | Country. |
| string | – | Email address. | |
| first_name | string | yes | First name. |
| gender | string | – | Gender. |
| hidden | boolean | – | Hide the contact. |
| string | – | Instagram handle. | |
| job_title | string | – | Job title. |
| lastName | string | – | Last name. |
| string | – | LinkedIn profile. | |
| mobile | string | – | Mobile number, ideally E.164 (+12132679977); without a country code Superphone assumes the US. |
| nickname | string | – | Nickname. |
| notes | string | – | Free-text notes. |
| province | string | – | State or province. |
| string | – | Twitter handle. | |
| unsubscribed | boolean | – | Mark the contact as unsubscribed from messages. |
| vip | boolean | – | Mark as VIP. |
| zip_code | string | – | Postal code. |
No output schema declared.
No examples provided.
superphone_find_contact Find contact by mobile or email ~80
Find one contact by exact mobile number or email address (give at least one; E.164 such as +12132679977 is best). Returns the full contact or null when none matches. GraphQL query `contactByIdentifier`.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address. | |
| mobile | string | – | Mobile number, ideally E.164. |
No output schema declared.
No examples provided.
superphone_get_account Get account ~51
The Superphone account behind the API key: user id, email, name, the business phone numbers (number, default/active flags, short code) and notification preferences. GraphQL query `me`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superphone_get_contact Get contact ~63
One contact by id with every profile field, tags, custom contributions (recorded purchases) and its latest 10 conversations (ids to read with superphone_get_conversation). GraphQL query `contact`.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Superphone contact id. |
No output schema declared.
No examples provided.
superphone_get_conversation Get conversation messages ~132
One conversation with its most recent messages (default 20, newest last): body, from/to, direction (INCOMING_TEXT, OUTGOING_TEXT, SYSTEM, calls), delivery status, errors and media. To read older messages pass `before` = the previous reply's previous_cursor. GraphQL query `conversation`.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Cursor: pass the previous reply's previous_cursor to read older messages. |
| conversation_id | string | yes | Superphone conversation id. |
| message_count | integer | – | How many of the latest messages to return, 1-100 (default 20). |
No output schema declared.
No examples provided.
superphone_get_form Get sign-up form ~58
One sign-up form by id, or the account's default form when form_id is omitted. GraphQL queries `form` / `defaultForm`.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | – | Superphone form id; omit for the default form. |
No output schema declared.
No examples provided.
superphone_get_message Get message ~47
One message by id: body, from/to, direction, delivery status, error and media. GraphQL query `message`.
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | Superphone message id. |
No output schema declared.
No examples provided.
superphone_list_contacts List contacts ~123
List the SMS contacts (the subscriber list) with name, mobile, email, company, VIP/hidden/archived/unsubscribed/opted-out flags, total spent, creation date and tags (up to 20). Oldest first; page with next_cursor. `total` is the size of the whole list. GraphQL query `contacts`.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor: pass the previous reply's next_cursor to get the next page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
superphone_list_conversations List conversations ~112
List text conversations (the inbox): id, participant number, platform (TWILIO = SMS, FACEBOOK = Messenger), hidden/archived flags, creation date and the contact. Page with next_cursor. Read the messages of one with superphone_get_conversation. GraphQL query `conversations`.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor: pass the previous reply's next_cursor to get the next page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
superphone_list_forms List sign-up forms ~52
List the sign-up (opt-in) forms: id, public hashId, domain, titles, opt-in text flag, optional fields, redirect URL, default and enabled flags. GraphQL query `forms`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superphone_list_webhooks List webhooks ~58
List the configured webhooks: id, destination URL, active flag and subscribed events (CONTACT_ADDED, CONTACT_UPDATED, CONTACT_TAGS_CHANGED, MESSAGE_RECEIVED, MESSAGE_SENT, MESSAGE_STATUS_UPDATED). GraphQL query `webhooks`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
superphone_remove_contact_tags Remove tags from contact ~112
WRITE: remove tags from a contact, by name or by tag id. This can take the contact out of tag-driven segments and automations. Returns the contact with its remaining tags. GraphQL mutations `removeContactTagsByNames` / `removeContactTags`.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | Superphone contact id. |
| tag_ids | array | – | Tag ids (from superphone_get_contact). Give tag_names or tag_ids, not both. |
| tag_names | array | – | Tag names. |
No output schema declared.
No examples provided.
superphone_search_numbers Search available phone numbers ~79
Search phone numbers that could be bought for the account, optionally starting with some digits (for example an area code), with their price. Read-only: this tool never buys a number. GraphQL query `searchNumbers`.
| Name | Type | Req | Description |
|---|---|---|---|
| starts_with | string | – | Digits the number should start with, e.g. an area code like 415. |
No output schema declared.
No examples provided.
superphone_send_message Send a text message ~182
WRITE, IRREVERSIBLE: send a real text message to a customer from the account's number. It is delivered immediately, uses the account's messaging credits and cannot be recalled. Only send what the user explicitly asked for, to the number they named, and never to contacts who unsubscribed or opted out. Give exactly one of conversation_id (reply in an existing conversation) or mobile (a number, ideally E.164 like +12132679977; without a country code Superphone assumes the US). Returns the new message id. GraphQL mutation `sendMessage`.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The message text. |
| conversation_id | string | – | Reply in this conversation. |
| mobile | string | – | Recipient mobile number, E.164 recommended. |
| platform | string | – | TWILIO = SMS (default); FACEBOOK = Messenger conversation. |
No output schema declared.
No examples provided.
superphone_update_contact Update contact ~321
WRITE: change fields of an existing contact. Only the fields you pass change: the tool first reads the contact and sends the full record back with your changes (the API requires the first name on every update). Pass an empty string to clear a text field. Returns the updated contact. GraphQL mutation `updateContact`.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | Archive the contact. |
| birthday | string | – | Birthday as text, e.g. 1990-05-17. |
| city | string | – | City. |
| company | string | – | Company. |
| contact_id | string | yes | Superphone contact id. |
| country | string | – | Country. |
| string | – | Email address. | |
| first_name | string | – | New first name. |
| gender | string | – | Gender. |
| hidden | boolean | – | Hide the contact. |
| string | – | Instagram handle. | |
| job_title | string | – | Job title. |
| lastName | string | – | Last name. |
| string | – | LinkedIn profile. | |
| mobile | string | – | Mobile number, ideally E.164 (+12132679977); without a country code Superphone assumes the US. |
| nickname | string | – | Nickname. |
| notes | string | – | Free-text notes. |
| province | string | – | State or province. |
| string | – | Twitter handle. | |
| unsubscribed | boolean | – | Mark the contact as unsubscribed from messages. |
| vip | boolean | – | Mark as VIP. |
| zip_code | string | – | Postal code. |
No output schema declared.
No examples provided.
How do I install the SuperPhone MCP by usefulapi server?
SuperPhone MCP by usefulapi is a hosted endpoint at https://superphone.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 · superphone.usefulapi.io
claude mcp add --transport http io-usefulapi-superphone 'https://superphone.usefulapi.io/mcp'
What is the SuperPhone MCP by usefulapi server?
SuperPhone MCP by usefulapi is listed in the public MCP registry as io.usefulapi/superphone. MCP server for SuperPhone, contacts, conversations, tags and consent-based text messages. This page covers its hosted endpoint (https://superphone.usefulapi.io/mcp).
Is the SuperPhone MCP by usefulapi server safe to use?
SuperPhone 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 SuperPhone MCP by usefulapi server expose?
SuperPhone MCP by usefulapi exposes 17 tools: superphone_get_account, superphone_list_contacts, superphone_get_contact, superphone_find_contact, superphone_list_conversations, and 12 more. Their descriptions and schemas cost roughly 2,022 tokens of context every time the server is loaded.
Does the SuperPhone MCP by usefulapi server require authentication?
Its publisher declares no required credentials for SuperPhone 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 SuperPhone MCP by usefulapi server still maintained?
SuperPhone MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 SuperPhone MCP by usefulapi server?
VerifyMCP ran 4 checks on SuperPhone 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 SuperPhone 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.