Voidmob MCP Server

@voidmob/mcp npm v1.1.5 Source verified

Published by voidmobcom — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Mobile proxies, non-VoIP SMS verifications, dedicated numbers, and global eSIMs for AI agents and MCP clients.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([topup_esim, get_esim_qr]) co-exist with external-action tools ([purchase_dedicated_number, reuse_number]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [topup_esim, get_esim_qr] → sinks [purchase_dedicated_number, reuse_number]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow topup_esim → purchase_dedicated_number

Tools 28

Each tool and what it can reach — statically extracted from the published source.

  • get_esim_qringests untrusted input
  • purchase_dedicated_numbernetwork egress
  • reuse_numbernetwork egress
  • topup_esimingests untrusted input
  • cancel_rentalno sensitive capability
  • create_proxy_listno sensitive capability
  • delete_proxy_listno sensitive capability
  • get_accountno sensitive capability
  • get_dedicated_numberno sensitive capability
  • get_esim_statusno sensitive capability
Show 18 more tools ↓
  • get_geono sensitive capability
  • get_proxy_statusno sensitive capability
  • get_rentalno sensitive capability
  • list_ordersno sensitive capability
  • list_proxy_listsno sensitive capability
  • purchase_esimno sensitive capability
  • purchase_proxyno sensitive capability
  • re_rent_rentalno sensitive capability
  • regenerate_proxy_passwordno sensitive capability
  • renew_proxyno sensitive capability
  • rent_numberno sensitive capability
  • rotate_proxy_ipno sensitive capability
  • search_dedicated_countriesno sensitive capability
  • search_esim_plansno sensitive capability
  • search_proxiesno sensitive capability
  • search_sms_servicesno sensitive capability
  • toggle_auto_renewno sensitive capability
  • topup_proxyno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.5 latest A 97/100 1 1.13.0 2026-09-07
v1.1.3 A 97/100 1 1.13.0 2026-08-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/voidmob-mcp/badge.svg)](https://mcptrustchecker.com/registry/voidmob-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/voidmob-mcp"><img src="https://mcptrustchecker.com/registry/voidmob-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/voidmob-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @voidmob/mcp --online

Use the free API → How scoring works

More in Communication & Collaboration