Skip to main content
Glama
Meerkats-Ai

NeverBounce MCP Server

by Meerkats-Ai
README.md
# NeverBounce MCP Server

This is a Model Context Protocol (MCP) server that integrates with the NeverBounce API to provide email validation capabilities.

## Features

- Validate email addresses to check if they are valid, deliverable, and safe to send to

## Setup

### Local Setup

1. Clone this repository
2. Install dependencies:
   ```
   npm install
   ```
3. Create a `.env` file based on `.env.example` and add your NeverBounce API key:
   ```
   NEVERBOUNCE_API_KEY=your_api_key_here
   ```
4. Build the server:
   ```
   npm run build
   ```
5. Start the server:
   ```
   npm start
   ```

### Docker Setup

1. Clone this repository
2. Create a `.env` file with your NeverBounce API key
3. Build and run using Docker Compose:
   ```
   docker-compose up -d
   ```

## MCP Configuration

To use this server with an MCP client, add the following configuration to your MCP settings file:

```json
{
  "mcpServers": {
    "neverbounce": {
      "command": "node",
      "args": ["path/to/neverbounce/dist/index.js"],
      "env": {
        "NEVERBOUNCE_API_KEY": "your_api_key_here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
```

## Available Tools

- `neverbounce_validate_email`: Validate an email address to check if it's valid and deliverable

## License

ISC

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessSyncing