F
licenseNot graded
qualityB
maintenanceEnables AI agents to verify email addresses in real-time, checking syntax, DNS, MX records, and SMTP handshake, returning verdicts and deliverability scores without sending actual emails.
-
mxprobe
by andrewchmr
Related Servers
Alternatives to mxprobe
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously create email accounts, verify domains, send and receive emails, and monitor delivery events without requiring human sign-up or payment.1-
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to verify a single email address in real time, clean an entire uploaded list file with per-address verdicts, and download the results as CSV with the addresses that are safe to send to. It runs on npm with zero dependencies and includes built-in credit reporting and spending limits so agents cannot overspend without approval.24 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to verify email addresses with catch-all detection, search existing contacts by company domain, and, when no API key is present, provision a human-approved subscription and retrieve the key after payment.4257 npmMIT
- MIT
TDQS
A4.1/5.0
Scored across 5 tools
Disambiguation4/5
The account tools (signup, balance, buy_credits) are clearly separable from the verification tools, and verify_batch is distinguished by its 500-address scope. The only soft overlap is verify_email versus a single-address verify_batch call, since both return identical schemas and differ mainly in the hosted-vs-free tier and batching.
Naming Consistency3/5
Two tools follow a clean verb_noun form (verify_email, verify_batch) and buy_credits fits, but signup is a bare verb and balance is a bare noun, so the pattern breaks in two of five cases. Mixed conventions, though each name remains readable in context.
Tool Count5/5
Five tools cleanly cover the two halves of the service: verification (single and batch) and account/credit lifecycle (signup, balance, buy_credits). Nothing feels padded or missing at the count level; each tool maps to a distinct user intent.
Completeness4/5
The core loop — get a key, check credits, buy more, verify addresses — is fully covered, including an out_of_credits path with checkout_url. Minor gaps: no way to inspect or rotate an existing key, no credit/usage history, and no status retrieval for long batch work beyond the synchronous response.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues