RevenueBase MCP Server

How to use

Start the server using your preferred MCP client workflow, then connect with an MCP client to access all verification tools. You can verify a single email in real time, submit large batches for processing, check job status, view queued tasks, cancel jobs, and monitor remaining credits. You can also generate new API keys for secure access. The server supports catch-all domains and can navigate common email firewalls to improve delivery verification.

How to install

# Prerequisites: Python 3.7+, uvw, and a shell
# 1) Clone the repository and enter the directory
git clone https://github.com/avivshafir/revenuebase-mcp-server
cd revenuebase-mcp-server

# 2) Install dependencies using uv
uv sync

# 3) Set up your RevenueBase API key
export REVENUEBASE_API_KEY="your_api_key_here"

# 4) Run the server
python server.py

Configuration and connection details

Prepare your MCP client configuration to connect to the local server using the standard stdio transport. The server runs as a local process and accepts connections on stdin/stdout. Use the following approach to start the server with the MCP client wrapper that invokes the Python entry point and passes your API key.

# Example MCP stdio wrapper configuration (shown for clarity in this guide)
{
  "type": "stdio",
  "name": "revenuebase",
  "command": "uv",
  "args": ["--directory", "/path/to/revenuebase-mcp-server", "run", "python", "server.py"],
  "env": {
    "REVENUEBASE_API_KEY": "your_api_key_here"
  }
}

Using with Claude Desktop

If you are using Claude Desktop, place the following configuration in your Claude Desktop config file to connect to the MCP server. This uses the stdio transport via uv to launch the local server with the Python entry point and your API key.

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

Available tools and how to use them

The server exposes a set of tools you can call from your MCP client to perform tasks.

1) Real-time Email Verification Verifies a single email address instantly.

2) Batch Email Submission Submits a reference to a batch file for processing.

3) Batch Process Status Checks the status of a batch processing job.

4) Queued Processes Lists all currently queued batch jobs.

5) Cancel Process Cancels an ongoing or queued batch job.

6) Get Credits Retrieves the remaining API credits for your account.

7) Generate New API Key Generates and returns a new API key.

Security and credentials

Keep your RevenueBase API key secure. Do not expose it in client-side code or public repositories. Use an environment variable in your MCP client configuration and rotate keys periodically.

Notes and tips

- Your server requires Python 3.7+ and the listed MCP tooling to run smoothly. - The API endpoints you use from your server correspond to the RevenueBase endpoints for real-time verification, batch processing, batch status, queued processes, credits, and API key generation.

Troubleshooting

If the server does not start, ensure that you have set REVENUEBASE_API_KEY in the environment and that the Python entry point (server.py) exists in the project directory. Check that uv is installed and that the directory path in the config matches where you cloned the repository. If HTTP endpoints are returning errors, verify that the API key is valid and that you have network access to RevenueBase services.

Notes on availability and compatibility

This MCP server is designed to work with MCP clients that support stdio transport or the uv wrapper for launching local MCP servers. It requires a compatible Python runtime and the uv client tooling to orchestrate the server process.

Appendix: API keys and endpoints

Environment variable: REVENUEBASE_API_KEY must be set to your RevenueBase API key.

Usage examples

Real-time verification and batch processing can be combined in your application flow. Verify an email first to confirm its validity, then batch-process larger lists to optimize throughput and monitor credits to manage usage.

real_time_email_verification

Verifies a single email address in real time and returns verification status and risk indicators.

batch_email_submission

Submits a file reference or list for batch email processing and returns a batch job identifier.

batch_process_email_status

Checks the status of a running batch processing job using its process ID.

queued_process

Retrieves a list of all currently queued batch processing jobs.

cancel_process

Cancels an ongoing or queued batch processing job by its ID.

get_credits

Fetches the remaining API credits available to your account.

new_api_key

Generates and returns a new API key for secure access.