d1jiema-mcp
Related Servers
Alternatives to d1jiema-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to send WhatsApp, Telegram, SMS, VK/OK, and MAX messages, files, and bulk mailings, and to manage delivery status, webhooks, and sub-accounts.MIT- AlicenseAqualityBmaintenanceEnables AI agents to purchase phone numbers and retrieve one-time SMS/OTP verification codes via the CODASMS API, with support for 700+ services and 180+ countries including automatic refunds if no code arrives.711 npmMIT
- AlicenseNot gradedqualityAmaintenanceHosted MCP server for PacketExchange, the wholesale voice and SMS marketplace. Agents can search routes per mobile network with measured connect and caller ID results, compare prices, send SMS, place and follow calls, run SMS or voice verification codes and check the account balance. Route search works without an API key.MIT

SimRelay MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to manage SimRelay SIMs: list, lock, release, read SMS history, and stream incoming messages in real-time via WebSocket.111 npmISC- AlicenseAqualityCmaintenanceVirtual phone number platform for AI agents — rent numbers across 200+ countries, receive SMS, and manage the full activation lifecycle.6225 npm4MIT

VoidMob MCPofficial
AlicenseAqualityAmaintenancePhone numbers, mobile IPs and eSIMs for your AI agent.3084 npm28MIT
TDQS
Scored across 12 tools
The set includes four token/config tools (settings_read, settings_update, setup_local, login) whose boundaries are fuzzy—especially setup_local vs login, both of which open a local token flow. The generic d1jiema_request also overlaps with all specific read tools, though it is clearly marked as a catch-all.
All tools share the d1jiema_ prefix and snake_case, but the verb/noun pattern is inconsistent: some use verb_noun (get_phone, send_sms), some noun_verb (settings_read), and others are bare verbs or nouns (login, balance, history). The style is readable but not predictable.
12 tools is within a reasonable range for an SMS/phone service. However, four tools for token configuration alone feels slightly over-provisioned, keeping it from a perfect score.
Core lifecycle operations—phone acquisition, SMS retrieval, release, block, send, balance, history—are covered, and the generic request tool extends read coverage to any documented GET operation. Minor gaps remain (e.g., explicit phone status check or token deletion), but agents have workarounds.