MyEmailVerifier for AI agents
MyEmailVerifier checks email addresses for deliverability and risk signals like disposable, role-based, or catch-all status before they enter a mailing list. 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 MyEmailVerifier.
Verify one address, read-only
Check one email address's deliverability and risk signals before it enters an outreach list, a read-only check.
Verify a batch of emails
Run a batch of contact emails through verification before a list import.
Flag risky role-based addresses
Check whether an address is role-based, like info@, before treating it as a personal contact.
2 MyEmailVerifier actions, graded by risk.
Every MyEmailVerifier 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.
- myemailverifier.verify_emailVerify Email
- myemailverifier.verify_emailsVerify 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.
MyEmailVerifier in three steps.
- 01Your users connect MyEmailVerifierThey add their MyEmailVerifier 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 MyEmailVerifier through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('myemailverifier', { 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 MyEmailVerifier connects.
Users add their MyEmailVerifier 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 MyEmailVerifier 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 MyEmailVerifier from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
MyEmailVerifier and Arc0, answered.
Can I use MyEmailVerifier with Claude, ChatGPT or Cursor?
Yes. Connect MyEmailVerifier 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 MyEmailVerifier actions you allow.
How do users connect MyEmailVerifier?
Users add their MyEmailVerifier 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 MyEmailVerifier 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 MyEmailVerifier?
Yes. Allow read actions and deny writes in the MyEmailVerifier policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call MyEmailVerifier too?
Yes. The same MyEmailVerifier connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug MyEmailVerifier into your agent.
Your users connect MyEmailVerifier 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