SMSBulk MCP Server
Related Servers
Alternatives to SMSBulk MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceGives AI agents real phone numbers to receive SMS and extract verification codes through tool calls.624 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.8 npmMIT
- AlicenseAqualityFmaintenanceEnables AI agents to create temporary email addresses, receive confirmation emails, and extract verification links, automating sign-up and email verification workflows without manual intervention.621 npm61MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and use temporary email and SMS inboxes, check messages, and wait for or extract OTPs and verification links during account registration. Combines both channels through a unified OTP tool while redacting sensitive tokens in audit logs.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to create disposable email inboxes, read messages, and wait for verification codes (OTPs) through MCP tools.437 npmMIT
- AlicenseAqualityCmaintenanceProvides disposable email inboxes for AI assistants to sign up, receive emails, and extract verification codes.745 npmMIT
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action: SMS services, countries, activations, wallet, and email domain. The email_ prefix clearly separates email tools from SMS tools, and within each group, operations like request, status, cancel, resend are unambiguous. No two tools appear to do the same thing.
The naming is largely consistent with a verb_noun pattern (e.g., list_services, get_balance, request_number), and the email_ prefix uniformly marks email tools. Minor exceptions include a few short verbs like 'complete' and 'cancel' without a noun, and 'request_resend' vs 'email_reorder' which use different phrasing, but the overall pattern is predictable and readable.
With 18 tools, the count is slightly above the typical 3-15 range, but it is justified by covering two distinct domains (SMS verification and email OTP). Each tool serves a clear purpose, and the count does not feel bloated or overwhelming. It straddles the boundary but remains reasonable.
The tool set covers the full lifecycle for both SMS and email verification: discovery, ordering, status, completion, cancellation, resend, plus wallet management and transaction history. There are no obvious dead ends or missing operations that would prevent an agent from executing common workflows.