Model Context Protocol (MCP) server for Apollo.io API integration
Nose for Leads is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Finds, filters, and verifies local-business leads; every email carries a verification receipt.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nose-for-leads-mcp https://api.noseforleads.com/mcp
# 2 — ask your agent for something these tools do
# translate_icp, start_campaign, get_campaign_status and 8 more
Nose for Leads costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nose-for-leads-mcp https://api.noseforleads.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Translate free-text ICP description (e.g. "plumbers in phoenix with no website") into a structured query. Call this BEFORE start_campaign — start_campaign only accepts a structured query dict, never free text. Returns {query, vertical, geo, category, location, preview, unsupported, discovery} — pass vertical/geo/query straight to start_campaign. `discovery
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
Submit a lead-generation campaign. Pass translate_icp's vertical, geo, and query fields directly (category/location are ALIASES for vertical/geo, accepted so translate output round-trips; prefer vertical/geo when constructing calls). query's full shape and field vocabulary are in this tool's schema — build it with translate_icp from free text (recommended),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — | |
| vertical | no | — | |
| geo | no | — | |
| category | no | — | |
| location | no | — | |
| idempotency_key | no | — |
Check the status of a previously submitted campaign (queued/running/done/ done_partial/failed) by job_id. Prefer wait_seconds=45 over sleeping between polls: the call holds until the status or pipeline stage changes (or the timer expires) and returns the normal snapshot either way — loop on it until status is terminal. Out-of-range wait_seconds clamps to [0, 45],
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
| wait_seconds | integer | no | — |
Fetch a page of leads produced by a campaign (paginate with offset/limit). kept_only=True returns only rows the user marked kept in review (for export). match_status narrows to one population: 'validated' (verified email, billed) or 'needs_review' (surfaced free; rejection_reason says why) — omit it for both. Returns {summary, total, offset, limit, rows}; total coun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
| offset | integer | no | — |
| limit | integer | no | — |
| kept_only | boolean | no | — |
| match_status | no | — |
List the ICP packs (saved vertical/geo templates) available to this tenant.
No parameter schema on file.
Add an email or domain to the suppression list (scope is 'email' or 'domain') so future campaigns exclude it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | yes | — |
| value | string | yes | — |
| reason | string | yes | — |
Mark a lead kept or discarded after review (status: kept | discarded | unreviewed). Then fetch_results(kept_only=true) returns only kept leads — the export set.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | — |
| result_id | integer | yes | — |
| status | string | yes | — |
Check this tenant's prepaid credit balance (a validated lead costs 1 credit — 2 for person-target or Meta-ads campaigns), the available credit packs, and the ledger (paginate ledger entries with offset/limit, newest first). Campaigns cannot start with a zero balance — buy a pack via the dashboard when balance runs low. When you authenticate with an API key t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | — |
| limit | integer | no | — |
List this tenant's campaigns, newest first — the recovery path when a job_id was lost: every row carries job_id, status, the query it ran, and credits spent, so you can resume polling (get_campaign_status) or fetch results without resubmitting (and double-charging). Filters: q (substring over vertical/geo), status (queued | running | done | done_partial | failed), c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offset | integer | no | — |
| limit | integer | no | — |
| q | no | — | |
| status | no | — | |
| order | string | no | — |
| created_after | no | — | |
| created_before | no | — |
Today's external vendor usage against the tenant's daily quota (vendor_calls_today / per_day_max / remaining). This is the OTHER ceiling besides credits: when remaining hits 0, campaign work pauses until midnight even with a healthy credit balance — check it before launching a large or urgent campaign. remaining is quota UNITS, which usually equals calls; a creato
No parameter schema on file.
Send feedback to the Nose for Leads team. Set kind='product' for feedback about the leads, the service, coverage, or pricing — relay what the business owner tells you (categories: lead_quality, pricing, missing_feature, praise, other). Set kind='tool' (default) for feedback about these MCP tools themselves — a confusing description, a bug, a missing capability. Use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | — |
| kind | string | no | — |
| category | string | no | — |
| tool | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nose for Leads or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.29.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Nose for Leads can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.