Skip to main content
Glama
revenuebase-mcp-server

revenuebase-mcp-server

by avivshafir

RevenueBase MCP Server

A Model Context Protocol (MCP) server that provides access to RevenueBase's industry-leading email verification API. This server enables AI assistants and applications to verify business emails, including catch-all and firewall-protected domains, with over 99% accuracy.

Features

  • Real-time Email Verification: Verify individual email addresses instantly

  • Batch Email Processing: Submit and process large email lists

  • Process Management: Monitor, cancel, and track batch processing jobs

  • Credit Management: Check remaining API credits

  • API Key Management: Generate new API keys

  • High Accuracy: Over 99% accuracy for B2B email verification

  • Catch-All Domain Support: Verify catch-all email domains that other tools can't handle

  • Firewall Navigation: Bypass email firewalls like Mimecast and Barracuda

Related MCP server: json-mcp-server

About RevenueBase

RevenueBase provides industry-leading email verification services specifically built for B2B data providers. With the ability to verify catch-all and firewall-protected domains, RevenueBase ensures maximum accuracy where other services fall short.

Learn more about RevenueBase's email verification services at: https://revenuebase.ai/email-list-cleaning/

Installation

  1. Clone this repository:

git clone https://github.com/avivshafir/revenuebase-mcp-server
cd revenuebase-mcp-server
  1. Install dependencies using uv:

uv sync
  1. Set up your RevenueBase API key:

export REVENUEBASE_API_KEY="your_api_key_here"

Usage

Running the Server

python server.py

The server will start and be available for MCP connections.

Using with MCP Clients

Claude Desktop

To use this server with Claude Desktop, add the following configuration to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "revenuebase": {
      "command": "uv",
      "args": ["--directory", "/path/to/revenuebase-mcp-server", "run", "python", "server.py"],
      "env": {
        "REVENUEBASE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Replace /path/to/revenuebase-mcp-server with the actual path to your cloned repository and your_api_key_here with your actual RevenueBase API key.

Other MCP Clients

For other MCP clients, you can connect to the server using the stdio transport. The server runs as a standard MCP server and accepts connections on stdin/stdout.

Example using the MCP Python SDK:

from mcp import ClientSession, StdioServerParameters
from mcp.client.stdio import stdio_client

server_params = StdioServerParameters(
    command="python",
    args=["server.py"],
    env={"REVENUEBASE_API_KEY": "your_api_key_here"}
)

async with stdio_client(server_params) as (read, write):
    async with ClientSession(read, write) as session:
        # Initialize the connection
        await session.initialize()
        
        # List available tools
        tools = await session.list_tools()
        print("Available tools:", [tool.name for tool in tools.tools])
        
        # Call a tool
        result = await session.call_tool("real_time_email_verification", {
            "email": "test@example.com"
        })
        print("Verification result:", result)

Available Tools

1. Real-time Email Verification

Verify a single email address instantly.

Parameters:

  • email (string): The email address to verify

Example:

real_time_email_verification("user@example.com")

2. Batch Email Submission

Submit a file reference for batch email processing.

Parameters:

  • filename (string): The filename reference for batch processing

Example:

batch_email_submission("email_list.csv")

3. Batch Process Status

Check the status of a batch email processing job.

Parameters:

  • process_id (int): The ID of the batch processing job

Example:

batch_process_email_status(12345)

4. Queued Processes

List all queued email batch processing jobs.

Example:

queued_process()

5. Cancel Process

Cancel an ongoing or queued batch email processing job.

Parameters:

  • process_id (int): The ID of the process to cancel

Example:

cancel_process(12345)

6. Get Credits

Retrieve the number of remaining credits for your account.

Example:

get_credits()

7. Generate New API Key

Generate and return a new API key.

Example:

new_api_key()

Configuration

Environment Variables

  • REVENUEBASE_API_KEY: Your RevenueBase API key (required)

API Endpoints

The server connects to the following RevenueBase API endpoints:

  • https://api.revenuebase.ai/v1/process-email - Real-time email verification

  • https://api.revenuebase.ai/v1/batch-process-email - Batch email submission

  • https://api.revenuebase.ai/v1/batch-process-email-status - Batch status check

  • https://api.revenuebase.ai/v1/queued-process - List queued processes

  • https://api.revenuebase.ai/v1/cancel-process - Cancel process

  • https://api.revenuebase.ai/v1/credits - Get credits

  • https://api.revenuebase.ai/v1/new-api-key - Generate new API key

Error Handling

All tools include proper error handling and will raise RuntimeError if the API key is not configured. HTTP errors from the RevenueBase API are automatically raised using requests.raise_for_status().

Requirements

  • Python 3.7+

  • fastmcp

  • requests

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For RevenueBase API support and documentation, visit:

For issues with this MCP server, please open an issue in this repository.

Available Tools

7 tools
batch_email_submissionC

Submits a file reference for batch email processing using the Revenuebase API.

Inputs: filename (required).

batch_process_email_statusC

Retrieves status of batch email processing job.

Inputs: process_id (required).

cancel_processC

Cancels an ongoing or queued batch email processing job using the Revenuebase API.

Inputs: process_id (required).

get_creditsA

Retrieves the number of remaining credits for the authenticated user.

Inputs: no named parameters.

new_api_keyB

Generates and returns a new API key for the user.

Inputs: no named parameters.

queued_processB

Lists all queued email batch processing jobs.

Inputs: no named parameters.

real_time_email_verificationC

Verifies a single email address using the Revenuebase API.

Inputs: email (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: batch_email_submission initiates processing, batch_process_email_status checks status, cancel_process stops jobs, get_credits shows credits, new_api_key generates keys, queued_process lists jobs, and real_time_email_verification verifies single emails. The descriptions reinforce these distinct functions, making tool selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent snake_case naming pattern with clear verb-noun combinations (e.g., batch_email_submission, real_time_email_verification). The naming convention is uniform across all seven tools, making them predictable and easy to understand at a glance.

    Tool Count5/5

    With 7 tools, this server is well-scoped for email verification and batch processing tasks. Each tool serves a specific, necessary function in the workflow, from initiation to status checks and management, without being overly sparse or bloated.

    Completeness4/5

    The tool set covers core email verification and batch processing operations comprehensively, including submission, status retrieval, cancellation, credit management, and API key generation. A minor gap exists in lacking a tool for detailed results of completed batch jobs, but agents can work around this using the status tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers