D7 Networks MCP by usefulapi
REMOTE · D7-NETWORKS.USEFULAPI.IO
Read D7 Networks balance, SMS pricing and delivery status; look up numbers; send one SMS.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 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 Usability83
- 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 894 tokens (~149/item across 6 items; 6 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 Management20
- Stability observed for 6 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 7 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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
- 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 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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 18 Oct 2026 · Probed https://d7-networks.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 d7-networks.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://d7-networks.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://d7-networks.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://d7-networks.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://d7-networks.usefulapi.io/mcp |
| Authorisation server | https://d7-networks.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://d7-networks.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/d7-networks/ |
| http (plaintext) | http://d7-networks.usefulapi.io/mcp | Inconclusive | 302 | http://d7-networks.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 →
d7_get_balance Get credit balance ~39
Read the D7 account's remaining credit balance (free; no credit is spent). D7 REST: GET /messages/v1/balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
d7_get_lookup_report Get number lookup report ~64
Read the stored result of an earlier number lookup by its request_id (free; no credit is spent). D7 REST: GET /hlr/v1/report/{request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id that d7_lookup_number returned. |
No output schema declared.
No examples provided.
d7_get_message_status Get SMS delivery status ~85
Read the delivery status of an SMS request: per recipient the status (delivered, sent, scheduled, un_delivered, not_reachable, spam_content, insufficient_credit), message parts and cost (free). D7 REST: GET /report/v1/message-log/{request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id that d7_send_sms returned. |
No output schema declared.
No examples provided.
d7_get_sms_pricing Get SMS pricing ~85
Read the account's price per SMS part, for one country or for all countries (free; no credit is spent). Use it to estimate the cost before d7_send_sms. D7 REST: GET /messages/v1/sms/pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| country_iso | string | – | Two-letter ISO country code, for example AE. Omit for all countries. |
No output schema declared.
No examples provided.
d7_lookup_number Look up a phone number (costs credits) ~124
WRITE (spends credits): look up ONE phone number's carrier data (country, network, MCC/MNC, ported, reachable, mobile or fixed). Each lookup is billed to the D7 account's credit balance (the cost is returned by d7_get_lookup_report as number_lookup_cost) and the account must have lookup routing enabled. It does not message the number. D7 REST: POST /hlr/v1/lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient | string | yes | The phone number, international format with the country code, for example +971501234567. |
No output schema declared.
No examples provided.
d7_send_sms Send an SMS (spends credits) ~287
WRITE (sends real text messages and spends credits): send ONE text message to 1-10 recipients (never a list or campaign). Each recipient costs the per-country price for every message part (about 160 GSM characters or 70 unicode characters per part; see d7_get_sms_pricing), taken from the D7 credit balance, and a sent SMS cannot be recalled. Free trial accounts may only use D7's demo sender id; other sender ids must be registered with D7. Send only messages the recipients expect, as unsolicited SMS violates D7's terms. Returns a request_id for d7_get_message_status. D7 REST: POST /messages/v1/send.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The message text, at most 640 characters. |
| data_coding | string | – | text = GSM 03.38 characters only, unicode = Arabic/Chinese/emoji etc., auto (default) = D7 decides from the content. |
| originator | string | yes | Sender id shown on the phone: up to 11 letters/digits (alphanumeric) or a registered number. Must be allowed for the account. |
| recipients | array | yes | 1 to 10 phone numbers, each in international format with the country code, for example +971501234567. |
| tag | string | – | Your own reference string, stored with the request. |
No output schema declared.
No examples provided.
How do I install the D7 Networks MCP by usefulapi server?
D7 Networks MCP by usefulapi is a hosted endpoint at https://d7-networks.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 · d7-networks.usefulapi.io
claude mcp add --transport http io-usefulapi-d7-networks 'https://d7-networks.usefulapi.io/mcp'
What is the D7 Networks MCP by usefulapi server?
D7 Networks MCP by usefulapi is listed in the public MCP registry as io.usefulapi/d7-networks. Read D7 Networks balance, SMS pricing and delivery status; look up numbers; send one SMS. This page covers its hosted endpoint (https://d7-networks.usefulapi.io/mcp).
Is the D7 Networks MCP by usefulapi server safe to use?
D7 Networks 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 D7 Networks MCP by usefulapi server expose?
D7 Networks MCP by usefulapi exposes 6 tools: d7_get_balance, d7_get_sms_pricing, d7_get_message_status, d7_get_lookup_report, d7_lookup_number, d7_send_sms. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Does the D7 Networks MCP by usefulapi server require authentication?
Yes. D7 Networks 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 D7 Networks MCP by usefulapi server still maintained?
D7 Networks MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.