mcpField
L
ListCheckup

ListCheckup

Remote
listcheckup.comBusiness & Marketing0Updated 1d ago

About ListCheckup

ListCheckup is an MCP server for AI assistants that verifies individual email addresses and lists. It separates list pricing from starting a check, so the cost is shown before credits are used.

Key features

  1. 01Verify one email address
  2. 02Check email lists
  3. 03Preview list cost before starting
  4. 04View balance and list progress
  5. 05Return status, reason, and confidence

Use cases

  1. 01Check an address before contacting it
  2. 02Estimate verification cost for a lead list
  3. 03Review list-check progress and results

MCP support

Exposes email and list verification tools to MCP clients over remote Streamable HTTP. Access uses a bearer key, and list pricing is separate from starting the check.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://listcheckup.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://listcheckup.com/mcpAuth required

Tools

Details

From the project README

ListCheckup MCP server

Email verification for AI assistants. Connect Claude, Cursor or any MCP client to ListCheckup and let it check a single address or a whole list, showing you the price before anything is spent.

  • Endpoint: https://listcheckup.com/mcp (remote, Streamable HTTP)
  • Auth: Authorization: Bearer lck_live_... (create a key in your ListCheckup dashboard)
  • Free tier: 100 checks every month, no card. Catch-all and unknown results are not charged, and credits never expire.
  • Data: processed on EU servers. Nothing is sent to the addresses being checked.

Tools

ToolWhat it doesCost
check_emailVerify one address: valid, invalid, risky, catch-all or unknown, with the reason and a confidence score1 credit (free if catch-all or unknown)
get_balanceCredits left on the accountFree
create_listSubmit a list and get its priceFree
start_listStart checking a list you've pricedSpends credits
get_listStatus and progress of a listFree
get_list_summaryCounts by status once a list is finishedFree

Pricing and starting are separate tools on purpose: an assistant has to show you what a list will cost before anything is spent, and you can say no. No tool takes an account as an argument; the key in the header decides whose credits are used.

Connect

Claude Code

claude mcp add --transport http listcheckup https://listcheckup.com/mcp \
  --header "Authorization: Bearer lck_live_..."

Claude Desktop, Cursor and most other clients

{
  "mcpServers": {
    "listcheckup": {
      "url": "https://listcheckup.com/mcp",
      "headers": { "Authorization": "Bearer lck_live_..." }
    }
  }
}

Check it works

curl -X POST "https://listcheckup.com/mcp" \
  -H "Authorization: Bearer lck_live_..." \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Six tools listed means you're connected.

Example prompts

  • "Check whether [email protected] is a real address."
  • "Here's my leads CSV. How much would it cost to verify it? Don't start until I say so."
  • "How many credits do I have left?"

Treat the key as a password

Anything holding it can spend your credits. Keep config files with the key out of shared repositories, give each machine its own key, and revoke a key in the dashboard if it leaks. Revoking takes effect immediately.

Links

ListCheckup checks addresses you already hold. Purchased, rented or scraped lists aren't allowed under the acceptable use policy.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.