Nose for Leads MCP server
com.noseforleads/leads-mcpnoseforleads.comstreamable-httpv1.0.0Scanned
Finds, filters, and verifies local-business leads; every email carries a verification receipt.
11 tools: 1 do something that can't be undone, 4 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Nose for Leads MCP server can do
The Nose for Leads MCP server is published by noseforleads.com, a domain the MCP Registry verified. It has 11 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (4 tools: translate_icp, start_campaign, add_suppression and review_lead), but cannot delete data. 6 tools only read.
1 tool brings in text other people can write (start_campaign); 1 tool can send data out of your system (send_feedback).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
11 tools
Can't be undone 1Claude Code: ask
send_feedbackSend feedback to the Nose for Leads team.Can send data outNo findings
Why it is in this group
- The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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 freely; it's our main signal for improving the product and the agent experience.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
add_suppressionAdd an email or domain to the suppression list (scope is 'email' or 'domain') so future campaigns exclude it.No findings
Why it is in this group
- The name "add_suppression" says "add": a word for a change.
Description, as the server wrote it Add an email or domain to the suppression list (scope is 'email' or 'domain') so future campaigns exclude it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
review_leadMark a lead kept or discarded after review (status: kept | discarded | unreviewed).No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_campaignSubmit a lead-generation campaign.Reads text others writeNo findings
Why it is in this group
- The name "start_campaign" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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), or construct it directly. An unknown predicate field (or rank), and any unknown `discovery` key, is rejected with a 422 naming it; an unknown top-level `query` key is silently ignored, so keep to predicates/rank/discovery — a typo there will not error, it will just do nothing. Costs 1 credit per validated lead — every campaign type, including founder/person campaigns and campaigns that filter on Meta ads. A campaign cannot overspend: if discovered leads exceed your balance it delivers what your credits cover and the campaign ends `done_partial`; check get_credits first if your balance is low. vertical/geo are REQUIRED except for a locationless campaign — `query` carrying a discovery block with mode 'launch_feeds' or 'web_search' — which has no geography at all. If the tenant has no card on file this returns a 403 `card_required` error with a `setup_url` — surface that URL to the user so they can verify a card (never charged unless they buy a pack). Pass a stable idempotency_key when you might retry — a retry returns the ORIGINAL campaign (idempotent_replay=true), never a duplicate charge. Returns {job_id, idempotent_replay}; poll get_campaign_status with job_id.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
translate_icpTranslate free-text ICP description (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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` is non-empty when the ask routes OUTSIDE Google Maps, in one of two shapes. Mode 'launch_feeds': people/companies that RECENTLY LAUNCHED (e.g. "founders of B2B SaaS that launched in the last 3 months") — it names the launch feeds to search and whether the leads are people or companies. Mode 'web_search': long-tail ONLINE businesses Google Maps never had (e.g. "marketing agencies for dentists"), found via paid organic search — companies only, never people. Either way the block is already embedded inside the returned `query`, so passing `query` through unchanged is all that's needed; neither mode has a geography, so vertical/geo come back empty and start_campaign does not require them. Anything we cannot actually source lands in `unsupported` instead — read that list aloud to the user rather than pretending the campaign will cover it.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
fetch_resultsFetch a page of leads produced by a campaign (paginate with offset/limit).No findings
Why it is in this group
- The name "fetch_results" says "fetch": a word for reading.
Description, as the server wrote it 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 counts the filtered population. Rows carry verification receipts (verified_by/verified_at/ verifier_verdict) when a live verification exists — treat them as the authoritative proof; null means no receipt, not a failure. Two more quotable proof lines appear where earned: person_receipt (who the person is and where we saw them launch, on person-target leads) and tech_receipt (dated evidence of the detected platform) — forward them as-is.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_campaign_statusCheck the status of a previously submitted campaign (queued/running/done/ done_partial/failed) by job_id.No findings
Why it is in this group
- The name "get_campaign_status" says "get": a word for reading.
Description, as the server wrote it 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], never errors.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_creditsCheck 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 ledge…No findings
Why it is in this group
- The name "get_credits" says "get": a word for reading.
Description, as the server wrote it 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 this also returns YOUR key's remaining budgets — check it before large campaigns.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_icp_packList the ICP packs (saved vertical/geo templates) available to this tenant.No findings
Why it is in this group
- The name "get_icp_pack" says "get": a word for reading.
Description, as the server wrote it List the ICP packs (saved vertical/geo templates) available to this tenant.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
get_usageToday's external vendor usage against the tenant's daily quota (vendor_calls_today / per_day_max / remaining).No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it 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 creator discovery costs one unit per delivered record, so it can consume far more than one call's worth. Mirrors REST GET /v1/usage.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
list_campaignsList 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 poll…No findings
Why it is in this group
- The name "list_campaigns" says "list": a word for reading.
Description, as the server wrote it 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), created_after/ created_before (ISO-8601 window over creation time), order ('desc' default, 'asc' oldest first). Paginate with offset/limit (limit 1-200); `total` counts everything matching the filters, not just this page.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.noseforleads.com/.well-known/oauth-protected-resource
- Authorization servers
- https://api.noseforleads.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.noseforleads.com/mcp: tools/list returned 11 tools to an anonymous client, including send_feedback (irreversible), translate_icp (write), start_campaign (write), add_suppression (write), review_lead (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http leads https://api.noseforleads.com/mcpclaude mcp add --transport http leads https://api.noseforleads.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__leads__get_campaign_status",
"mcp__leads__fetch_results",
"mcp__leads__get_icp_pack",
"mcp__leads__get_credits",
"mcp__leads__list_campaigns",
"mcp__leads__get_usage"
],
"ask": [
"mcp__leads__translate_icp",
"mcp__leads__start_campaign",
"mcp__leads__add_suppression",
"mcp__leads__review_lead",
"mcp__leads__send_feedback"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as leads. Review it before you use it.
Capability tags behind 2 rules
- mcp__leads__start_campaign untrusted-input
- mcp__leads__send_feedback outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.noseforleads/leads-mcp/verify?hash=231f1492071c29b1eb5650b1302682ab4aa7186a2917d276c62e461aa356a79f" | jq -e '.changed == false'Pinned hash 231f1492071c, from Nov 13, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.noseforleads/leads-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.noseforleads/leads-mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
Nose for Leads MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Nose for Leads MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Nose for Leads MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Nose for Leads MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_feedback.
What tools does the Nose for Leads MCP server have?
- 11 tools: 1 irreversible, 4 write, 6 read. send_feedback, translate_icp, start_campaign, add_suppression, review_lead, get_campaign_status, fetch_results, get_icp_pack and 3 more.
Does the Nose for Leads MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Nose for Leads MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.
Has the Nose for Leads MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.