Skip to main content
Home Features Pricing Blog Support Log In Try It Free
AI Assistants

Verify emails from your AI assistant

BounceKo runs a Model Context Protocol (MCP) server. Connect it to an AI assistant such as Claude or ChatGPT and the assistant can verify email addresses with your BounceKo credits and check your credit balance, without you leaving the conversation. You sign in with your BounceKo account the first time, and you can disconnect the assistant at any time.

Server address:

https://app.bounceko.com/mcp

You need a BounceKo account with credits. Every new account gets 100 free credits to start.

What it does

The server gives your assistant two tools. It runs the same verification as the BounceKo dashboard and API, and the results follow the verification settings on your account.

Tool What it does
verify_email Verifies 1 to 25 email addresses in one call. For each address it returns a status (valid, invalid, risky, do_not_email, unknown or invalid_format), the reason, and flags for disposable, free-provider and role addresses. An address that could not be completed comes back as not_verified and can be submitted again.
get_credit_balance Returns your credit balance: the total, and how much is trial, lifetime-deal and purchased credit.

What it costs

  • Each unique, valid address that BounceKo verifies uses 1 credit from your existing balance.
  • Results marked unknown are free.
  • An address repeated within one call is charged once. Text that is not a valid email address is not charged.
  • Checking your balance is free.
  • If your balance does not cover the unique addresses in a call, nothing is verified and the assistant is told how many credits you have.

You buy credits in the BounceKo dashboard, not inside the assistant. See pricing for credit packs.

Connect Claude

This works in Claude on the web and in the desktop app.

  1. Open Settings, then Connectors.
  2. Choose Add custom connector.
  3. Enter a name such as BounceKo and the server address https://app.bounceko.com/mcp.
  4. Sign in to BounceKo when asked and approve the connection.

Connect ChatGPT

In ChatGPT, add a custom MCP server and enter the server address https://app.bounceko.com/mcp. When ChatGPT asks you to sign in, use your BounceKo account and approve the connection. Where the custom server option appears depends on your ChatGPT plan and settings.

Connect Claude Code

Run this once. Claude Code opens a BounceKo sign-in the first time a tool is used.

claude mcp add --transport http bounceko https://app.bounceko.com/mcp

To use an API key instead, set BOUNCEKO_API_KEY in your shell and add the header. Your shell fills in the value when you run the command, so Claude Code saves your API key in its own configuration. The variable only keeps the key out of what you type and out of your shell history. On macOS and Linux:

claude mcp add --transport http bounceko https://app.bounceko.com/mcp --header "Authorization: Bearer $BOUNCEKO_API_KEY"

In Windows PowerShell the variable is written $env:BOUNCEKO_API_KEY. Check that it is set first: in PowerShell a plain $BOUNCEKO_API_KEY that is not set becomes empty without an error, and BounceKo then answers with a 401.

claude mcp add --transport http bounceko https://app.bounceko.com/mcp --header "Authorization: Bearer $env:BOUNCEKO_API_KEY"

Connect Cursor

Add this to ~/.cursor/mcp.json. Cursor opens a BounceKo sign-in the first time a tool is used.

{
  "mcpServers": {
    "bounceko": {
      "url": "https://app.bounceko.com/mcp"
    }
  }
}

To use an API key instead, set BOUNCEKO_API_KEY in the environment Cursor starts from and send it in a header:

{
  "mcpServers": {
    "bounceko": {
      "url": "https://app.bounceko.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:BOUNCEKO_API_KEY}"
      }
    }
  }
}

Cursor fills in the ${env:BOUNCEKO_API_KEY} in the header from that variable.

Connect VS Code

Add this to .vscode/mcp.json. VS Code opens a BounceKo sign-in the first time a tool is used.

{
  "servers": {
    "bounceko": {
      "type": "http",
      "url": "https://app.bounceko.com/mcp"
    }
  }
}

To use an API key instead, have VS Code ask for it when the server starts, so it is not stored in the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "bounceko-api-key",
      "description": "Bounceko API key",
      "password": true
    }
  ],
  "servers": {
    "bounceko": {
      "type": "http",
      "url": "https://app.bounceko.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:bounceko-api-key}"
      }
    }
  }
}

You can find your API key in the dashboard, on the API tab. The same tab has the Claude Code and Cursor snippets with a button that copies them with your key filled in. VS Code always asks for the key instead, because .vscode/mcp.json is a workspace file that is often committed.

Security and privacy

  • Assistants that support sign-in never receive your API key. You approve each connection on a BounceKo page, and the assistant gets its own access token, which BounceKo stores only as a hash.
  • You can see every connected app on the API tab of the dashboard, under Connected apps, and disconnect it there.
  • Changing your password or your email address disconnects every connected app. Signing out does not.
  • Verification results come back to the assistant, so they become part of your conversation with it. Check the privacy policy of the assistant provider for how it handles conversations.
  • BounceKo's own handling of these connections is described in the privacy policy.

Frequently asked questions

MCP, the Model Context Protocol, is an open standard that lets an AI assistant call tools in another service. BounceKo runs an MCP server, so an assistant that supports MCP can verify email addresses and read your credit balance on your behalf.

Any client that supports remote MCP servers over HTTPS. This page has setup steps for Claude, ChatGPT, Claude Code, Cursor and VS Code. Most of them sign you in with your BounceKo account the first time you use the connection.

No. Assistants that support sign-in open a BounceKo sign-in and consent page, and your API key is never shared with them. If a tool cannot sign in, you can send your API key in an Authorization header instead.

Each unique, valid address that BounceKo verifies uses 1 credit from your existing balance. Results marked unknown are not charged, repeated addresses in one request are charged once, and checking your balance is free. You buy credits in the BounceKo dashboard, not inside the assistant.

Up to 25 addresses per call. For larger lists, upload a file in the BounceKo dashboard or use the bulk API.

Yes. The results come back to the assistant so it can answer you, which means they become part of your conversation with that assistant. How the assistant provider handles conversations is covered by its own privacy policy.

Sign in to the BounceKo dashboard, open the API tab and use the Disconnect button next to the app under Connected apps. The assistant stops working with your account straight away. Changing your password or your email address also disconnects every connected app.

No. Disconnecting stops future access. Verification records an assistant already created are kept on your account like other API verifications, until they are removed by the normal retention period. They are not shown in your dashboard history. To ask for earlier deletion, contact us through the support page.