Available

Findymail MCP server

Findymail is a B2B contact data provider that finds and verifies email addresses and phone numbers for sales outreach, used by SDRs building prospecting lists. Connect through Arc0 to use the actions your identity is allowed to call.

EmailAPI keyMCP + RESTfindymail.com
AUDIT LOG · FINDYMAILPOLICY: acme-support
09:41:07 · claude · u_8f2read
findymail.list_contact_lists
List contact lists✓ allowed · 212ms
09:41:08 · claude · u_8f2read
findymail.get_credits
Get remaining credits✓ allowed · 164ms
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Findymail.

01

Find email by name

Find a verified work email. Use when a full name and employer are known, not when an email is already available. Costs one finder credit only when found. A timed-out lookup may still be charged; do not retry blindly.

02

Find email by LinkedIn profile

Find a verified work email from a LinkedIn profile or username. Use when a profile is known, not when an email is already available. Costs one finder credit only when found. A timed-out lookup may still be charged; do not retry blindly.

03

Verify email

Check deliverability and mail provider. Use when an email from another source needs checking. Do not use on finder results: they are already verified. Costs one verifier credit per attempt.

02 · ACTIONS

5 Findymail actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

5

Look things up, subject to your permissions.

  • findymail.find_email_by_name
    Find email by name

    Find a verified work email. Use when a full name and employer are known, not when an email is already available. Costs one finder credit only when found. A timed-out lookup may still be charged; do not retry blindly.

  • findymail.find_email_by_linkedin
    Find email by LinkedIn profile

    Find a verified work email from a LinkedIn profile or username. Use when a profile is known, not when an email is already available. Costs one finder credit only when found. A timed-out lookup may still be charged; do not retry blindly.

  • findymail.verify_email
    Verify email

    Check deliverability and mail provider. Use when an email from another source needs checking. Do not use on finder results: they are already verified. Costs one verifier credit per attempt.

  • findymail.get_credits
    Get remaining credits

    Read remaining finder and verifier credits. Use when checking capacity before paid lookups; not for account identity or historical usage.

  • findymail.list_contact_lists
    List contact lists

    Read contact-list IDs, names and sharing flags. Use when locating a list or checking ownership; not to retrieve contacts or change lists. The limit bounds output locally; the vendor has no documented pagination.

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · POLICIES AND AUDIT

Control access to Findymail.

Connect the intended Findymail 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 approvals

Example policy choices

  • Read actions: allow where authorized

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Findymail connects.

Connect Findymail 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
05 · AI CLIENTS

Use Findymail with your AI client.

Sign in to Arc0 and connect Findymail in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Findymail with Claude

Claude Desktop + Claude Code

  1. 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.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Findymail with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. 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/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Findymail with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. 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/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Findymail with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. 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/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Findymail with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Findymail with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. 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.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

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

07 · FAQ

Findymail and Arc0, answered.

Q01

Does Findymail 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.

Q02

Can I use Findymail 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.

Q03

Is this the official Findymail MCP server?

This is Arc0’s integration page, not a claim of an official Findymail server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Findymail for its own current MCP offerings.

Q04

Which Findymail actions are supported?

5 registry-defined actions: 5 read, 0 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Findymail need?

Connect Findymail 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.

Q06

Can I restrict writes in Findymail?

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.

Q07

What does Findymail 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.

Get started

Plug Findymail into your agent.

Findymail MCP server: 5 actions including find email by name, find email by linkedin profile, verify email. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Findymail and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Findymail.