NeverBounce MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEVERBOUNCE_API_KEY | Yes | Your NeverBounce API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| neverbounce_validate_emailC | Validate an email address to check if it's valid and deliverable. |
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 or overlap with other tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently follows a consistent naming pattern, as there are no other tools to compare it against. The tool name 'neverbounce_validate_email' is clear and descriptive.
A single tool is too few for a server dedicated to email validation, as it lacks complementary operations like bulk validation, status checking, or integration with other email-related functions. This minimal scope limits functionality and may require agents to work around gaps.
The server is severely incomplete for email validation; it only offers single email validation without support for batch processing, result history, or additional verification features (e.g., disposable email detection). This will likely cause agent failures in more complex workflows.