VoidMob MCP
OfficialRelated Servers
Alternatives to VoidMob MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceGives AI agents real phone numbers to receive SMS and extract verification codes through tool calls.621 npmMIT
- AlicenseAqualityCmaintenanceGives AI agents phone numbers, email, SMS, and voice calls as MCP tools, enabling them to provision numbers, capture 2FA codes, send messages, and make calls.15MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage phone numbers, send/receive SMS, and place voice calls through natural language, connecting to the phone network via the AgentPhone API.296 npm123MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to use a real Android phone with a SIM to retrieve phone numbers, receive SMS verification codes, and manage SMS messages.-

Telnyx MCP Serverofficial
FlicenseBqualityFmaintenanceEnables interaction with Telnyx's telephony, messaging, and AI assistant APIs to manage phone numbers, send messages, make calls, and create AI assistants. Includes webhook support for real-time event handling and comprehensive tools for voice, SMS, cloud storage, and embeddings.4625-- AlicenseBqualityCmaintenanceGive AI agents a real phone number and voice. Make calls, send email, manage contacts — 26 tools, 12 resources.431MIT
TDQS
Scored across 28 tools
Each tool targets a distinct resource and action, with clear ID conventions (ver_, ren_, ded_) and service-specific search tools. Overlapping actions like reuse_number vs re_rent_rental are differentiated by resource type. No two tools have ambiguous boundaries.
All tools follow a verb_noun pattern with consistent verbs for common actions: search_, purchase_, get_, list_, create_, delete_. Even multi-word actions like toggle_auto_renew and re_rent_rental maintain the pattern. No mixing of camelCase or inconsistent verb styles.
The 28 tools cover four distinct service domains (SMS, dedicated numbers, eSIMs, proxies) plus account and order management. While above the typical threshold, the count is justified by the breadth of the platform; no redundant tools exist. The proxy domain has 11 tools but each serves a unique management function.
Core lifecycle operations are covered for each service: search, purchase, status, and resource-specific management (reuse, topup, rotate, etc.). Minor gaps include no explicit cancel for dedicated numbers/eSIMs and no edit for proxy lists, but workarounds are documented (toggle_auto_renew, delete+recreate). Overall, agents can complete intended workflows without dead ends.