[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Findymail API and MCP server > Findymail has a full REST API with a Bearer key, but no first-party MCP server (checked 23 Oct 2026). Its API docs cover the email finder and verifier, contact lists, exclusion lists, Intellimatch lead search, Signals and credits, and mention no MCP. Your agent needs a wrapper that holds your API key. B2B email finder and verifier. It also runs Intellimatch, an AI lead search from a plain-English description of your ideal customer, with exclusion lists, contact lists and Signals. ## What is the Findymail API? Cotlet's Findymail API exposes 14 endpoints for your own Findymail account: get credits, list contact lists, list contacts, list exclusion lists, list excluded domains, get lead search, find email, verify email, create contact list, create exclusion list, add excluded domains, remove excluded domains, delete exclusion list and start lead search. The get_credits endpoint returns read the finder or verifier credit balance of your Findymail account. Each endpoint takes simple JSON inputs like list_id, name or query and works both as an operation of the findymail_read or findymail_write MCP tool for agents and as a REST call for scripts. - **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md) - **Endpoints:** 14 (8 read, 6 write) - **Updated:** 2026-10-21 Findymail has a full REST API with a Bearer key, but no first-party MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Findymail with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Findymail have an official API? Findymail has a full REST API with a Bearer key, but no first-party MCP server (checked 23 Oct 2026). Its API docs cover the email finder and verifier, contact lists, exclusion lists, Intellimatch lead search, Signals and credits, and mention no MCP. Your agent needs a wrapper that holds your API key. | Task | Findymail official | Cotlet | |---|---|---| | Find an email from a name and a domain | Yes: REST API, 1 finder credit when found | Yes | | Verify an email | Yes: REST API, 1 verifier credit per check | Yes | | List contact lists and read their contacts | Yes: REST API | Yes | | Create a contact list | Yes: REST API | Yes | | Manage exclusion lists and their domains | Yes: REST API, up to 10,000 domains per call | Yes | | Start an Intellimatch lead search and read the results | Yes: REST API, you poll a hash until the export is ready | Yes | | Check the credit balance | Yes: REST API | Yes | | Call all of it from an AI agent as MCP tools | No: No first-party MCP server | Yes | Sources: [Findymail API documentation](https://app.findymail.com/docs/), [Findymail pricing](https://www.findymail.com/pricing), [Findymail Intellimatch, the AI lead finder](https://www.findymail.com/ai-b2b-lead-finder/), [Findymail API for developers](https://www.findymail.com/api/) ## Quick reference ```text Findymail has a full REST API with a Bearer key, but no first-party MCP server (checked 23 Oct 2026). Its API docs cover the email finder and verifier, contact lists, exclusion lists, Intellimatch lead search, Signals and credits, and mention no MCP. Your agent needs a wrapper that holds your API key. Cotlet provides a hosted MCP server and REST API for Findymail: 14 tools (8 read, 6 write). Access Sign up at https://cotlet.dev/app/signup?app=findymail, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools findymail_read, findymail_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/findymail, each operation at its own route, e.g. POST /api/v1/findymail/excluded-domains Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations get_credits, list_contact_lists, list_contacts, list_exclusion_lists, list_excluded_domains, get_lead_search, find_email, verify_email, create_contact_list, create_exclusion_list, add_excluded_domains, remove_excluded_domains, delete_exclusion_list, start_lead_search Confirm delete_exclusion_list, start_lead_search (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/findymail-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=findymail, requests Findymail in the Cotlet console and creates an API key there. 2. The user signs in to Findymail once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Findymail for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted Findymail server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Findymail MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to Findymail in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Findymail only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no Findymail login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following Findymail's terms; Cotlet is not affiliated with Findymail. ``` ## What can an AI agent do in Findymail? Cotlet is best for outbound and growth teams who want their AI agent to run lead searches, find and verify emails and keep exclusion lists current without running or fixing a server. - **[Keep a prospecting exclusion list up to date](https://cotlet.dev/integrations/findymail-api-mcp-server/sync-exclusion-list.md)** (runs: weekly): "Add the domains of this month's new customers (acme.io, northwind.com, globex.co) to my Customers exclusion list in Findymail. Create the list if it does not exist, and skip domains that are already on it." → `list_exclusion_lists`, `create_exclusion_list`, `list_excluded_domains`, `add_excluded_domains` - **[Build a lead list from a description of your ideal customer](https://cotlet.dev/integrations/findymail-api-mcp-server/build-lead-list-from-icp.md)** (runs: weekly): "Run a targeted Findymail lead search for agencies in Europe that run paid ads for e-commerce brands. Find 200 companies, look for a Head of Growth or VP Marketing and their emails, skip my Customers list, and tell me when it is done." → `get_credits`, `list_exclusion_lists`, `start_lead_search`, `get_lead_search` - **Verify the emails in a contact list** (runs: weekly): "Take the contacts in my Q4 outreach list in Findymail and verify each email. Tell me how many are verified and list the ones that are not." → `list_contact_lists`, `list_contacts`, `verify_email` - **Find the email of a person at a company**: "Find the work email of Dana Whitfield at northwind.com. If Findymail finds one, give it to me with the domain it used." → `find_email` - **Check credits before a big search** (runs: daily): "Tell me how many finder and verifier credits I have left in Findymail, and warn me if the finder balance is below 500." → `get_credits` ## Can Findymail automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Findymail connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to keep a prospecting exclusion list up to date, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/findymail/exclusion-lists. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/findymail/exclusion-lists with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Findymail. ### get_credits Read the finder or verifier credit balance of your Findymail account. Access: read. REST: `GET /api/v1/findymail/credits`. MCP: `findymail_read → get_credits`. | Parameter | Type | Required | Description | |---|---|---|---| | `type` | string | no | finder (default) or verifier. | Returns the credits left for the type you ask for, the account email and has_capacity. has_capacity is only filled on usage-based plans, where false means the plan limit is reached; on credit-based plans it is null and the agent reads the credits number. Credits belong to the team owner, so every member sees the same balance. Reading the balance is free. Example response: ```json { "credits": 4210, "email": "maya@yourname.com", "has_capacity": null } ``` ### list_contact_lists List your Findymail contact lists with their IDs. Access: read. REST: `GET /api/v1/findymail/contact-lists`. MCP: `findymail_read → list_contact_lists`. No parameters. Returns every list with its ID, name, dates, whether it is shared with the team and whether you own it. Use the ID in list_contacts. Reading lists is free. Example response: ```json { "lists": [ { "id": 3108, "name": "Q4 outreach", "created_at": "2026-09-30T08:12:00Z", "updated_at": "2026-10-21T14:03:00Z", "shared_with_team": false, "is_owner": true }, { "id": 2975, "name": "Webinar leads", "created_at": "2026-08-12T10:40:00Z", "updated_at": "2026-09-02T09:15:00Z", "shared_with_team": true, "is_owner": true } ] } ``` ### list_contacts Read the contacts saved in one of your lists, or in all of them. Access: read. REST: `GET /api/v1/findymail/contacts`. MCP: `findymail_read → list_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `list_id` | integer | no | List ID from list_contact_lists. Omit or pass 0 for all contacts. | Returns each contact with its ID, name, email, LinkedIn URL, company and job title, with totals for the list. The tool reads contacts only; it does not add them to a list. Reading contacts is free. Example response: ```json { "recordsTotal": 2, "data": [ { "id": 88120, "name": "Dana Whitfield", "email": "dana@northwind.com", "linkedin_url": "https://www.linkedin.com/in/example-dana", "company": "Northwind Logistics", "job_title": "Head of Growth" }, { "id": 88121, "name": "Luis Ortega", "email": "luis@globex.co", "linkedin_url": "https://www.linkedin.com/in/example-luis", "company": "Globex", "job_title": "VP Marketing" } ] } ``` ### list_exclusion_lists List the exclusion lists you own or share with your team. Access: read. REST: `GET /api/v1/findymail/exclusion-lists`. MCP: `findymail_read → list_exclusion_lists`. No parameters. Returns each list with its ID, name, whether it is shared, whether you own it and the owner name. The global exclusion list is not in the result: it is the one used when a call has no list ID. Reading lists is free. Example response: ```json { "lists": [ { "id": 1204, "name": "Customers", "is_shared": true, "is_owner": true, "user_id": 5512, "owner_name": "Maya" }, { "id": 1230, "name": "Past prospects", "is_shared": false, "is_owner": true, "user_id": 5512, "owner_name": "Maya" } ] } ``` ### list_excluded_domains Read the domains on an exclusion list, or on the global list. Access: read. REST: `GET /api/v1/findymail/excluded-domains`. MCP: `findymail_read → list_excluded_domains`. | Parameter | Type | Required | Description | |---|---|---|---| | `list_id` | integer | no | Exclusion list ID. Omit it to read the global exclusion list. | | `query` | string | no | Only domains that contain this text. | | `page` | integer | no | Page number, starting at 1. | | `per_page` | integer | no | Domains per page. | Returns each domain with its ID and the list it belongs to, with the current page, the page size and the total. The domain IDs are what remove_excluded_domains takes. Reading domains is free. Example response: ```json { "data": [ { "id": 990114, "domain": "acme.io", "excluded_domain_list_id": 1204 }, { "id": 990115, "domain": "northwind.com", "excluded_domain_list_id": 1204 } ], "current_page": 1, "per_page": 50, "total": 2 } ``` ### get_lead_search Check an Intellimatch lead search and read its results once it is done. Access: read. REST: `GET /api/v1/findymail/lead-search`. MCP: `findymail_read → get_lead_search`. | Parameter | Type | Required | Description | |---|---|---|---| | `hash` | string | yes | Hash returned by start_lead_search. | | `page` | integer | no | Results page, starting at 1. | | `per_page` | integer | no | Rows per page, up to 500. | Returns the status first: pending, processing, success, failed or not_found. While it is processing, it adds progress and the counts of finished and pending jobs. When the status is success, it also returns the rows with company, domain, description, employee count range, industries, country, match score and the contact found, with page numbers. Checking the status and reading results are free. Example response: ```json { "hash": "f3b9a1c27d5e4086", "status": "success", "data": [ { "company_name": "Northwind Logistics", "domain": "northwind.com", "employee_count_range": "51-200", "industries": [ "Marketing services" ], "country": "DE", "match_score": 94, "contact_name": "Dana Whitfield", "contact_email": "dana@northwind.com", "contact_job_title": "Head of Growth" }, { "company_name": "Globex", "domain": "globex.co", "employee_count_range": "11-50", "industries": [ "Advertising" ], "country": "NL", "match_score": 88, "contact_name": "Luis Ortega", "contact_email": "luis@globex.co", "contact_job_title": "VP Marketing" } ], "meta": { "page": 1, "per_page": 100, "total": 200 } } ``` ### find_email Find the work email of a person from their name and a company domain. Access: read. REST: `GET /api/v1/findymail/emails/find`. MCP: `findymail_read → find_email`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | Full name of the person. | | `domain` | string | yes | Company domain, for example northwind.com. A company name also works, a domain is better. | Returns the contact with name, domain and email, or no contact when Findymail finds nothing. A found email costs 1 finder credit, and an empty result is free. It reaches nobody, so it does not wait for your OK. Example response: ```json { "contact": { "name": "Dana Whitfield", "domain": "northwind.com", "email": "dana@northwind.com" } } ``` ### verify_email Check whether an email address is deliverable. Access: read. REST: `GET /api/v1/findymail/emails/verify`. MCP: `findymail_read → verify_email`. | Parameter | Type | Required | Description | |---|---|---|---| | `email` | string | yes | Email address to check. | Returns the email, verified as true or false and the mail provider. Each check costs 1 verifier credit, whatever the result. It reaches nobody, so it does not wait for your OK. Example response: ```json { "email": "dana@northwind.com", "verified": true, "provider": "google" } ``` ### create_contact_list Create an empty contact list in Findymail. Access: write. REST: `POST /api/v1/findymail/contact-lists`. MCP: `findymail_write → create_contact_list`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | Name of the new list. | Returns the new list with its ID and dates. It changes only your own account and reaches nobody, so it does not wait for your OK. Example response: ```json { "list": { "id": 3140, "name": "Q1 outreach", "created_at": "2026-10-23T09:00:00Z", "updated_at": "2026-10-23T09:00:00Z", "shared_with_team": false, "is_owner": true } } ``` ### create_exclusion_list Create an exclusion list for Intellimatch searches. Access: write. REST: `POST /api/v1/findymail/exclusion-lists`. MCP: `findymail_write → create_exclusion_list`. | Parameter | Type | Required | Description | |---|---|---|---| | `name` | string | yes | List name, unique among your lists. | | `is_shared` | boolean | no | Share the list with your team. Needs a team account. | Returns the list with its ID, name, is_shared and is_owner. A name you already use fails with a 422 error, and sharing without a team fails with a 400 error. It reaches nobody, and the list can be deleted again, so it does not wait for your OK. Example response: ```json { "id": 1260, "name": "Competitors", "is_shared": false, "is_owner": true } ``` ### add_excluded_domains Add domains to an exclusion list, or to the global list. Access: write. REST: `POST /api/v1/findymail/excluded-domains`. MCP: `findymail_write → add_excluded_domains`. | Parameter | Type | Required | Description | |---|---|---|---| | `domains` | array | yes | Bare domains such as acme.io, up to 10,000 per call. | | `list_id` | integer | no | Exclusion list ID. Omit it to add to the global list. | Returns success, the total sent, how many were processed at once and how many were queued, with the list ID. Findymail processes the first 50 immediately and queues the rest in the background. It reaches nobody and the domains can be removed with remove_excluded_domains, so it does not wait for your OK. Example response: ```json { "success": true, "total": 3, "processed_immediately": 3, "queued": 0, "list_id": 1204 } ``` ### remove_excluded_domains Remove domains from an exclusion list by their IDs. Access: write. REST: `DELETE /api/v1/findymail/excluded-domains`. MCP: `findymail_write → remove_excluded_domains`. | Parameter | Type | Required | Description | |---|---|---|---| | `ids` | array | yes | Domain IDs from list_excluded_domains. | Returns success and the number of domains deleted. On a shared list you need the removeDomains permission, and a domain on the global list must be yours. It reaches nobody and the domains can be added again, so it does not wait for your OK. Example response: ```json { "success": true, "deleted_count": 1 } ``` ### delete_exclusion_list Delete one of your exclusion lists with all its domains. Access: write, asks the user first. REST: `DELETE /api/v1/findymail/lists/{list_id}/exclusion-lists`. MCP: `findymail_write → delete_exclusion_list`. | Parameter | Type | Required | Description | |---|---|---|---| | `list_id` | integer | yes | Exclusion list ID from list_exclusion_lists. | Returns success. Only the owner can delete a list, and the domains on it are deleted too, so searches that used it start returning those companies again. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "success": true } ``` ### start_lead_search Start an Intellimatch search for companies that match a description, with contacts if you ask for them. Access: write, asks the user first. REST: `POST /api/v1/findymail/lead-search/start`. MCP: `findymail_write → start_lead_search`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | yes | Plain-English description of your target companies. | | `limit` | integer | no | Companies to find, 100 by default, 5000 at most. | | `mode` | string | no | broad (default, includes adjacent companies) or targeted (fewer, more precise). | | `target_job_titles` | array | no | Up to 3 tiers of job titles in priority order, for example [["Head of Growth", "VP Marketing"]]. Default [["CEO"]]. | | `find_contact` | boolean | no | Find a contact at each company. | | `find_email` | boolean | no | Find the contact email. | | `find_phone` | boolean | no | Find the contact phone number. | | `require_email` | boolean | no | Keep only companies where an email was found. Needs find_contact and find_email. | | `exclusion_list_ids` | array | no | Exclusion list IDs to apply. 0 is the global list (default), -1 applies none. | Returns a hash. Pass it to get_lead_search to follow the search and read the rows. The search spends Findymail credits: 1 per 10 companies in broad mode or 1 per company in targeted mode, plus 1 per contact, 1 per email and 10 per phone found, charged when the export is generated. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "hash": "f3b9a1c27d5e4086" } ``` ## How do I connect Findymail to Claude Code, Codex or Cursor? Connecting Findymail takes three steps: sign up, sign in to Findymail once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect Findymail to your agent. 1. **Create an account** Sign up and add Findymail in the console. Your API key is there too. 2. **Sign in to Findymail in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Findymail there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the Findymail tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Add the domains of this month's new customers (acme.io, northwind.com, globex.co) to my Customers exclusion list in Findymail. Create the list if it does not exist, and skip domains that are already on it. ``` ### Call Findymail from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/findymail with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/findymail/excluded-domains \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"list_id":1204,"domains":["acme.io","northwind.com","globex.co"]}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "success": true, "total": 3, "processed_immediately": 3, "queued": 0, "list_id": 1204 } ``` ## Why use Cotlet for Findymail? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to Findymail yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When Findymail changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Findymail to Cotlet? Yes. You sign in to Findymail yourself, in your own Cloud Browser, and we never save your password. Your agents only get Findymail once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official Findymail integration?** No, Cotlet is independent of Findymail. Findymail's own API is too limited for this work. Cotlet works through your own Findymail account, the way you use Findymail in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to Findymail in your console: your agents lose access at once and you stay signed in. Signing out of Findymail in the browser works too, and Reset browser deletes the whole profile. ## Is there a Findymail MCP server on GitHub? Yes. Third-party Findymail MCP servers exist on GitHub, usually maintained by one person, and hosted ones take your API key too. You install one yourself, put your Findymail key in its config and fix it when the API changes. Cotlet hosts the same kind of server for you, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Clone the repo, install it, create an API key in Findymail, paste it into the config of each MCP client | Sign up, sign in to Findymail once, add one MCP server or API key | | When Findymail changes | It breaks or misses new endpoints until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free | | Your Findymail access | An API key in a config file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When access expires | Calls fail until you create a new key and update every config | Your Cloud Browser keeps you signed in; if Findymail logs you out, your agent gets a link to sign in again | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time; Findymail credits are used either way | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when Findymail changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the Findymail API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Findymail API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Findymail account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to Findymail yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Findymail only after you enable it. When Findymail signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to Findymail, sign out of Findymail in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **Findymail's terms:** You use your own Findymail account and stay responsible for following Findymail's terms. Cotlet is independent and not affiliated with Findymail. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open Findymail in the console and press Request access. Then you create your API key and connect Findymail there. **Do I need to be technical?** No. You sign in to Findymail once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect Findymail to Cotlet?** Yes. You sign in to Findymail yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Findymail once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My Findymail sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Findymail cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through Findymail's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Findymail sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no Findymail login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** Findymail offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Which Findymail plan do I need?** Findymail lists "API & MCP access" among what all plans include, and the API docs say a key comes from your account. On usage-based plans (Individual, Team, Scale) all seats share one usage pool across the app, extension, integrations and the API, and the free trial gives 10 credits with no card (checked 23 Oct 2026). **Does my agent use my Findymail credits?** Yes. Cotlet works in your own Findymail account, so finds, verifications and lead searches draw from your plan as they do in the app. A find is charged only when an email is found, and checking a lead search or reading its results is free. **Can my agent post or send messages in Findymail without asking me?** No. Every call to delete_exclusion_list or start_lead_search waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_contact_list, create_exclusion_list, add_excluded_domains and remove_excluded_domains run without asking, because they send nothing to anyone and one call undoes it. **Can I use the Findymail API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/findymail from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.