BounceLens Email Check
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| check_emailA | Check one email address for bad syntax, typos in the domain (gmial.com → gmail.com), disposable/throwaway domains, role addresses (info@, sales@) and domains that do not exist or have no mail server. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos. |
| check_emailsA | Check up to 500 email addresses at once (same checks as check_email, plus duplicates, counting Gmail dot and +tag variants as the same inbox). Returns a summary with counts and one result per address, in input order. status is "invalid" (will bounce: bad syntax, domain does not exist, no mail server), "risky" (disposable domain, likely typo such as gmial.com, no MX record) or "unconfirmed" (format and domain OK; the mailbox itself is not checked). did_you_mean holds the corrected address for typos. |
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
check_email and check_emails have clearly distinct purposes: one validates a single address, the other validates up to 500 in a batch. The descriptions explicitly differentiate them, and there is no functional overlap that would cause misselection.
Both tools follow a consistent verb_noun pattern (check_email, check_emails), with the plural form clearly indicating the batch operation. The naming is predictable and easy to infer.
Two tools is slightly below the typical 3-15 range, but the server's narrow purpose (email validation) is well-covered by a single and a bulk tool. Each tool earns its place, and adding more would likely be redundant.
The surface fully covers the stated domain: single and bulk email validation with detailed statuses, typo suggestions, and duplicate handling. There are no obvious missing operations for the core task, and the limitation on mailbox checking is clearly disclosed.