FireText MCP by usefulapi
REMOTE · FIRETEXT.USEFULAPI.IO
Read FireText credit, messages and reports; send an SMS to up to 10 numbers; manage opt-outs.
Available components
Last scanned (7 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 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 Security78
- 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 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
- 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 & 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2117 tokens (~162/item across 13 items; 13 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
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 14 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
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 17 Oct 2026 · Probed https://firetext.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 firetext.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://firetext.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://firetext.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://firetext.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://firetext.usefulapi.io/mcp |
| Authorisation server | https://firetext.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://firetext.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/firetext/ |
| http (plaintext) | http://firetext.usefulapi.io/mcp | Inconclusive | 302 | http://firetext.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 →
firetext_get_click_report Get click report ~145
Link clicks for one sent message (mobile, names, clicked, userAgent). Only for messages that used FireText's Trackable SMS feature (otherwise the vendor answers URL error). FireText: /clickreport.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | FireText message ID (see firetext_list_sent_messages). |
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10000 or 25000 (the vendor's only choices for this report). Large; omit for the vendor default. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_get_contact Get contact ~105
Stored details of one contact by mobile number (firstname, lastname, mobile, customField1-3). FireText: /contactinfo.
| Name | Type | Req | Description |
|---|---|---|---|
| mobile | string | yes | Mobile number: UK 07700900123 / 447700900123, or international without + and leading zeros (e.g. 33612345678). |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_get_credit Get SMS credit ~62
Number of SMS credits (messages) remaining on the FireText account or a sub-account. FireText: /credit.
| Name | Type | Req | Description |
|---|---|---|---|
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_get_delivery_report Get delivery report ~179
Per-recipient delivery status of one sent message (mobile, names, messageSent, messageUpdate, status: Delivered / Declined / Buffered / Pending with Network / Rejected / Unconfirmed). Give the FireText message id OR the custom reference used when sending. FireText: /deliveryreport.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | FireText message ID (see firetext_list_sent_messages). |
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10000 or 25000 (the vendor's only choices for this report). Large; omit for the vendor default. |
| reference | string | – | The custom reference set when sending (alternative to message). |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_get_sent_summary Get sent summary ~87
Totals for a date range: number of campaigns, recipients and credits used. FireText: /sentreport.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start date YYYY-MM-DD. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| to | string | yes | End date YYYY-MM-DD. |
No output schema declared.
No examples provided.
firetext_list_keywords List keywords ~93
SMS keywords on the account (keywordID, number, keyword, reference). FireText: /keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10, 25 (default), 50 or 100. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_list_received_messages List received messages ~167
Inbound SMS received on the account's FireText numbers/keywords (messageID, sentTo, keyword, receivedFrom, receivedOn, message). Dates YYYY-MM-DD; from="last" returns only what is new since the last call. FireText: /receivedmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date YYYY-MM-DD, or "last" for only what is new since the last access. |
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10, 25 (default), 50 or 100. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| to | string | – | End date YYYY-MM-DD. |
No output schema declared.
No examples provided.
firetext_list_scheduled_messages List scheduled messages ~107
Messages queued for later sending (messageID, queuedOn, scheduledFor, recipientCount, sourceAddress, sendTo, message). FireText: /scheduledmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10, 25 (default), 50 or 100. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
firetext_list_sent_messages List sent messages ~161
Messages (campaigns) sent from the account: messageID, sentOn, sentTo (group), recipientCount, message. The messageID is what the delivery and click reports need. Dates YYYY-MM-DD. FireText: /sentmessages.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date YYYY-MM-DD, or "last" for only what is new since the last access. |
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10, 25 (default), 50 or 100. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| to | string | – | End date YYYY-MM-DD. |
No output schema declared.
No examples provided.
firetext_list_unsubscribed List unsubscribed contacts ~164
Contacts that opted out (names, mobile, custom fields, addedOn, unsubscribedOn, reason). Optional date range and group API id. FireText: /unsubscribed.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start date YYYY-MM-DD, or "last" for only what is new since the last access. |
| group | string | – | Group API ID to restrict to one group. |
| page | integer | – | Page number (1-based). |
| pp | – | – | Results per page: 10, 25 (default), 50 or 100. |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| to | string | – | End date YYYY-MM-DD. |
No output schema declared.
No examples provided.
firetext_send_sms Send SMS ~270
WRITE, SPENDS MONEY: sends a REAL SMS to real phones and uses the account's SMS credits (one credit per 160 GSM characters per recipient; long and unicode messages cost more). Cannot be undone. At most 10 recipients per call; no groups, templates, scheduling or repeats. Only call after the user confirmed the exact text, sender and numbers. FireText: /sendsms.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Sender ID shown on the handset: 3-11 characters, letters and digits only (a company name or a reply number). |
| message | string | yes | Message text (UTF-8), up to 612 characters (160 per single GSM SMS, 153 per part when longer; unicode 70/66). |
| reference | string | – | Optional custom reference stored against the message (usable in firetext_get_delivery_report). |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| to | array | yes | Recipient mobile numbers (1-10): UK 07... / 447..., or international without + and leading zeros. |
| unicode | – | – | 0 = GSM characters only (default), 1 = always unicode, 2 = auto-detect from the text. |
No output schema declared.
No examples provided.
firetext_subscribe_contact Add or update contact ~220
WRITE: adds a contact (by mobile number) to the FireText account, optionally into a group, or with update=true refreshes the names/custom fields of an existing contact. Does not send any SMS. A contact that opted out cannot be re-added this way (they must rejoin by SMS). FireText: /subscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| custom1 | string | – | – |
| custom2 | string | – | – |
| custom3 | string | – | – |
| firstname | string | – | – |
| group | string | – | Group API ID to add the contact to. |
| lastname | string | – | – |
| mobile | string | yes | Mobile number: UK 07700900123 / 447700900123, or international without + and leading zeros (e.g. 33612345678). |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
| update | boolean | – | true = overwrite firstname, lastname and custom1-3 of an existing contact. |
No output schema declared.
No examples provided.
firetext_unsubscribe_contact Unsubscribe contact ~144
WRITE: opts a contact out of the FireText account (all groups by default), so it no longer receives group messages. The contact can only rejoin by SMS. Does not send any SMS. FireText: /unsubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Group API ID, only if the account unsubscribes per group. |
| mobile | string | yes | Mobile number: UK 07700900123 / 447700900123, or international without + and leading zeros (e.g. 33612345678). |
| subaccount | string | – | Sub-account ID (only when the account has the sub-account module). Omit for the main account. |
No output schema declared.
No examples provided.
How do I install the FireText MCP by usefulapi server?
FireText MCP by usefulapi is a hosted endpoint at https://firetext.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 · firetext.usefulapi.io
claude mcp add --transport http io-usefulapi-firetext 'https://firetext.usefulapi.io/mcp'
What is the FireText MCP by usefulapi server?
FireText MCP by usefulapi is listed in the public MCP registry as io.usefulapi/firetext. Read FireText credit, messages and reports; send an SMS to up to 10 numbers; manage opt-outs. This page covers its hosted endpoint (https://firetext.usefulapi.io/mcp).
Is the FireText MCP by usefulapi server safe to use?
FireText MCP by usefulapi scores 64 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 FireText MCP by usefulapi server expose?
FireText MCP by usefulapi exposes 13 tools: firetext_get_credit, firetext_list_received_messages, firetext_list_sent_messages, firetext_get_sent_summary, firetext_list_scheduled_messages, and 8 more. Their descriptions and schemas cost roughly 1,904 tokens of context every time the server is loaded.
Does the FireText MCP by usefulapi server require authentication?
Yes. FireText MCP by usefulapi 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 FireText MCP by usefulapi server still maintained?
FireText MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.