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_emailB | Verify email address syntax, disposable domain status, and MX plausibility |
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
With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly stated and distinct.
The single tool name 'verify_email' follows a clear verb_noun pattern, which is consistent and predictable.
The server has only one tool, which feels thin for a general-purpose email verification service. However, for a narrowly scoped utility, the single tool could be acceptable, making it borderline.
The tool covers syntax, disposable domain status, and MX plausibility, but lacks SMTP-level verification or mailbox existence checks. This leaves a significant gap for a service named 'inboxvalid'.