PureChecker for AI agents
PureChecker verifies email addresses for syntax, domain, deliverability, and risk signals, individually or in batches. Marketing and sales teams use it to keep email lists clean before sending. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in PureChecker.
Check a single email address
Verify one email address's deliverability before adding it to a campaign list.
Batch check an email list
Run a list of email addresses through validation before a bulk campaign send.
Flag risky addresses for review
Surface addresses with high risk signals for a human to review before removing them.
2 PureChecker actions, graded by risk.
Every PureChecker action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- purechecker.check_emailCheck Email
- purechecker.check_emailsCheck Emails
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
PureChecker in three steps.
- 01Your users connect PureCheckerThey add their PureChecker api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls PureChecker through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('purechecker', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How PureChecker connects.
Users add their PureChecker api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same PureChecker connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use PureChecker from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
PureChecker and Arc0, answered.
Can I use PureChecker with Claude, ChatGPT or Cursor?
Yes. Connect PureChecker to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the PureChecker actions you allow.
How do users connect PureChecker?
Users add their PureChecker api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which PureChecker actions can my agent take?
2 in total: 2 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in PureChecker?
Yes. Allow read actions and deny writes in the PureChecker policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call PureChecker too?
Yes. The same PureChecker connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug PureChecker into your agent.
Your users connect PureChecker once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan