Icypeas MCP server
Icypeas finds and verifies professional email addresses using a person's name and company domain, for sales prospecting. Teams use it to keep this process accurate at a scale manual review cannot match. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for Icypeas.
Start email search
Use when finding an unknown email for one person, not when the address is known (use verification). Enqueues one search; poll get_search. Costs 1 credit per found email. A timeout may still be charged; do not blindly resubmit.
Start email verification
Use when verifying one known email, not discovering an unknown address (use email search). Enqueues one job; poll get_search. Costs 0.1 credit per tested email. A timeout may still be charged; do not blindly resubmit.
Start domain scan
Use when finding role mailboxes for one domain, not a named person (use email search). Enqueues one scan; poll get_search. Budget 1 credit per domain. A timeout may still be charged; do not blindly resubmit.
7 Icypeas actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
3Look things up, subject to your permissions.
- icypeas.get_searchGet search
Use when polling one search id, not a bulk file (use list_results). One request; wait 2s between polls. NOT_FOUND/DEBITED_NOT_FOUND retain the item with no emails; null means absent. See terminal/status fields for end states; INSUFFICIENT_FUNDS carries a 403 permission error.
- icypeas.list_resultsList results
Use when paging a known bulk file or search id, not starting new searches. Send returned sorts with next=true (forward) or false (backward); stop on empty items. Total is collection size. Free; 30 requests/minute. For one job poll use get_search.
- icypeas.get_subscriptionGet subscription
Use when reading the configured key-owner account credit balance and plan before paid lookups, not changing billing or reading another account. Key/email ownership needs live verification. Invoice and checkout links are excluded.
write
4Create and change things. Allow, or ask the user first.
- icypeas.start_email_searchStart email search
Use when finding an unknown email for one person, not when the address is known (use verification). Enqueues one search; poll get_search. Costs 1 credit per found email. A timeout may still be charged; do not blindly resubmit.
- icypeas.start_email_verificationStart email verification
Use when verifying one known email, not discovering an unknown address (use email search). Enqueues one job; poll get_search. Costs 0.1 credit per tested email. A timeout may still be charged; do not blindly resubmit.
- icypeas.start_domain_scanStart domain scan
Use when finding role mailboxes for one domain, not a named person (use email search). Enqueues one scan; poll get_search. Budget 1 credit per domain. A timeout may still be charged; do not blindly resubmit.
- icypeas.scrape_profileScrape profile
Use when enriching one known LinkedIn person URL, not company pages or name discovery. Returns a compact profile or null. Costs 1.5 credits per found profile. A timeout may still be charged; do not blindly repeat.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to Icypeas.
Connect the intended Icypeas account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- icypeas.scrape_profile: require approval
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Icypeas connects.
Connect Icypeas using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. 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 Icypeas with your AI client.
Sign in to Arc0 and connect Icypeas in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Icypeas with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingIcypeas with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingIcypeas with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingIcypeas with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingIcypeas with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingIcypeas with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
Icypeas and Arc0, answered.
Does Icypeas work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use Icypeas with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official Icypeas MCP server?
This is Arc0’s integration page, not a claim of an official Icypeas server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Icypeas for its own current MCP offerings.
Which Icypeas actions are supported?
7 registry-defined actions: 3 read, 4 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does Icypeas need?
Connect Icypeas using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in Icypeas?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does Icypeas through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug Icypeas into your agent.
Icypeas MCP server: 7 actions including start email search, start email verification, start domain scan. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Icypeas and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Icypeas.