mxprobe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MXPROBE_API_KEY | No | Optional hosted-tier API key from the signup tool or POST https://api.mxprobe.dev/v1/signup. Without it the verify tools run the free local DNS tier. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_emailA | Check whether an email address can receive mail before sending to it. Each result is { email, action, verdict, reason, checks }. action is send | hold | kill: send means go ahead, hold means send only with a fallback in hand (catch-all, forwarder, greylisted or refused probe), kill means never send (no mail server, or the mailbox does not exist). checks.smtp is skipped on the free DNS tier; the hosted tier probes the mailbox. Uses the hosted SMTP probe (1 credit) when an API key is configured and hosted is not false; otherwise the free local DNS tier. |
| verify_batchA | Check up to 500 addresses in one call. Each result is { email, action, verdict, reason, checks }. action is send | hold | kill: send means go ahead, hold means send only with a fallback in hand (catch-all, forwarder, greylisted or refused probe), kill means never send (no mail server, or the mailbox does not exist). checks.smtp is skipped on the free DNS tier; the hosted tier probes the mailbox. DNS kills cost nothing; with a key the survivors go to the hosted probe at 1 credit each. |
| signupA | Sign up with an email address. Returns an API key with 100 free checks and saves it locally for the other tools. The key is also mailed to the address. One key per address. |
| balanceA | How many hosted checks are left on the configured API key. |
| buy_creditsA | Get a Stripe Checkout link for more hosted checks: 9 USD per 10,000, one payment, credits never expire. Open the link to pay; credits land on the key when Stripe confirms. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clear, distinct purpose: signup creates an account, verify_email checks a single address, verify_batch checks up to 500 at once, balance queries credits, and buy_credits handles payment. The overlap between single and batch verification is well-delineated by their descriptions, leaving no ambiguity.
Most names follow a consistent verb_noun pattern (verify_email, verify_batch, buy_credits) and all use snake_case. 'signup' is a slight deviation as a compound verb/noun, and 'balance' is a plain noun, breaking the pattern. Still, the style is uniform and predictable.
Five tools is well-scoped for an email verification service, covering account creation, verification (single and batch), balance checking, and credit purchasing. Each tool serves a necessary function without bloat or redundancy.
The set covers the core lifecycle: account setup, verification, credit management, and purchasing. Minor gaps like account deletion or key revocation exist, but they are not essential to the primary use case and can be handled externally.