inboxvalid-mcp
Server 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 |
|---|---|
| verify_emailA | Verifies an email address's deliverability plausibility: syntax, disposable-domain, and MX-record checks. Returns a structured status ('valid' | 'invalid' | 'risky') with a machine-readable reason code - never throws on a bad address, always returns a result. |
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 1 tool
Only one tool exists, so there is no possibility of confusion or misselection. The tool's purpose is unambiguous and clearly defined.
The tool name 'verify_email' follows a clear verb_noun pattern that matches its functionality. With only one tool, consistency is trivially maintained.
The server has a single tool, which feels thin but aligns with its narrow scope of email verification. The minimal count is borderline but not inappropriate given the focused domain.
The tool covers all key aspects of email verification—syntax, disposable-domain, and MX checks—and always returns a structured result. There are no obvious gaps within the stated purpose.