MailProbe
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILPROBE_API_KEY | Yes | Your MailProbe API key, which starts with `mp_live_`, created under **Developer** in your account on mailprobe.dev. The local server starts and lists its tools without it, but a call explains how to set it. (The remote server at https://mailprobe.dev/mcp instead takes the key in the `Authorization: Bearer mp_live_...` header.) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_emailsA | Checks whether email addresses exist and can receive mail, in real time and without sending anything. Returns one result per address, in input order. Act on |
| get_creditsA | Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit. |
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 2 tools
The two tools target entirely different concerns: verifying addresses versus reading the account credit balance. There is no plausible way to confuse one with the other, and the descriptions make the boundary explicit ('Reading the balance uses no credit').
Both names follow a clean verb_noun snake_case pattern (verify_emails, get_credits) with the noun reflecting the resource being acted on. No mixing of conventions.
Two tools is thin for a standalone server, even a narrowly scoped one. The surface is arguably complete for a pure verification API, but a status/account or batch-history tool would round it out.
verify_emails is a fully-featured core operation (batch limits, per-status semantics, scoring, typo suggestions) and get_credits covers the account concern. Minor gaps remain, such as account details or a past-verification history/results lookup.