_ registry / mcp streamable-http · checked 1h ago

misarreach

https://reach.misar.io

Registry code: 3ac3ab555316d179

api record

endpoint: https://reach.misar.io/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

reachable

live

uptime, 30 days

50%

90 days 50%· all time 50%

latency

583ms

last good check

priced tools

of 27 tools

_ answered our checks, 90 days 2 checks · signed record

2026-10-03 15:33 degraded → live
2026-10-03 13:31 unknown → degraded· fetch failed

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 27 tools

27 auth-required 27 of 27 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

list_leads auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "page": { "type": "number", "description": "Page number (default 1)" }, "limit": { "type": "number", "description": "Results per page (default 20, max 100)" }, "job_id": { "type": "string", "description": "Filter leads by a specific search job UUID" }, "search": { "type": "string", "description": "Search term to filter by name, email, or company" } } }
arguments 21 lines

search_leads auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query describing the ideal lead (2-200 chars)"
    },
    "useAI": {
      "type": "boolean",
      "description": "Use AI to enrich and score results (default false)"
    },
    "filters": {
      "type": "object",
      "properties": {
        "role": {
          "type": "string",
          "description": "Job title or role"
        },
        "industry": {
          "type": "string",
          "description": "Industry sector"
        },
        "location": {
          "type": "string",
          "description": "Geographic location"
        },
        "companySize": {
          "type": "string",
          "description": "Company size range (e.g. '10-50')"
        }
      },
      "description": "Optional filters"
    }
  }
}

arguments 38 lines

get_search_job_status auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "jobId" ], "properties": { "jobId": { "type": "string", "description": "Lead search job UUID" } } }
arguments 12 lines

discover_companies auth-required 1h ago

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.

mcp-tool

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max companies to return (1-100, default 20)"
    },
    "query": {
      "type": "string",
      "description": "Free-text company search query"
    },
    "industry": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Industry filters (max 10)"
    },
    "location": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Location filters (max 10)"
    },
    "technology": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Technology stack filters (max 10)"
    },
    "fetch_emails": {
      "type": "boolean",
      "description": "Also fetch contact emails for discovered companies (default false)"
    },
    "headcount_max": {
      "type": "number",
      "description": "Maximum employee count"
    },
    "headcount_min": {
      "type": "number",
      "description": "Minimum employee count"
    }
  }
}

arguments 46 lines

enrich_lead auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "leadId" ], "properties": { "leadId": { "type": "string", "description": "Lead UUID from list_leads" } } }
arguments 12 lines
list_lead_lists auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
send_to_campaign auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "leadIds", "campaignId" ], "properties": { "listId": { "type": "string", "description": "Target contact list UUID (defaults to campaign's own list)" }, "leadIds": { "type": "array", "items": { "type": "string" }, "description": "Lead UUIDs to import (1-500)" }, "campaignId": { "type": "string", "description": "Target campaign UUID" } } }
arguments 24 lines
list_deals auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "limit": { "type": "number", "description": "Max results (default 50, max 100)" }, "offset": { "type": "number", "description": "Pagination offset (default 0)" }, "status": { "type": "string", "description": "Filter by deal status (e.g. new, contacted, interested, meeting, proposal, closed, lost)" } } }
arguments 17 lines
update_deal auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "dealId" ], "properties": { "notes": { "type": "string", "description": "Updated deal notes (max 5000 chars)" }, "value": { "type": "number", "description": "Updated deal value in minor currency units" }, "dealId": { "type": "string", "description": "Deal UUID" }, "status": { "enum": [ "interested", "meeting", "proposal", "closed", "lost" ], "type": "string", "description": "New deal status" } } }
arguments 31 lines
move_deal_stage auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "dealId", "newStage" ], "properties": { "dealId": { "type": "string", "description": "Deal UUID" }, "newStage": { "enum": [ "new", "contacted", "interested", "meeting", "proposal", "closed", "lost" ], "type": "string", "description": "Target stage" } } }
arguments 26 lines

update_sales_agent_config auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "properties": {
    "enabled": {
      "type": "boolean",
      "description": "Enable or disable the sales agent"
    },
    "cal_link": {
      "type": "string",
      "description": "Calendly or Cal.com URL for meeting booking (max 500 chars, set null to clear)"
    },
    "offer_price": {
      "type": "number",
      "description": "Offer price in minor currency units (integer, min 0)"
    },
    "offer_description": {
      "type": "string",
      "description": "Short description of the offer (max 1000 chars, set null to clear)"
    },
    "max_replies_per_day": {
      "type": "number",
      "description": "Maximum automated replies per day (1-500, default 20)"
    },
    "confidence_threshold": {
      "type": "number",
      "description": "Confidence score below which agent flags for human review (0.0-1.0, default 0.65)"
    }
  }
}

arguments 29 lines

process_sales_agent auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "conversationId" ], "properties": { "conversationId": { "type": "string", "description": "UUID of the conversation to process" } } }
arguments 12 lines
get_channels_status auth-required 1h ago
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.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_pipeline auth-required 1h ago
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.

mcp-tool
{ "type": "object", "properties": { "workspaceId": { "type": "string", "description": "Optional workspace UUID to filter pipeline" } } }
arguments 9 lines
get_autopilot_status auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "runId" ], "properties": { "runId": { "type": "string", "description": "Autopilot run UUID" } } }
arguments 12 lines
submit_lead_feedback auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "jobId", "leadEmail", "feedback" ], "properties": { "jobId": { "type": "string", "description": "Lead search job UUID" }, "feedback": { "enum": [ "positive", "negative" ], "type": "string", "description": "Feedback sentiment" }, "leadEmail": { "type": "string", "description": "Email address of the lead" } } }
arguments 26 lines
verify_emails auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "email": { "type": "string", "description": "Single email to verify (use this OR emails array)" }, "emails": { "type": "array", "items": { "type": "string" }, "description": "Batch of emails to verify (max 20)" } } }
arguments 16 lines
score_leads auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "jobId": { "type": "string", "description": "Score all unscored leads for this job UUID (use this OR leadIds)" }, "leadIds": { "type": "array", "items": { "type": "string" }, "description": "Specific lead UUIDs to (re)score (max 200, use this OR jobId)" } } }
arguments 16 lines
create_lead_list auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "List name (1-200 chars)" } } }
arguments 12 lines
sync_lead_list auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "listId" ], "properties": { "listId": { "type": "string", "description": "Hunter.io list ID (integer as string)" } } }
arguments 12 lines
preview_message auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "Person's full name (1-100 chars)" }, "role": { "type": "string", "description": "Job title or role (optional, max 100 chars)" }, "company": { "type": "string", "description": "Company name (optional, max 100 chars)" } } }
arguments 20 lines

create_deal auth-required never probed

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.

mcp-tool

{
  "type": "object",
  "required": [
    "leadEmail"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "description": "Deal notes (max 5000 chars)"
    },
    "value": {
      "type": "number",
      "description": "Deal value in minor currency units (default 0)"
    },
    "currency": {
      "type": "string",
      "description": "ISO 4217 currency code (default USD)"
    },
    "leadName": {
      "type": "string",
      "description": "Lead's display name"
    },
    "contactId": {
      "type": "string",
      "description": "UUID of associated contact"
    },
    "leadEmail": {
      "type": "string",
      "description": "Lead's email address"
    },
    "campaignId": {
      "type": "string",
      "description": "UUID of associated campaign"
    },
    "conversationId": {
      "type": "string",
      "description": "UUID of associated conversation"
    }
  }
}

arguments 40 lines

start_autopilot auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "goal" ], "properties": { "goal": { "type": "string", "description": "Outreach goal description (10-500 chars). E.g. 'Find and email 10 SaaS startup CTOs in London about our product'" }, "workspace_id": { "type": "string", "description": "Optional workspace UUID to associate with this run" } } }
arguments 16 lines
list_autopilot_runs auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": { "limit": { "type": "number", "description": "Max results (default 20)" }, "offset": { "type": "number", "description": "Pagination offset" } } }
arguments 13 lines
update_channel auth-required never probed
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.

mcp-tool
{ "type": "object", "required": [ "channel", "enabled" ], "properties": { "channel": { "enum": [ "whatsapp", "sms", "push" ], "type": "string", "description": "Channel to update" }, "enabled": { "type": "boolean", "description": "Whether to enable (true) or disable (false) the channel" } } }
arguments 22 lines
get_sales_agent_config auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines
get_sales_agent_actions auth-required never probed
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.

mcp-tool
{ "type": "object", "properties": {} }
arguments 4 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, it shows the verified badge, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3ac3ab555316d179.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3ac3ab555316d179/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/3ac3ab555316d179/badge.svg)](https://brick.blue/agent/3ac3ab555316d179)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on misar.io 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

mail.misar.io misarmail mcp · 54 tools