meisimusa-mcp
Related Servers
Alternatives to meisimusa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceHosted 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
- AlicenseAqualityBmaintenanceEnables 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.28364 npm126MIT

VoidMob MCPofficial
AlicenseAqualityBmaintenancePhone numbers, mobile IPs and eSIMs for your AI agent.28181 npm22MIT
Salvy MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up and manage a company's phone lines, usage, invoices, employees, cost centers, and assets, including actions such as blocking lines, changing plans, and porting numbers. Billable actions return a quote and require confirmation before being charged.MIT- 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
- AlicenseAqualityDmaintenanceGives AI agents real phone numbers to receive SMS and extract verification codes through tool calls.640 npmMIT
TDQS
Scored across 16 tools
Messaging tools (read_messages vs wait_for_message) and top-up tools (topup_lookup vs topup_start) are clearly delineated, but the purchase surface has three adjacent paths: search_us_numbers returns a plan_id 'for purchase', while purchase is described as buying an 'eSIM plan', and buy_numbers separately orders numbers from the prepaid wallet. Pricing is similarly split between get_number_pricing (own account) and get_ai_line_offer (public offer), and search_plans vs search_us_numbers sit close together. Descriptions cross-reference well enough to recover, but an agent can easily misselect on the buying flow.
Almost everything is snake_case verb_noun (get_order, list_my_numbers, send_message, read_messages), which is predictable and readable. The exceptions are the bare verb 'purchase' and the noun-first prefix family topup_lookup/topup_start, which break the verb_noun pattern slightly without causing confusion.
Sixteen tools is slightly heavy but the domain genuinely spans four areas: travel eSIM data, US number provisioning, top-ups, and SMS messaging plus account/pricing reads. Each tool maps to a real operation with few obvious redundancies, so the count is defensible rather than bloated.
The main lifecycle chains are covered end to end: search_plans -> get_quote -> purchase -> get_activation, get_number_pricing -> buy_numbers -> get_order -> list_my_numbers, and topup_lookup -> topup_start, plus a read/send/wait messaging trio. Gaps remain around lifecycle exits and recovery: there is no cancel-order or release-number operation, and no 'list my eSIM orders' tool, so an agent that loses an order_id has a dead end for retrieving the activation QR.