The MisarReach MCP Server MCP server,
connected in one click.

“Use “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 f.”

“Use “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_s.”

“Use “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 g.”

“Use “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 use.”

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 f

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_s

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 g

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 use

discover_companies — Find COMPANIES matching firmographic criteria via Hunter.io, optionally pulling contact emails for each. This is company-level discovery —

enrich_lead — Fill in a saved lead's missing person and company detail — seniority, department, LinkedIn, phone, company size, industry. Use it on one l

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

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, no