MisarReach MCP Server

by misar-ai Your server? Claim it

not responding

MisarReach MCP Server is listed as active in the registry but did not answer our last check. 266 installs a week from npm. It exposes 27 tools. Last commit 19 Aug 2026.

Find and enrich leads, run multi-channel outreach, and manage the sales pipeline.

Installs per day peak 519 · avg 49 · -72% w/w

a month agotoday

Uptime history 14 days of history · worst day 46%

14 days agonow

87.3%

Uptime 24h

69 of 79 checks

Tools

read from the server

643 ms

Response time

average over 24h

266

Installs / week

npm and PyPI

MisarReach MCP Server does not always answer

Over the last week it answered 85.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add misarreach-mcp --transport http https://api.misar.io/reach/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "misarreach-mcp": {
      "url": "https://api.misar.io/reach/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.misarreach-mcp]
url = "https://api.misar.io/reach/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "misarreach-mcp": {
      "url": "https://api.misar.io/reach/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "misarreach-mcp": {
      "url": "https://api.misar.io/reach/mcp"
    }
  }
}

Available tools 27

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

sales

get_sales_agent_actions

Get what the AI sales agent has done today, with summary stats — actions taken, deals created, replies sent. This is the audit trail: use it to see what the agent did on the account's behalf, and to sanity-check its behaviour after enabling it. Covers TODAY only, so it is not the tool for historical reporting. Reads only and changes nothing; it does not approve or undo any action. Requires an API key. No actions today is a normal answer, not an error.

get_sales_agent_config

Fetch the AI sales agent's current settings: whether it is enabled, its booking link, offer price, reply limits and confidence threshold. Read this before update_sales_agent_config so you change one field without clobbering the rest, and to check whether the agent is enabled at all before expecting it to act. Reads only, takes no parameters, changes nothing. Requires an API key. Returns the configuration for the authenticated account.

update_sales_agent_config

Change the AI sales agent's settings — enable or disable it, set the booking link, offer price, reply limits and confidence threshold. These settings govern an agent that replies to real prospects, so treat them as live: ENABLING it lets it start responding on its own, the confidence threshold decides how sure it must be before acting, and reply limits cap how much it can send. Read the current config first — only the fields you pass change, but a wrong value takes effect immediately. Safe to repeat. Requires an API key.

autopilot

get_autopilot_status

Get the current progress and results of one autopilot run. This is how you follow a run started by start_autopilot: call it with the runId, leaving time between polls. Reading status does not pause, stop, or alter the run in any way — it keeps going regardless, and there is no tool here to stop it. Reads only and costs no credits, however often you call it. Requires an API key. A run still in progress is a normal answer, not an error.

list_autopilot_runs

List past and running autopilot runs with their status and result summaries. Use it to review what has already been run — and to check for a run already in flight before start_autopilot launches a second one against the same goal. For detail on one run, use get_autopilot_status. Reads only, costs no credits, and starts nothing. Requires an API key. Returns runs newest first with paging.

deal

create_deal

Open a new deal against a lead's email address. Use it when a conversation turns into a real opportunity worth tracking. Each call creates a NEW deal — it does not check for an existing one on the same email, so list_deals first if you might be duplicating. To change a deal that exists, use update_deal. Requires an API key. `value` is in MINOR CURRENCY UNITS — 2500 means $25.00, not $2500 — and defaults to 0 with currency USD. Returns the created deal, which enters the pipeline at the first stage.

update_deal

Change a deal's status, value, or notes. Only the fields you pass are altered. For moving a deal along the pipeline board prefer move_deal_stage, which is the same operation expressed in stage terms; use this one for value and notes. Setting status to 'closed' or 'lost' marks the deal resolved and takes it out of open pipeline revenue. Safe to repeat — the same call twice leaves the same deal. Requires an API key, and the account must own the deal. `value` is in MINOR CURRENCY UNITS (2500 = $25.00). Notes REPLACE the existing note rather than appending.

lead

create_lead_list

Create a new, empty lead list in Hunter.io. Creating the list does not put anything in it, and it does not import anything locally — sync_lead_list does that. Call list_lead_lists first: each call creates a NEW list and nothing deduplicates by name. Requires an API key and a connected Hunter.io account. Costs no credits. Returns the created list with the id that sync_lead_list needs.

list_lead_lists

List the Hunter.io lead lists connected to this account. Use it to find a listId before sync_lead_list, or to check whether a list already exists before create_lead_list makes a duplicate. These are Hunter.io's lists, which are separate from the leads stored locally — list_leads shows those. Reads only, costs no credits, takes no parameters. Requires an API key and a connected Hunter.io account. An empty result means no lists exist yet.

leads

list_leads

List leads already saved to the account, newest first, with paging and search. Use this to work with leads you already have. It does NOT find new ones — that is search_leads, which starts a job and costs credits. Narrow to one search job with job_id when you want just that job's results. Reads only and costs no credits. Requires an API key. Returns saved lead records with contact and company fields plus enrichment and score where present. An empty page is a normal answer, not an error.

search_leads

Start an AI lead-search job and return its jobId immediately. This is ASYNCHRONOUS: results are not in the response. Poll get_search_job_status with the jobId until it reports completion, then read the leads with list_leads filtered by that job_id. Use it to find NEW leads; use list_leads for ones already saved. CONSUMES SEARCH CREDITS on every call, and each call starts a separate job — do not retry it as a way to check progress. Requires an API key. Setting useAI additionally spends AI credits to enrich and score the results as they arrive.

channel

update_channel

Turn one outreach channel on or off — WhatsApp, SMS or push. This changes how the account actually delivers messages, so it affects live campaigns and autopilot runs, not just future ones. DISABLING a channel silently stops delivery over it; enabling one that has no credentials configured will not make it work. Call get_channels_status first to see where things stand. Handles one channel per call. Safe to repeat: setting a channel to the state it is already in changes nothing. Requires an API key.

channels

get_channels_status

Report the configuration, connection state and delivery stats for every outreach channel — WhatsApp, SMS and push. Check this before relying on a channel: a disabled or unconfigured one silently delivers nothing. It is also the natural first step before update_channel, so you know the current state rather than toggling blind. Reads only, takes no parameters, and changes nothing. Requires an API key. Returns each channel with whether it is enabled, whether credentials are configured, and recent delivery counts.

deals

list_deals

List deals as a flat, paged array, optionally filtered by status, with revenue totals alongside. Use this when you want deals as data — to count them, filter one status, or page through many. For the board view with deals grouped into stages, use get_pipeline instead; the two return the same deals in different shapes. Reads only. Requires an API key. Returns the deals plus a summary of total, closed and open pipeline revenue. Money is in minor currency units (cents), so divide by 100 before showing it.

discover

discover_companies

Find COMPANIES matching firmographic criteria via Hunter.io, optionally pulling contact emails for each. This is company-level discovery — reach for it when the user is targeting organisations by industry, location, headcount or tech stack. When they want named people, use search_leads. Filters combine with AND, so stacking many narrows results sharply. Requires an API key. Setting fetch_emails=true performs email lookups and COSTS CREDITS; leaving it false is a plain company search. Returns matching companies with firmographics. No lead is saved to the account by this call.

enrich

enrich_lead

Fill in a saved lead's missing person and company detail — seniority, department, LinkedIn, phone, company size, industry. Use it on one lead at a time, after list_leads has given you its id, and typically before writing outreach that needs context. Check the lead first: enriching one that already has these fields spends credits for nothing. CONSUMES ENRICHMENT CREDITS per call. Requires an API key. Updates the stored lead in place and returns it; it does not create a new record, and running it twice does not duplicate the lead — but it does bill twice.

job

get_search_job_status

Poll one lead-search job for its progress and results. This is the companion to search_leads: call it repeatedly with the jobId you were given until the job reports it has finished. Leave a few seconds between polls — searches take a while, and polling harder does not make them faster. Reads only and costs no credits, however many times you call it. Requires an API key. Returns the run state, progress, and the leads found so far; a job still running is a normal answer, not an error.

move

move_deal_stage

Move one deal to a different pipeline stage — the equivalent of dragging its card on the board. This is the tool for pipeline progression; update_deal is for value and notes. Moving to 'closed' or 'lost' resolves the deal and removes it from open pipeline revenue, which changes reported figures — only do it when the user says the outcome is settled. Safe to repeat: moving a deal to the stage it is already in changes nothing. Stages are not ordered by this call, so it can move a deal backwards as easily as forwards. Requires an API key.

pipeline

get_pipeline

Get the sales pipeline as a board: deals grouped by stage, with revenue totals. Use this for 'how does the pipeline look' questions and stage-by-stage review. It is the board view of the same deals list_deals returns flat — reach for that one when you need filtering or paging, since this returns the whole board. Reads only. Requires an API key. Stages are new, contacted, interested, meeting, proposal, closed and lost. Money is in minor currency units (cents), so divide by 100 before showing it.

preview

preview_message

Draft a sample AI-personalised outreach message for a named person, to show what the agent would say. This is a PREVIEW: nothing is sent, saved, or attached to a lead or campaign. Use it to check tone before committing to a sequence. The person does not need to exist as a lead — pass their name and, if known, role and company. This is the one tool here that needs no API key. Generative, so the same input yields different wording each time. Returns the drafted message text.

process

process_sales_agent

Run the sales-agent pipeline over one conversation: decide the next action and carry it out. This ACTS on a real conversation — depending on what it decides, it can reply to the prospect, create a deal, or book a meeting. It is not a dry run and there is no preview, so call it only when the user wants the agent to take its turn on that specific conversation. For what it has already done, use get_sales_agent_actions. CONSUMES AI CREDITS. Not idempotent: calling twice processes the conversation twice and can send two messages. Requires an API key, and the agent's configured confidence threshold still governs whether it acts.

score

score_leads

Queue AI qualification scoring for leads — either every unscored lead in a search job, or a specific set of ids. Pass jobId OR leadIds, not both. This runs in the BACKGROUND: it returns a count immediately and the scores appear on the leads afterwards, so re-read them with list_leads rather than expecting scores in this response. CONSUMES AI CREDITS per lead scored. Requires an API key. Passing leadIds rescores leads even if they already have a score, which bills again — pass jobId to score only what is unscored. Caps at 200 ids per call.

send

send_to_campaign

Add saved leads to a campaign's contact list in bulk, up to 500 at a time. This is how leads enter an outreach sequence, so treat it as consequential: once they are on a running campaign's list they can start receiving messages. It does NOT send anything by itself and does not start the campaign — but it removes the last step before the campaign does. Every lead must belong to the authenticated account, or the call fails. Adding a lead already on the list does not duplicate it. Requires an API key. Verify addresses with verify_emails first; importing dead ones damages sender reputation.

start

start_autopilot

Start an autonomous outreach run: give the agent a goal and it finds, contacts and follows up with leads on its own. This is the most consequential tool on this server. It is FIRE-AND-FORGET and it SENDS REAL MESSAGES TO REAL PEOPLE without returning for approval, so only start a run when the user has explicitly asked for one and understands the goal as written — the goal text is the entire brief. It returns a runId immediately; watch progress with get_autopilot_status. CONSUMES AUTOPILOT CREDITS, plus search, enrichment and AI credits as it works. Requires an API key. Each call starts a SEPARATE run — calling twice runs two campaigns concurrently against the same goal.

submit

submit_lead_feedback

Record whether an AI-generated outreach message for a lead was good or bad, as training signal for future generations. Use it when the user judges a drafted message — it improves later output rather than changing anything now. It does not edit, resend, or delete the message, and it sends nothing to the lead. Writes a feedback record; sending the same verdict twice is harmless. Requires an API key. Costs no credits.

sync

sync_lead_list

Import a Hunter.io lead list into local lead records so the rest of these tools can work with it. Run it after create_lead_list, or on any existing list from list_lead_lists, to pull its contacts in. Until a list is synced its contacts are invisible to list_leads, enrich_lead and send_to_campaign. Writes local lead records. Re-syncing the same list refreshes rather than duplicating, so it is safe to repeat. Requires an API key and a connected Hunter.io account. Costs no credits; enrichment and verification are billed separately.

verify

verify_emails

Check whether email addresses are deliverable, one or up to 20 at a time. Run this before a send to protect sender reputation — bouncing a campaign off dead addresses is what gets a domain blocked. Pass either `email` for one or `emails` for a batch, not both. CONSUMES VERIFICATION CREDITS per address checked, so a 20-address batch costs 20. Requires an API key. Returns a deliverability verdict per address; 'undeliverable' is a successful result, not an error. Nothing is sent to the addresses.

Endpoints

URL	Transport	State	Latency	Checked
https://api.misar.io/reach/mcp	streamable-http	answering	696 ms	11 min ago

Alternatives to MisarReach MCP Server

same job, measured the same way

Twist

by pulsemcp

MCP server for Twist team messaging — manage channels, threads, and messages.

97 installs/wk local only

Apollo.io

by apolloio

Prospect, enrich leads, and manage outreach sequences with Apollo.io.

answering

Coalesce Transform

by jessemarshall

MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

235 installs/wk local only

Coalesce Transform

by coalesce-software-inc

MCP server for managing Coalesce Transform workspaces, nodes, pipelines, and runs.

local only

Salesforce Marketing

by zleventer

MCP server for Salesforce — 47 tools for leads, campaigns, pipeline, attribution, and reporting.

36 installs/wk local only

Chatflow

by yersat

WhatsApp CRM for AI agents: search contacts, read chats, manage the sales pipeline, send messages.

answering

Slack

by mindstone

Slack MCP server: channels, messages, threads, reactions, users, files, and scheduled messages

94 installs/wk local only

Outreach

by mindstone

Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings

36 installs/wk local only

MisarReach MCP Server — questions

Answers built from our own checks of this server.

What can MisarReach MCP Server do?

It exposes 27 tools, read directly from the server on our last check. Among them: create_deal, create_lead_list, discover_companies, enrich_lead, get_autopilot_status, get_channels_status and 21 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is MisarReach MCP Server mostly used for?

Its tools cluster around sales, leads and autopilot. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is MisarReach MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 69 of 79 checks got a reply (87.3%), average response time 643 ms. The bar chart above shows every period we have measured.

The registry lists MisarReach MCP Server as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect MisarReach MCP Server?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MisarReach MCP Server need an API key?

No. MisarReach MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 27 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MisarReach MCP Server?

It answers our handshake in 643 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use MisarReach MCP Server?

The npm package @misarreach/mcp was installed 266 times in the last week. Week over week that is -72%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is MisarReach MCP Server open source?

Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.