MisarReach MCP server — find and enrich leads, verify emails, run multi-channel
MisarReach MCP server — find and enrich leads, verify emails, run multi-channel outreach, and manage the sales pipeline from any MCP client.
active Production-safe Score 84/100 http no auth
At a glance
| Endpoint | https://api.misar.io/reach/mcp |
|---|---|
| Source | https://github.com/Misar-AI/misarreach-mcp |
| Transport | http |
| Tools | 31 |
| Auth | none |
| First seen | 2026-08-19 00:14:02 |
| Last checked | 2026-11-17 21:57:05 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1527 / 1928 ms |
| Last successful check | 2026-11-17 21:57:05 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (31)
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 fsearch_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_sget_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 gsubmit_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 usediscover_companies— Find COMPANIES matching firmographic criteria, optionally pulling contact emails for each. This is company-level discovery — reach for itenrich_lead— Fill in a saved lead's missing person and company detail — seniority, department, LinkedIn, phone, company size, industry. Use it on one lverify_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 ascore_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, nolist_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 listcreate_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_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 epreview_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,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 colist_deals— List deals as a flat, paged array, optionally filtered by status, with revenue totals alongside. Use this when you want deals as data — tocreate_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 createsupdate_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_dealget_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 stmove_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;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 conslist_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 forget_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 runIdget_channels_status— Report the configuration, connection state and delivery stats for every outreach channel — WhatsApp, SMS and push. Check this before relyiupdate_channel— Turn one outreach channel on or off — WhatsApp, SMS or push. This changes how the account actually delivers messages, so it affects live cget_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.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. Theget_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: useprocess_sales_agent— Run the sales-agent pipeline over one conversation: decide the next action and carry it out. This ACTS on a real conversation — dependingsearch_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 LinkedIreveal_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 stacompany_email_format— The email address format a company uses (e.g. {first}.{last}@acme.com), learned only from addresses that were verified deliverable, with eacverify_email— Check whether one email address can receive mail. Returns valid, invalid, accept_all (a catch-all domain: the server accepts every address,
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:57:05 | ✓ | ✓ | 1529 ms | 85 | active |
| 2026-11-17 21:26:29 | ✓ | ✓ | 1689 ms | 85 | active |
| 2026-11-17 20:42:18 | ✓ | ✓ | 1268 ms | 85 | active |
| 2026-11-17 19:57:30 | ✓ | ✓ | 1574 ms | 85 | active |
| 2026-11-17 19:28:05 | ✓ | ✓ | 1699 ms | 85 | active |
| 2026-11-17 18:56:39 | ✓ | ✓ | 1522 ms | 85 | active |
| 2026-11-17 18:26:52 | ✓ | ✓ | 1673 ms | 85 | active |
| 2026-11-17 17:42:29 | ✓ | ✓ | 1541 ms | 85 | active |
| 2026-11-17 16:57:20 | ✓ | ✓ | 1232 ms | 85 | active |
| 2026-11-17 16:27:06 | ✓ | ✓ | 1503 ms | 85 | active |
| 2026-11-17 15:40:48 | ✓ | ✓ | 1535 ms | 85 | active |
| 2026-11-17 14:55:20 | ✓ | ✓ | 1615 ms | 85 | active |
| 2026-11-17 14:25:10 | ✓ | ✓ | 1379 ms | 85 | active |
| 2026-11-17 13:40:06 | ✓ | ✓ | 1239 ms | 85 | active |
| 2026-11-17 12:56:00 | ✓ | ✓ | 1576 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.misar.io/reach/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-misar-io-reach-mcp # JSON