List your agent

Emailchaser

MCP server● Hosted · onlinev1.0.1

Run cold email outbound from an AI agent: campaigns, leads, replies, sender accounts, autopilot

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: find leads.
All AI agents to find leads, ranked →

Similar tools

Listed for the same task: find leads

Reviews

No review yet. Used Emailchaser? Be the first to help others choose.

What it does

Emailchaser is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to 2 capabilities: lead generation and outreach sequencing. That makes it a candidate for tasks such as find leads or find B2B partners.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.1
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://app.emailchaser.com/api/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "emailchaser": {
      "url": "https://app.emailchaser.com/api/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Emailchaser answered an MCP connection on 16 Nov 2026 and introduced itself as emailchaser 1.0.0 (MCP protocol 2025-06-18).

102 tools offered to AI assistants

  • confirm_connection · Confirms the API key works and tells Emailchaser which AI assistant connected. Use it when the user connects Emailchaser or asks to confirm or check the Emailchaser connection: it records the assistant and time on the key, which the app's A
  • list_campaigns · Lists cold email campaigns in the workspace with their status and stats (sent, replies, bounces). Supports pagination and filtering by status or folder.
  • create_campaign · Creates a campaign in the workspace. The campaign starts as a DRAFT and sends nothing. A new campaign has no emails in it, so it cannot be launched until it has a sequence and a sender email attached. Sending limits and deliverability setti
  • get_campaign · Retrieves a campaign by ID, including settings, sending schedule, stats and per-status email counts. minimumHealth lists each connected email account on the campaign with its healthScore and whether the campaign's minimum health score (sett
  • update_campaign · Updates campaign properties such as name, emoji, timezone, sending limits, the minimum email account health score and deliverability settings. Only the provided fields are changed. A new minimum health score re-plans a running campaign at o
  • launch_campaign · Launches a new campaign or resumes a paused one. The campaign configuration is validated before launching; emails start sending per the campaign schedule.
  • pause_campaign · Pauses a running campaign and cancels all currently scheduled emails.
  • update_campaign_schedule · Updates a campaign's sending schedule: timezone, sending days, daily time window and frequency. everySchedule can be left out: the campaign keeps its current frequency, or 5 minutes (the app's default) if it has none.
  • get_campaign_sequence · Returns the ordered emails that make up a campaign's sequence, including any A/B variants. delayDays on each step is counted from the previous step, and the first step is always 0.
  • replace_campaign_sequence · Replaces a campaign's WHOLE sequence with the steps provided. This is not a partial edit: steps you leave out are removed, so send the full sequence every time. Sending the same payload twice leaves the same result, so a retry cannot duplic
  • delete_campaign · Permanently deletes a campaign and all associated data, including its emails, sequences and scheduled tasks. This cannot be undone.
  • get_campaign_stats · Returns a campaign's performance in one call: totals (sent, replied, positive, bounced, meetings), per-A/B-variant results, per-sequence-step results and a daily time series (UTC days). Use it to judge how a campaign is doing or to compare
Show 88 more
  • attach_campaign_sender_emails · Attaches connected sender email accounts to a campaign. A campaign only sends through the senders attached to it, so this call decides which mailboxes it uses. Idempotent: already-attached senders are left untouched and only missing ones ar
  • detach_campaign_sender_email · Detaches a sender email from a campaign so the campaign stops sending through that mailbox. Unsent follow-ups to emails this sender already sent are canceled and do not come back on re-attach; a running campaign is rescheduled onto its rema
  • move_lead_to_campaign · Moves a lead from one campaign to another: the lead's unsent emails in the source campaign are deleted, and if the target campaign is running, emails for the lead are enqueued there. Use it to re-route a lead into a better-fitting campaign.
  • list_leads · Lists the leads in the workspace, newest first, 20 per page. Filter by exact email to look up a single lead, or by campaign to list only that campaign's leads. This is how you find the ID of a lead you added earlier.
  • add_leads · Creates or updates up to 1,000 leads in one request, optionally adding them to a campaign via campaignId. Existing leads (matched by email) are updated instead of duplicated. Returns the id of every lead written, so they can be fetched or u
  • get_lead · Retrieves a lead by ID, including contact details and company information.
  • update_lead · Updates a lead's contact details. Only the provided fields are changed.
  • delete_lead · Permanently deletes a lead by ID. This cannot be undone.
  • get_lead_conversation · Returns a lead's full email thread in chronological order: outbound emails (sent, scheduled and unsent drafts) plus inbound replies, each with direction and status. AI reply drafts awaiting review are marked isDraft. Every inbound reply in
  • mark_lead_meeting · Records that a meeting was actually booked with this lead: sets meetingBookedAt to now, sets the lead's category to meeting_booked and fires the LeadCategoryUpdate webhook. Emailchaser never infers meetings from reply text or calendars, so
  • unmark_lead_meeting · Removes the booked-meeting mark from a lead, e.g. when it was recorded by mistake or the meeting was canceled: clears meetingBookedAt and, when the category is still meeting_booked, reverts it to interested. The original booked time is lost
  • update_lead_category · Sets or corrects a lead's category (tag), typically to fix an AI misclassification of a reply. Setting meeting_booked behaves exactly like marking a meeting as booked. Changing the category away from meeting_booked does NOT clear the booked
  • list_replies · Lists inbound emails (replies received from prospects) in the workspace, newest first, 20 per page. Filter by AI response category, campaign, lead or a time floor. responseCategory is null while AI categorization is still pending. This tool
  • list_reply_drafts · Lists AI-suggested reply drafts awaiting review, newest first, 20 per page. Each draft answers the inbound reply referenced by inReplyToEmailId. Nothing here has been sent: a draft stays a draft until it is sent. A draft's subject and body
  • update_reply_draft · Edits the subject and/or body of an AI reply draft before it goes out. Provide at least one field; provided fields must be non-empty. This never changes the draft's status or sends anything: the draft stays a draft until it is sent. Emails
  • send_reply_draft · Sends an AI reply draft to the prospect through the conversation's sender mailbox; it is scheduled for delivery right away and cannot be recalled. The draft's CURRENT subject and body are what goes out, so check its wording before sending:
  • send_reply · Answers an inbound reply with your own message, in the same email thread and from the mailbox the conversation runs through (in a conversation the prospect started, your mailbox they wrote to). It works for every inbound reply, including th
  • list_sender_emails · Lists the sending email accounts in the workspace, 20 per page, with their connection status, daily limits and health score. Filter to one campaign's senders, to connected or disconnected mailboxes only, or to one workspace on the account.
  • get_sender_email · Retrieves a connected sending email account by ID, including its health score. healthScore is the account's health score: 0-100, higher is better, the share of its warm-up emails over the last 7 full days that landed in the inbox rather tha
  • connect_sender_email · Connects an SMTP/IMAP mailbox to the workspace using an app password, with no browser step. Google and Microsoft mailboxes are NOT supported here because both require an interactive consent screen that cannot be automated; connect those in
  • update_sender_email · Updates a connected sending email account's display name, signature or daily sending limits. Only the provided fields are changed. Warm-up settings are separate and are not changed here. The returned account includes its healthScore (0-100,
  • get_sender_email_dns · Checks the sender domain's SPF, DKIM, DMARC and MX records and reports each as OK, WARNING, MISSING or ERROR with human-readable issues (the same checks behind the app's DNS vitals view), plus the mailbox's warm-up status: whether it is enr
  • get_sender_email_warmup · Reads a mailbox's warm-up settings: whether warm-up is on, the ramp (startLimit warm-up emails on the first day, increaseBy more each sending day, up to capLimit a day), weekdays-only, timezone, today's ramp target (currentPerDay) and the a
  • update_sender_email_warmup · Switches warm-up on or off and changes the warm-up ramp for up to 100 mailboxes in one call, applying the same settings to each. Only the settings provided change. Warm-up sends startLimit emails on the first day and adds increaseBy each se
  • list_inbox_placement_tests · Lists every inbox placement test defined in the workspace, newest first. A test is the definition: the email content, which mailboxes send it and, for a recurring test, how often it runs. Each execution of a test is a run. Inbox placement i
  • list_inbox_placement_runs · Lists inbox placement runs, newest first, optionally only those of one test. Each run counts how many probe emails landed in the inbox, in spam, in a Gmail category tab (promotions) or nowhere (missing, which usually means a silent block).
  • get_inbox_placement_run · Returns one inbox placement run with its complete report: the headline inbox / spam / promotions / missing split, the breakdown per mailbox provider and per sending mailbox, and the content spam rules the copy triggered. 'Promotions' rolls
  • list_inbox_placement_run_results · Returns one row per probe email of a run: which of your mailboxes sent it, which seed mailbox received it, where it landed and how many seconds it took to arrive. deliverySeconds is worth watching on its own: greylisting and throttling show
  • get_inbox_placement_stats_by_date · Rolls completed inbox placement runs up by UTC calendar day over a window, for a trend. Defaults to the last 30 days. Days on which nothing ran are ABSENT from the series rather than zero: never report a missing day as 0% placement, it mean
  • get_sender_reputation · Returns the latest health check for every connected mailbox: SPF, DKIM, DMARC and MX status (OK, WARNING, MISSING or ERROR), blacklist listings with their delisting links, measured inbox placement over recent runs and a combined 0-100 healt
  • get_deliverability_insights · What is wrong with deliverability across the workspace right now, worst first, each with the action that fixes it. Combines the inbox placement measured over the window with the latest health check of every connected mailbox: authentication
  • list_webhooks · Lists the webhook endpoints registered for the workspace, with their event type and status.
  • create_webhook · Registers a webhook endpoint that receives a POST request whenever the selected event happens (email sent, reply received, bounce, lead created, lead category updated, or campaign status changed). API reference: https://www.emailchaser.com/
  • update_webhook · Updates a registered webhook's name, URL, event type or enabled state. Only the provided fields are changed. Disabling a webhook stops deliveries without deleting it. API reference: https://www.emailchaser.com/docs/api-reference/webhooks
  • delete_webhook · Deletes a registered webhook endpoint by ID so it stops receiving events.
  • list_blocklist_entries · Returns the suppression entries (blocked domains and email addresses) that apply to this workspace, newest first. Blocked entries are never emailed by any campaign. By default that spans both lists: this workspace's own entries and the acco
  • add_blocklist_entries · Adds up to 1,000 suppression entries in one call so no campaign ever emails them. Each value is either a full email address (contains @) or a bare domain; the type is inferred per value. Existing entries and invalid values are skipped, so t
  • remove_blocklist_entries · Unblocks up to 1,000 domains or email addresses in one call, so campaigns can email them again. Pass values (domains or addresses, matched case-insensitively) and/or ids (blocklist entry IDs); a value that is not blocked is counted as skipp
  • get_blocklist_entry · Returns one suppression entry by ID: the blocked domain or email address, when it was added and which list it belongs to. Entries inherited from the account-wide list are visible from a sub-workspace too and report scope "global".
  • update_blocklist_entry · Changes one suppression entry's blocked value, its scope, or both; provide at least one. A value containing @ is stored as an email address, otherwise as a domain, so an entry can be converted between the two. Moving an entry to or from the
  • remove_blocklist_entry · Removes one suppression entry by ID, so campaigns can email that domain or address again. This cannot be undone: the entry and the record of when it was added are gone. A sub-workspace key cannot remove an account-wide entry it merely inher
  • import_instantly · Imports your Instantly.ai campaigns and leads into Emailchaser using your Instantly API key. Imported campaigns are created as DRAFTS — nothing sends until you review and launch them. Runs in the background and returns a job id.
  • list_instantly_accounts · Fetches the sending accounts of an Instantly.ai workspace using your Instantly API key, together with a pre-filled CSV for Emailchaser's bulk IMAP/SMTP connection flow. A read-only preview before an import: nothing is written to the workspa
  • copilot_plan · Given a company website, the honest AI SDR builds an ideal-customer-profile (ICP) and a suggested cold-email sequence. Read-only — creates nothing. Returns the ICP (personas, titles, industries, suggested Sales Navigator keywords) and a dra
  • copilot_launch · Creates a DRAFT campaign from a sequence. With a LinkedIn Sales Navigator search it also starts finding + verifying leads for it; without one the draft holds the emails and leads can be added from Lead Finder or a CSV upload. Nothing sends
  • create_icp · Stores a manually-authored Ideal Customer Profile (ICP): who the workspace sells to, as targeting criteria (titles, seniorities, industries, company sizes, locations, keywords). Set makePrimary to promote it to the workspace's active profil
  • list_icps · Lists the workspace's stored Ideal Customer Profiles (ICPs), newest first, with their targeting criteria, whether each is AI-generated or human-edited, and the estimated audience size.
  • get_primary_icp · Returns the workspace's active (primary) Ideal Customer Profile — the profile the workspace currently targets; at most one is primary. Errors with 404 when none is set.
  • get_icp · Retrieves one Ideal Customer Profile by ID, including its targeting criteria, whether it is AI-generated or human-edited, primary status and estimated audience size.
  • update_icp · Applies a partial edit to an Ideal Customer Profile: omitted fields are left unchanged, and sending an empty list clears that list. Any edit marks the profile as human-authored.
  • delete_icp · Deletes an Ideal Customer Profile. Deleting the primary leaves the workspace without an active profile. This cannot be undone.
  • set_primary_icp · Promotes an Ideal Customer Profile to the workspace's active one, demoting any existing primary. At most one profile is primary per workspace.
  • refresh_icp_audience_size · Re-counts how many prospects match an ICP's targeting criteria against the live data provider and caches the result on the profile. Sizing is free — it never spends credits; only revealing contact details is metered.
  • get_audience_size · Counts how many prospects match ad-hoc targeting criteria (titles, seniorities, industries, company sizes, locations, keywords) without saving anything. Free — searching never spends credits; only revealing contact details is metered. Use i
  • source_prospects · SPENDS CREDITS. Queues a background job that searches Emailchaser's contact database with an Ideal Customer Profile's targeting criteria, reveals the matching people and adds them to the campaign as leads. Uses the workspace's primary ICP w
  • get_lead_finder_filters · Returns the values Lead Finder's list filters accept (seniorities, jobFunctions, companySizes, revenue, industries, countries, headquartersCountries, regions, continents), the limits that apply to this workspace (page sizes, deepest page, p
  • search_lead_finder · Searches Emailchaser's B2B contact database (Lead Finder) with explicit filters and returns one page of matching people, masked: first name, last initial, title, seniority, job function, company name, industry, size and revenue band, and lo
  • get_lead_finder_search · Reads a Lead Finder search again by its searchId, the id returned when the search was run. While it is still running, or while its exact total is still being counted (totalStatus pending), the call waits up to about six seconds, so calling
  • add_lead_finder_prospects · SPENDS CREDITS, AND BY DEFAULT METERED EMAIL VERIFICATION. Adds people from the Lead Finder contact database to a campaign as leads, revealing their contact details, in the background. Pass refs (from Lead Finder search results; up to 1,000
  • list_lead_finder_imports · Lists the workspace's Lead Finder adds (people added to campaigns from the contact database), newest first, each with its progress: requested, added, skipped and why, what email verification said, and credits spent.
  • get_lead_finder_import · Returns one Lead Finder add's progress: status (running, completed, failed or canceled), how many people were added and skipped and why (skipReasons), what email verification said, and credits spent. added, creditsSpent and status can still
  • cancel_lead_finder_import · Stops a running Lead Finder add. It reads canceled at once. A batch the worker is already writing is still added and charged; a batch still being screened or verified is dropped, though verification checks already made are billed. Credits h
  • plan_autopilot · Turns a monthly budget in dollars into a concrete outbound setup: how many domains and mailboxes it buys, monthly sending volume, prospects per month, and costs (one-off setup, recurring, first month). creditsUsd, recurringUsd and firstMont
  • start_autopilot_run · Starts an autopilot run for a company website: the AI builds an ICP, writes a sequence and checks that prospects match, then STOPS at an approval gate. Nothing is revealed, charged or sent and no sending accounts are bought until the run is
  • list_autopilot_runs · Lists the workspace's autopilot runs, newest first, with status (pending, building_icp, writing_sequence, sourcing_prospects, awaiting_approval, running, paused, completed, failed) and linked ICP/campaign IDs.
  • get_autopilot_run · Returns one autopilot run including its full audit trail. It does not return the budget plan: that is returned only in the response that started the run, when budgetUsd was given. Use it to check progress.
  • approve_autopilot_run · Approves an autopilot run that is awaiting approval — the one human gate in the flow. CAN SPEND REAL MONEY: approval first reveals the run's prospects at 1 credit ($0.033 at list) each, then, if the workspace has no connected sending accoun
  • pause_autopilot_run · Suspends an autopilot run that is still in flight; a paused run can be resumed later. Pausing never skips the approval gate. A completed or failed run cannot be paused.
  • resume_autopilot_run · Resumes a paused autopilot run. A run paused before approval goes back to awaiting approval — resuming can never skip the gate. A failed run resumes from the stage it failed at once the cause (e.g. insufficient credits) is fixed.
  • kill_autopilot_run · Engages the kill switch: the run halts wherever it is and can NEVER be resumed, and any campaign the run launched is paused so nothing more sends. A paused run can be resumed later; a killed one cannot. The optional reason is recorded in th
  • get_credit_balance · Returns the workspace's credit wallet: available, reserved, lifetime granted and used, and the monthly grant. Credits pay for prospect reveals and AI work (list price $0.033 each). A new workspace sees zeros, not an error. unlimited is true
  • list_credit_transactions · Lists the workspace's credit ledger, newest first: every grant, spend, reservation and refund with the balance after each entry. Filter by movement kind, reason or a time window. Use it to see where credits went, or to check for a stripe_to
  • purchase_credits · SPENDS REAL MONEY. Immediately charges the workspace's saved default card (the one behind the active subscription), off-session, with no confirmation step beyond this call — every successful call is a new charge. Buys 1,000 to 10,000 prospe
  • get_outcomes_report · Puts money against results for a time window: credit spend (grouped by reason, valued at the $0.033 list price) plus done-for-you order costs on one side, and sent emails, replies, positive replies and booked meetings on the other, with cos
  • search_dfy_domains · Checks availability and pricing of sending domains derived from a brand name (e.g. 'acme' yields acme-mail.com and similar). Only .com and .org are supported. Free to call. Returns the exact price of each available domain.
  • create_dfy_order · SPENDS REAL MONEY. Places a real order for sending domains and pre-warmed mailboxes: domains are registered at their listed price (about $13.99/year for a .com; each domain has its own listed price) and each mailbox costs about $3 setup plu
  • list_dfy_orders · Lists the workspace's done-for-you orders, newest first, each with status, cost breakdown and the ordered domains and mailboxes. Internal billing and provider records are never exposed.
  • get_dfy_order · Returns one done-for-you order: status (created, pending_approval, processing, completed, failed, partially_completed, canceled), cost breakdown and any failure reason. Use it to track an order's provisioning.
  • get_workspace_details · Returns the workspace behind the API key: campaign counts broken down by status and the list of members. Useful as a first call to confirm which workspace a key belongs to.
  • list_workspaces · Lists the workspaces owned by the account behind the API key: the main workspace and its sub-workspaces, each with id, name, icon and creation date. isCurrent marks the workspace this key is bound to. Every other tool acts on the current wo
  • create_workspace · Creates a sub-workspace under the account's main workspace (for example one per client, for an agency) and by default mints a read & write API key bound to it. The key's fullKey is returned exactly ONCE and cannot be retrieved again, so han
  • create_workspace_api_key · Mints a new API key bound to a workspace the calling key already owns: its own workspace, or one of its sub-workspaces when called with the main workspace's key. This is how a workspace whose key was lost gets a new one without a UI step. f
  • get_billing_profile · Returns the registrant and postal contact details held for the workspace: what is filed with the registrar when a done-for-you order buys a domain, and the postal address a CAN-SPAM footer must carry. Errors with 404 until the profile has b
  • set_billing_profile · Creates or replaces the workspace's registrant and postal contact details. Domain registration files these details with the registrar, so every field except addressLineTwo is required; a done-for-you order uses them when it registers domain
  • get_email_verification_rates · Returns what one email verification costs right now, read from the billing plan the meter actually charges against. The price is read live, never a fixed figure. Every check runs a waterfall of up to two providers and each one that returns
  • create_email_verification_job · SPENDS MONEY: every address checked adds metered usage to the workspace's next invoice. This does NOT use prospect credits and it does NOT create or send a campaign — it verifies a list on its own and gives back a per-address verdict you ca
  • list_email_verification_jobs · Lists the workspace's standalone email verification jobs, newest first, with live counts and what each has billed so far (meterEvents and spentUsd).
  • get_email_verification_job · Returns one verification job: its state, per-verdict counts and what it has billed. Poll until state is done. An errorCode of monthly_limit_reached means the allowance ran out and the remaining addresses came back unknown rather than missin

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://app.emailchaser.com/api/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://www.emailchaser.com/mcp-serverDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.0.1DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Emailchaser? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor EmailchaserLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Emailchaser?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/emailchaser?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/emailchaser/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Emailchaser

How do I connect Emailchaser?

Use the hosted endpoint https://app.emailchaser.com/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Emailchaser need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Emailchaser offer?

When Electra Index connected on 16 Nov 2026, it listed 102 tools: confirm_connection, list_campaigns, create_campaign, get_campaign, update_campaign, launch_campaign, pause_campaign, update_campaign_schedule and more. The full list is in "Live check" above.

Is Emailchaser online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use Emailchaser for?

Based on its description, it is most relevant to: find leads, find B2B partners, send personalized outreach, recruit developers.