// ai agents and mcp
Via APIClaude Desktop email verification with pingutil
People paste lists of addresses into Claude and ask which ones look fake, and without a tool Claude can only judge by how an address looks. Adding the pingutil MCP server as a custom connector lets Claude verify mailboxes and classify domains with real checks. The official way to send the API key is the connector's Request headers setting, which Anthropic lists as a beta not every account has yet.
Where it connects: Custom connector by URL (Customize > Connectors > Add custom connector, No sign-in with a Request header)
What goes wrong without it
- I paste a list of event signups into Claude and ask which are fake, and it just guesses from the spelling.
- Our ops team lives in the Claude app and has no way to run an email check without asking engineering.
- The connector dialog seems built for OAuth and our service uses an API key.
What you can do with Claude Desktop and pingutil
Check a pasted list in chat
Paste up to 50 addresses and ask Claude to verify them with pingutil. It calls verify_emails and can return a table of address, status and reason that you copy into your spreadsheet.
Triage a support inbox's senders
Paste the sender addresses from a batch of suspicious tickets and ask Claude to classify them with lookup_email, so disposable and randomized senders are flagged before anyone spends time on a reply.
Research a domain before a call
Ask "who is behind acme-robotics.io" and Claude calls lookup_email, returning the category and, for company domains, the profile with industry, headquarters and employee range.
Set it up
- 1
Create an API key in the pingutil dashboard.
- 2
In Claude, open Customize > Connectors, select Add, then Add custom connector, enter the name pingutil and the URL https://pingutil.com/mcp, then Continue. On Team and Enterprise plans an Owner adds it under Organization settings > Connectors instead.
- 3
For Authentication choose No sign-in, open Request headers, pick authorization from the list and enter the value Bearer followed by a space and your key. Claude sends the value exactly as typed, so include the word Bearer.
- 4
Click Add, then turn the connector on for a chat from the + menu under Connectors.
- 5
If your dialog has no Request headers section (the feature is in beta for a limited set of organizations), the only route is a local bridge: the community package mcp-remote (github.com/geelen/mcp-remote) run from claude_desktop_config.json, as in the example. It is not an Anthropic product and needs Node.js.
{
"mcpServers": {
"pingutil": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://pingutil.com/mcp",
"--transport",
"http-only",
"--header",
"Authorization:${PINGUTIL_AUTH}"
],
"env": {
"PINGUTIL_AUTH": "Bearer pk_live_your_key_here"
}
}
}
}What to do with each result
| pingutil result | Action in Claude Desktop |
|---|---|
| status valid | Mark the address as fine in the table Claude returns. |
| status invalid with did_you_mean | Show the suggested correction next to the address instead of dropping it. |
| status risky (accept_all) or unknown | Keep the address but label it unconfirmed; ask Claude not to treat these as fake. |
| lookup_email: category disposable or verdict.is_spam true | Flag the sender as throwaway in the triage summary. |
| lookup_email: category company with company profile | Summarise the company name, industry and size for the account note. |
Limits to plan for
- Request header authentication is a beta available to a limited set of organizations, per Anthropic's docs. Authentication settings cannot be edited after you add a connector: remove it and add it again to change the key. pingutil has no OAuth sign-in.
- The mcp-remote bridge is community software, not an Anthropic or pingutil product. Its README notes that Claude Desktop on Windows does not escape spaces inside args, which is why the example keeps the space in the env value and none around the colon.
- Verification of slow mail servers can take several seconds (up to about 25 s), and calls count toward the key's Free plan limits: 300 verifications a day and 3,000 a month, 2,000 lookups a day and 30,000 a month.
Claude Desktop documentation
- claude.com/docs/connectors/custom/add-unlisted
- support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Claude Desktop is a trademark of its owner. This integration uses Claude Desktop's documented extension points; it is not an official Claude Desktop app.
Common questions
- Can I add pingutil to claude_desktop_config.json directly with a URL and headers?
- Anthropic documents remote servers in Claude Desktop through custom connectors, not through the config file. The config file runs local commands, which is why the fallback uses mcp-remote as a local bridge to the remote URL.
- Does Claude see my API key?
- With a custom connector, Claude stores the header value as the connector's credential and does not show it again after you save. With the bridge, the key sits in plain text in claude_desktop_config.json on your computer, so treat that file like a password.
- Which tools does the server expose?
- verify_email, verify_emails (up to 50 addresses per call) and lookup_email. All are read-only, so you can allow them without risk of changes to your data, though each call counts toward your limits.
Stop bad addresses in Claude Desktop today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Claude Desktop setup will receive.