PacketExchange
REMOTE · PACKETEXCHANGE.IO
SMS, voice calls, OTP verification, phone numbers and wholesale voice routes by Minutes Network.
Available components
Last scanned (19 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 22 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (wmmn_topup_x402). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7552 tokens (~228/item across 33 items; 33 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 Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
- Tool “wmmn_list_routes” rewrote its description, which is the text the model reads security
- Tool “wmmn_route_details” rewrote its description, which is the text the model reads security
- “wmmn_list_routes” added an optional parameter “origin_policy” cosmetic
- “wmmn_list_routes” reworded the description of “verification” cosmetic
- 16 Oct 26 0
- Tool “wmmn_list_routes” rewrote its description, which is the text the model reads security
- “wmmn_list_routes” added an optional parameter “verification” cosmetic
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- 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 22 Oct 2026 · Probed https://packetexchange.io/mcp/http
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=packetexchange.io | CN=YE2,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53a7e07b57a0c3dac00b6b352e75a4c4b85 |
| SANs: packetexchange.io, share.packetexchange.io, www.packetexchange.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of packetexchange.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| packetexchange.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://packetexchange.io/mcp/http | Verified | 200 | |
| http (plaintext) | http://packetexchange.io/mcp/http | HTTPS enforced | 301 | https://packetexchange.io/mcp/http |
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 →
wmmn_verify_start ~394
SPENDS MONEY. Starts a phone-number verification: generates a one-time code, stores only a keyed hash of it, and sends it by SMS or by a voice call that speaks it. Billed exactly like a normal SMS or API call: the route price, plus a platform fee of 2% of the carrier cost, capped at $0.001 per call or message (0.5%, same cap, when the traffic runs over your own SIP trunk; no fee when the carrier cost is 0). Returns a verification_id (never the code on a live key). The code expires after expiry_seconds (default 600), allows 5 check attempts and approves once. Rate limited: 5 starts per number per hour, 30 second resend cooldown, 20 per number range per hour, and 1000 per account per day; embargoed, high-risk premium and do-not-contact destinations are refused. A test key simulates the send and returns testCode so the flow can be completed. Requires the verify:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Name used in the message (max 30). Defaults to your company name |
| channel | string | yes | Deliver the code by SMS or by a voice call |
| expiry_seconds | integer | – | How long the code stays valid, 60-3600 seconds (default 600) |
| from | string | – | SMS sender ID, 1-30 characters (default: your brand, or "Verify"), or the caller ID in E.164 for the voice channel |
| language | string | – | Message language (default en). ar is SMS only |
| length | integer | – | Code length, 4-10 (default 6) |
| strategy | string | – | Smart Routing strategy (default balanced) |
| to | string | yes | Number to verify, E.164 (e.g. "+447700900123") |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | – | – | string: One of: sms, voice. |
| createdAt | – | – | string: ISO-8601 timestamp (UTC) |
| expiresAt | – | – | string: ISO-8601 timestamp (UTC) |
| maxAttempts | – | – | integer: Wrong guesses allowed before the verification is dead (5) |
| sendRef | – | – | string: The messageId (SMS) or callId (voice) that carried the code |
| sendStatus | – | – | string: SMS send-time status, or `initiated` for a voice call |
| simulated | – | – | boolean: Present and true for test keys: nothing was sent |
| status | – | – | string: One of: pending. |
| testCode | – | – | string: Test keys ONLY: the code, so a sandbox can complete the check. Never present on a live key |
| to | – | – | string |
| verificationId | – | – | string: Pass to POST /verify/check |
No examples provided.
How do I install the PacketExchange MCP server?
PacketExchange is a hosted endpoint at https://packetexchange.io/mcp/http, 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 · packetexchange.io
claude mcp add --transport http io-packetexchange-mcp 'https://packetexchange.io/mcp/http'
What is the PacketExchange MCP server?
PacketExchange is an MCP server listed in the public MCP registry as io.packetexchange/mcp. SMS, voice calls, OTP verification, phone numbers and wholesale voice routes by Minutes Network. This page covers its hosted endpoint (https://packetexchange.io/mcp/http).
Is the PacketExchange MCP server safe to use?
PacketExchange scores 67 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 PacketExchange MCP server expose?
PacketExchange exposes 33 tools: wmmn_list_routes, wmmn_route_details, wmmn_market_summary, wmmn_resolve_route, wmmn_purchase_route, and 28 more. Their descriptions and schemas cost roughly 7,552 tokens of context every time the server is loaded.
Does the PacketExchange MCP server require authentication?
No. We connected to PacketExchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PacketExchange MCP server still maintained?
PacketExchange is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.