Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.gtovtya/b2bleads-mcp

NPM · B2BLEADS-MCP

Search and enrich B2B business leads by industry and city.

Available components

0 this week 84 Trust /100

Last scanned (21 hours ago)

Scores higher than 75% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1253 tokens (~125/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Schema quality: 174 → 125 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.70 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/b2bleads-mcp@1.6.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,253 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_get_usage ~54

Get how much of the connected B2BLeads account's monthly search quota has been used and how much remains for the current billing period. Use account_get_usage_limit for the plan's total monthly limit and renewal date.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

account_get_usage_limit ~48

Get the connected B2BLeads account's total monthly search quota and when the current billing period renews. Use account_get_usage for how much of it has been used so far.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_email ~101

Look up a best-effort contact email for a single business website (checks the homepage and common contact pages). Use this for one specific website, e.g. from a saved list or CSV, rather than re-running search_leads. May return a null email if none could be found; this tool never fabricates an address.

NameTypeReqDescription
websitestringyesThe business website URL to look up a contact email for, e.g. "https://example.com".

No output schema declared.

No examples provided.

get_saved_list ~55

Get one saved lead list by ID, including its full set of saved leads (read-only).

NameTypeReqDescription
list_idstringyesThe saved list's ID, from list_saved_lists or a search_leads save_to_list response.

No output schema declared.

No examples provided.

get_search_history ~54

Get the connected B2BLeads account's recent search history (up to the last 200 searches: query text, result count, date). Use this when the user asks what they searched for before. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_industries ~30

List the predefined industry categories that can be used as the `industry` filter in search_leads.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_saved_lists ~68

List all of the user's saved lead lists (read-only) — id, name, and lead count for each, not the leads themselves. Use this when the user asks what they've already saved, or which lists exist. Call get_saved_list with a list's id to fetch its full leads.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_saved_searches ~51

List the connected B2BLeads account's saved search alerts (recurring searches set up to auto-run and save results to a list). Read-only — never creates, modifies, or deletes one.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_leads ~396

Search for companies and business contacts in real time by industry, city, and other filters. Returns a ready-to-use list of leads (name, address, phone, website, and email where available). Use this whenever the user asks to find, list, or collect businesses/companies for sales, outreach, or research.

NameTypeReqDescription
citystring–City or region to search in, e.g. "Berlin" or "Austin, TX".
has_websiteboolean–Only return businesses that have a website.
industrystring–Industry filter. One of the predefined categories.
langstring–Result language as a BCP-47 tag, e.g. "en" or "pt-BR".
limitinteger–Max number of results to return (1-20). Defaults to a server-side value if omitted.
list_idstring–Existing saved-list ID to append results to.
list_namestring–Name of a saved list to find-or-create and append results to.
min_ratingnumber–Minimum rating (0-5) a business must have to be included.
open_nowboolean–Only return businesses that are currently open.
page_tokenstring–Pagination token returned by a previous call, to fetch the next page of results.
price_levelstring–Filter by price level.
qstring–Free-text search query, e.g. "construction companies in Munich". Optional if industry+city are given.
radius_kmnumber–Search radius in kilometers around the city center.
rank_bystring–How to sort results.
save_to_listboolean–If true, also save the results into a B2BLeads saved list (requires list_id or list_name).
verified_onlyboolean–Only return businesses with a verified listing.

No output schema declared.

No examples provided.

search_leads_advanced ~396

⚠️ ELEVATED COST: consumes 9x the quota of a single search_leads call. Only use this when the user explicitly wants more results than a regular search_leads call returned for one city, or asks to exhaustively cover a city — never as a default or first attempt; always try search_leads first. Tiles the given city into a 3x3 grid of sub-searches server-side to go beyond the normal ~20-60 result ceiling and return up to ~180 deduplicated businesses in one city. Requires an exact city name only (not the free-text query or industry) — passing a full sentence instead of a city name can cause it to geocode the wrong place and return zero results. Does not support pagination. Read-only: it never saves, creates, updates, or deletes leads.

NameTypeReqDescription
citystringyesCity or region to search in, e.g. "Berlin" or "Austin, TX". Must be ONLY the city name — do not pass the free-text query or industry words here, or the city may be geocoded incorrectly (e.g. resolvin…
has_websiteboolean–Only return businesses that have a website.
industrystring–Industry filter. One of the predefined categories.
langstring–Result language as a BCP-47 tag, e.g. "en" or "pt-BR".
min_ratingnumber–Minimum rating (0-5) a business must have to be included.
open_nowboolean–Only return businesses that are currently open.
price_levelstring–Filter by price level.
qstring–Free-text search query, e.g. "construction companies". Optional if industry is given.
verified_onlyboolean–Only return businesses with a verified listing.

No output schema declared.

No examples provided.

Install

How do I install the io.github.gtovtya/b2bleads-mcp server?

io.github.gtovtya/b2bleads-mcp runs locally as an npm package, launched with npx -y b2bleads-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · b2bleads-mcp

# add to Claude Code
claude mcp add gtovtya-b2bleads-mcp -- npx -y b2bleads-mcp
Common questions

What is the io.github.gtovtya/b2bleads-mcp server?

io.github.gtovtya/b2bleads-mcp is listed in the public MCP registry as io.github.gtovtya/b2bleads-mcp. Search and enrich B2B business leads by industry and city. This page covers its npm package (b2bleads-mcp).

Is the io.github.gtovtya/b2bleads-mcp server safe to use?

io.github.gtovtya/b2bleads-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.gtovtya/b2bleads-mcp server expose?

io.github.gtovtya/b2bleads-mcp exposes 10 tools: search_leads, search_leads_advanced, list_industries, list_saved_lists, get_saved_list, and 5 more. Their descriptions and schemas cost roughly 1,253 tokens of context every time the server is loaded.

Is the io.github.gtovtya/b2bleads-mcp server still maintained?

io.github.gtovtya/b2bleads-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.gtovtya/b2bleads-mcp server under?

io.github.gtovtya/b2bleads-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.gtovtya/b2bleads-mcp server?

VerifyMCP ran 16 checks on io.github.gtovtya/b2bleads-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.