MisarReach is an MCP server with 27 tools an agent can call, among them create_deal, create_lead_list, discover_companies. It answers at https://api.misar.io/reach/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 20 October 2026, succeeded.
Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 migh Inputs: leadEmail, leadName, value, currency, notes, conversationId |
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 Inputs: name |
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. Inputs: query, industry, location, headcount_min, headcount_max, technology |
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 Inputs: leadId |
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 ke Inputs: runId |
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 firs |
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 o Inputs: workspaceId |
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 |
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 |
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, Inputs: jobId |
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 detai Inputs: limit, offset |
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 stage Inputs: status, limit, offset |
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 fro |
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 wi Inputs: page, limit, search, job_id |
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 fro Inputs: dealId, newStage |
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 pe Inputs: name, role, company |
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 ru Inputs: conversationId |
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 Inputs: jobId, leadIds |
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 Inputs: query, useAI, filters |
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 Inputs: leadIds, campaignId, listId |
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 Inputs: goal, workspace_id |
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 e Inputs: jobId, leadEmail, feedback |
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 Inputs: listId |
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 Inputs: channel, enabled |
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. Settin Inputs: dealId, status, value, notes |
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 Inputs: enabled, cal_link, offer_price, offer_description, max_replies_per_day, confidence_threshold |
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` fo Inputs: email, emails |
Every block below points at https://api.misar.io/reach/mcp. Pick your client and copy.
claude mcp add --transport http misarreach https://api.misar.io/reach/mcp
{
"mcpServers": {
"misarreach": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.misar.io/reach/mcp"]
}
}
}{
"mcpServers": {
"misarreach": {
"url": "https://api.misar.io/reach/mcp"
}
}
}{
"servers": {
"misarreach": {
"type": "http",
"url": "https://api.misar.io/reach/mcp"
}
}
}{
"context_servers": {
"misarreach": {
"url": "https://api.misar.io/reach/mcp"
}
}
}{
"mcpServers": {
"misarreach": {
"serverUrl": "https://api.misar.io/reach/mcp"
}
}
}{
"mcpServers": {
"misarreach": {
"url": "https://api.misar.io/reach/mcp"
}
}
}name: MisarReach
version: 0.0.1
schema: v1
mcpServers:
- name: MisarReach
type: streamable-http
url: https://api.misar.io/reach/mcp{
"mcpServers": {
"misarreach": {
"httpUrl": "https://api.misar.io/reach/mcp"
}
}
}{
"mcpServers": {
"misarreach": {
"type": "http",
"url": "https://api.misar.io/reach/mcp"
}
}
}{
"mcpServers": {
"misarreach": {
"url": "https://api.misar.io/reach/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.misar.io%2Freach%2Fmcp&type=streamable_http&id=misarreach&name=MisarReach
It answered our last check on 20 October 2026 in 942 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
27, as returned by the server's own tools/list on 12 September 2026: create_deal, create_lead_list, discover_companies, enrich_lead, get_autopilot_status, get_channels_status, get_pipeline, get_sales_agent_actions, and 19 more.
It answered our last check on 20 October 2026 in 942 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.misar.io/reach/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.misar-ai. Endpoint host: api.misar.io. ARD identifier: urn:air:io.github.misar-ai:mcp:misarreach-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.