ListCheckup

com.listcheckupPublished by listcheckup.comOfficial publisherv1.0.0Updated Oct 29, 2026

Email verification for AI agents: check addresses and lists, priced before credits are spent.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

ListCheckup verifies email addresses and lists for AI assistants, pricing a list before any credits are spent.

What you can do
  • Verify a single email address and get its status, reason and confidence score
  • Check the account's remaining credits
  • Submit a list to get a price, then start the check once approved
  • Track list progress and read counts by status when a list finishes
When to use it
Useful when an assistant works with contact or lead data and needs to confirm which addresses are deliverable before sending, or to estimate the cost of verifying a whole list before committing credits.
Requirements
Remote Streamable HTTP endpoint; no local install. Requires a ListCheckup account and an API key sent as an Authorization bearer header. Network access to the service is needed.
Before you install
The API key can spend account credits, so keep it out of shared repositories and revoke it if leaked. Starting a list check spends credits, though pricing and starting are separate tools so cost can be shown first. Only addresses you already hold may be checked; purchased, rented or scraped lists are not allowed.

Installation

In SourceWeft

  1. Open ListCheckup in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.listcheckup%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "listcheckup": {
      "type": "http",
      "url": "https://listcheckup.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

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

Claude Desktop, Cursor and most other clients

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

Check it works

bash
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.

Source: README.md at commit ad667d1

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.