Messente MCP by usefulapi
REMOTE · MESSENTE.USEFULAPI.IO
Read Messente balance, prices, delivery status and statistics; send SMS to up to 10 numbers.
Available components
Last scanned (2 hours ago)
Scores higher than 47% 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 Usability86
- 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 1047 tokens (~116/item across 9 items; 9 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 10 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 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- 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 62
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://messente.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 messente.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://messente.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://messente.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://messente.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://messente.usefulapi.io/mcp |
| Authorisation server | https://messente.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://messente.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/messente/ |
| http (plaintext) | http://messente.usefulapi.io/mcp | Inconclusive | 302 | http://messente.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 →
messente_add_to_blacklist Add a number to the blacklist ~80
WRITE: add one phone number to the account's blacklist, so Messente will no longer send messages to it. Adding a number already listed is harmless. Messente: POST /phonebook/blacklist.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_number | string | yes | Phone number to blacklist, E.164 format, e.g. +37251000000. |
No output schema declared.
No examples provided.
messente_check_blacklist Check if a number is blacklisted ~70
Check whether one phone number is on the account's blacklist. Messente: GET /phonebook/blacklist/{phone} (found = blacklisted, 404 = not).
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number in E.164 format, e.g. +37251000000. |
No output schema declared.
No examples provided.
messente_get_balance Get account balance ~41
Get the Messente account's remaining SMS credit balance (in EUR). Messente legacy API: GET /get_balance (api2.messente.com).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
messente_get_delivery_status Get delivery status of a message ~105
Get the delivery report of a sent message by its omnimessage id (returned by messente_send_sms): per-message status (DELIVRD, UNDELIV, FAILED, ...), error and the price charged. Messente asks not to poll this for every message at scale. Messente: GET /omnimessage/{omnimessage_id}/status.
| Name | Type | Req | Description |
|---|---|---|---|
| omnimessage_id | string | yes | The omnimessage_id returned when the message was sent. |
No output schema declared.
No examples provided.
messente_get_prices Get SMS prices for a country ~72
Get this account's price per SMS part for one country, per mobile network (use it to estimate what messente_send_sms will cost). Messente legacy API: GET /prices.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. EE or GB. |
No output schema declared.
No examples provided.
messente_get_statistics Get message statistics ~86
Get total messages and total price per country for a date range, optionally for some message types. Messente: POST /statistics/reports (a read-only report).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | End date, YYYY-MM-DD. |
| message_types | array | – | Limit the report to these message types. |
| start_date | string | yes | Start date, YYYY-MM-DD. |
No output schema declared.
No examples provided.
messente_list_blacklist List blacklisted numbers ~85
List the phone numbers on the account's blacklist (numbers Messente will not send to). Returns the total count and at most `limit` numbers. Messente: GET /phonebook/blacklist.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum numbers to return (default 500). |
| offset | integer | – | Skip this many numbers (to page through a long list). |
No output schema declared.
No examples provided.
messente_lookup_numbers Look up phone numbers (HLR) ~117
Number lookup (HLR): is each number valid, ported, roaming, and which network it is on. COSTS CREDITS: Messente charges per number looked up (EUR 0.002 per number in its docs) and the Number Lookup service must be enabled on the account (a fixed monthly fee applies per Messente's docs). Up to 10 numbers per call. Messente: POST /hlr/sync.
| Name | Type | Req | Description |
|---|---|---|---|
| numbers | array | yes | Phone numbers in E.164 format (1-10). |
No output schema declared.
No examples provided.
messente_send_sms Send an SMS ~178
WRITE: SENDS REAL SMS TEXT MESSAGES to real people and SPENDS the account's Messente credit (each recipient is charged per SMS part, longer texts use several parts; use messente_get_prices to estimate). SMS only, at most 10 recipients per call, one message per recipient, never to a list. Send only to people who asked to receive it (Messente forbids unsolicited messages). Not undoable. Messente: POST /omnimessage with channel sms, once per recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| sender | string | – | Sender name (alphanumeric, max 11 chars) or number; must be a sender verified on the account. Omit to use the account default. |
| text | string | yes | The message text. |
| to | array | yes | Recipient phone numbers in E.164 format (1-10). |
No output schema declared.
No examples provided.
How do I install the Messente MCP by usefulapi server?
Messente MCP by usefulapi is a hosted endpoint at https://messente.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 · messente.usefulapi.io
claude mcp add --transport http io-usefulapi-messente 'https://messente.usefulapi.io/mcp'
What is the Messente MCP by usefulapi server?
Messente MCP by usefulapi is listed in the public MCP registry as io.usefulapi/messente. Read Messente balance, prices, delivery status and statistics; send SMS to up to 10 numbers. This page covers its hosted endpoint (https://messente.usefulapi.io/mcp).
Is the Messente MCP by usefulapi server safe to use?
Messente MCP by usefulapi scores 65 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 Messente MCP by usefulapi server expose?
Messente MCP by usefulapi exposes 9 tools: messente_get_balance, messente_get_prices, messente_get_delivery_status, messente_list_blacklist, messente_check_blacklist, and 4 more. Their descriptions and schemas cost roughly 834 tokens of context every time the server is loaded.
Does the Messente MCP by usefulapi server require authentication?
Yes. Messente 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 Messente MCP by usefulapi server still maintained?
Messente 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.