MisarReach MCP Server

Name: MisarReach MCP Server
Author: Misar-AI

MCP serverMCP

Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…

by Misar-AIrepository ↗homepage ↗v5.2.1MIT

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability713/716 checks ok

Tools observed via MCP handshake

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
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
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 r
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 m
discover_companies — Find COMPANIES matching firmographic criteria, optionally pulling contact emails for each. This is company-level discovery — reach for it when the user is tar
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
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 a
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
list_lead_lists — List the managed lead lists this account has created or synced. Use it to find a listId before sync_lead_list, or to check whether a list already exists befor
create_lead_list — Create a new, empty managed lead list. Creating the list does not put anything in it, and it does not import anything locally — sync_lead_list does that. Call
sync_lead_list — Import a managed 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 li
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 t
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 th
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
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 doe
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
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.
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
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 th
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 fl
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 betwe
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 d
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 autopil
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 upd
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 a
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 a
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,
search_verified_leads — Find people or businesses matching a plain-language description and return only leads with a real way to reach them (email, phone or LinkedIn), each read from a
reveal_company_contacts — Read a company's own website now and return what it publishes: contact emails, a phone number, its social profiles and its detected tech stack. robots.txt is ob
company_email_format — The email address format a company uses (e.g. {first}.{last}@acme.com), learned only from addresses that were verified deliverable, with each pattern's share an
verify_email — Check whether one email address can receive mail. Returns valid, invalid, accept_all (a catch-all domain: the server accepts every address, so this one cannot b

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.Misar-AI/misarreach-mcp

first seen 2 mo ago · fetched 2 d agoopen ↗

npm registry@misarreach/mcp

first seen 2 mo ago · fetched 3 h agoopen ↗

Field history (12 recent events)

2 d ago · declared · version → "5.2.1"
2 d ago · declared · description → "Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…"
2 d ago · declared · summary → "Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…"
4 d ago · observed · packageFacts → {"name":"@misarreach/mcp","registry":"npm","publishedAt":"2026-10-17T05:18:54.048Z","latestVersion":"5.2.1","weeklyDownl
13 d ago · observed · packageFacts → {"name":"@misarreach/mcp","registry":"npm","publishedAt":"2026-10-07T18:29:36.870Z","latestVersion":"5.2.0","weeklyDownl
1 mo ago · claimed · ownership → {"method":"dns_txt","target":"www.misarreach.com"}
2 mo ago · declared · summary → "Find and enrich leads, run multi-channel outreach, and manage the sales pipeline."
2 mo ago · declared · name → "MisarReach MCP Server"
2 mo ago · declared · description → "Find and enrich leads, run multi-channel outreach, and manage the sales pipeline."
2 mo ago · declared · publisherName → "Misar-AI"
2 mo ago · declared · repoUrl → "https://github.com/Misar-AI/misarreach-mcp"
2 mo ago · declared · homepageUrl → "https://www.misarreach.com"

when	check	result	http	latency	detail
31 min ago	mcp initialize	ok	200	575 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
2 h ago	mcp initialize	ok	200	584 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
2 h ago	mcp initialize	ok	200	564 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
4 h ago	mcp initialize	ok	200	355 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
5 h ago	mcp initialize	ok	200	567 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
6 h ago	mcp initialize	ok	200	863 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
7 h ago	mcp initialize	ok	200	636 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
8 h ago	mcp initialize	ok	200	957 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
9 h ago	mcp initialize	ok	200	675 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools
10 h ago	mcp initialize	ok	200	935 ms	server misarreach 5.2.0 · protocol 2025-06-18 · 31 tools

MisarReach MCP Server

Evidence

What the publisher says

Capabilities

Where this record came from