Email Verification MCP Server
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_emailC | Verify an email address for deliverability and status |
| mcpingA | Check if the MCP server is alive and responsive |
| mchelpC | Show tool help and usage examples |
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 3 tools
verify_email is the only domain-specific tool, while mcping and mchelp serve clearly separate utility purposes. There is no functional overlap or ambiguity between the tools.
verify_email follows a clear verb_noun pattern, but mcping and mchelp use a different no-underscore 'mc' prefix style. The names are still readable, but the set does not follow a single consistent convention.
Three tools is a reasonable count for a focused server, though two of the three are generic meta tools rather than domain operations. The effective domain surface is minimal but not unreasonable.
The core email verification operation is present and covers the primary need of checking deliverability and status. Batch verification or more granular diagnostics could be added, but agents can work around those gaps.