Hubertino: Google Maps leads
NPM · @HUBERTINO/MCP-SERVER
Scrape Google Maps business leads (phones, websites, emails, socials) with Hubertino.
Available components
Last scanned (22 hours ago)
Scores higher than 75% of npm servers
Category Web Scraping
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1843 tokens (~307/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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 →
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.
- 20 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 15 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 9 Nov 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.90 functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
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/@hubertino/mcp-server@0.1.0
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 →
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 →
download_export Download scrape as CSV/XLSX ~158
Save a finished scrape as a spreadsheet file on this computer and return its path. The API serves the file itself (authenticated), so this tool downloads it rather than returning a link. Only works once the scrape status is done. The file uses the full column layout (every column, blanks where unknown). Files are never overwritten: an existing name gets a -1, -2... suffix.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | – | Absolute directory to save into. Defaults to HUBERTINO_DOWNLOAD_DIR, else ~/Downloads, else the system temp directory. |
| format | string | – | xlsx (default, Excel/Google Sheets) or csv. |
| scrapeId | string | yes | The scrape id returned by start_scrape or list_scrapes (a UUID). |
No output schema declared.
No examples provided.
get_results Get scrape results (lead rows) ~419
Read a scrape's rows as compact JSON, one page at a time. Works while the scrape is running (partial rows) and after it is done. Long pages are cut short to fit one tool response (trimmed: true); keep paging from nextOffset. Each row is one business with only its populated fields, e.g. name, category, phone, email, website, address, city, state, postal_code, country_code, rating, reviews, business_status, company_facebook/instagram/linkedin/x/youtube, location_link, place_id and _status (found -> extracted -> enriched). Page with offset/nextOffset until hasMore is false. For a spreadsheet of every row use download_export instead of paging through thousands of rows.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | compact (default) drops long or duplicate columns (coordinates, opening hours, internal ids, links to order/reserve) and shortens very long text; full returns every populated column. |
| fields | array | – | Only return these columns, e.g. ["name","email","phone","website"]. Overrides detail. Available columns include query, name, category, phone, email, website, domain, company_facebook, company_instagr… |
| limit | integer | – | Rows per page (1-1000, default 50). |
| offset | integer | – | Rows to skip (default 0). Use nextOffset from the previous page. |
| scrapeId | string | yes | The scrape id returned by start_scrape or list_scrapes (a UUID). |
| withEmailOnly | boolean | – | Only return rows that have an email address. Filters within the requested page. |
No output schema declared.
No examples provided.
get_scrape Get scrape status ~134
Get one scrape's live status (queued, running, done, error), progress (stage, percent, searches done, places found/extracted), resultCount, credits reserved/charged, and coverage (how many delivered rows have an email, phone, website, socials...). Use it to check on a scrape without waiting; use wait_for_scrape to block until it finishes.
| Name | Type | Req | Description |
|---|---|---|---|
| includeSearches | boolean | – | Also return the individual Google Maps searches (query, URL, result count). Can be long. |
| scrapeId | string | yes | The scrape id returned by start_scrape or list_scrapes (a UUID). |
No output schema declared.
No examples provided.
list_scrapes List scrapes ~100
List this account's most recent scrapes, newest first (the API keeps the latest 200): id, title, status, resultCount, credits charged and dates. Use it to find a scrape id or to reuse a finished scrape instead of paying for the same search again.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many scrapes to return (1-200, default 20). |
| status | string | – | Only return scrapes with this status. |
No output schema declared.
No examples provided.
start_scrape Start a Google Maps lead scrape ~586
Start a Hubertino scrape that searches Google Maps for businesses and returns them as lead rows (name, category, phone, website, email, address, rating, reviews, social profiles). Use it for requests like "find dentists in Austin with emails" or "build a list of plumbers in Leeds". Every category is searched in every location: categories x locations searches, max 2000 per scrape. COSTS CREDITS: it reserves categories x locations x maxResults credits up front (capped at the balance), charges 1 credit per business actually delivered and refunds the rest. Confirm with the user before large scrapes. Returns the scrape id immediately (status queued); then call wait_for_scrape, then get_results or download_export. Limited to 12 new scrapes per 5 minutes per account.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | What to search Google Maps for, one business type per item, e.g. ["dentist"], ["plumber", "HVAC contractor"]. Use the words a customer would type into Google Maps. 1-1000 items, each 1-120 characters. |
| country | string | – | Optional Google edition (lower-case country code) used for the search: us, gb, ca, au, ie, de, fr, es, it, pt, nl, be, at, ch, se, no, dk, fi, pl, cz, lt, lv, ee, ro, hu, gr, br, mx, jp, in, nz, za.… |
| enrichLinks | boolean | – | Collect social profiles and ordering/reservation links for each place. Default true, no extra credits. |
| enrichWebsite | boolean | – | Visit each business's own website to find a contact email (and social profiles). Default true, no extra credits. Keep it on whenever the user wants emails. |
| locations | array | yes | Where to search, one place per item: a city, region, neighbourhood or zip/postal code, e.g. ["Austin, TX, United States"], ["Vilnius, Lithuania"], ["90210, CA, USA"]. Include the country for the best… |
| maxResults | integer | yes | Maximum places to collect PER SEARCH (per category x location pair), 1-500. Google Maps typically returns around 100 places per search; use 500 for "everything". This also sets the worst-case credit… |
No output schema declared.
No examples provided.
wait_for_scrape Wait for a scrape to finish ~160
Poll a scrape until it is done (or failed), or until timeoutSeconds passes, then return its status like get_scrape. If it is still running when the time is up, just call wait_for_scrape again. Sends MCP progress notifications when the client asks for them. Many MCP clients abort a tool call after about 60 seconds, so keep the default timeout unless you know yours allows more.
| Name | Type | Req | Description |
|---|---|---|---|
| pollIntervalSeconds | integer | – | Seconds between status checks (2-60, default 5). |
| scrapeId | string | yes | The scrape id returned by start_scrape or list_scrapes (a UUID). |
| timeoutSeconds | integer | – | How long to wait before returning the current status (5-600, default 50). |
No output schema declared.
No examples provided.
How do I install the Hubertino: Google Maps leads MCP server?
Hubertino: Google Maps leads runs locally as an npm package, launched with npx -y @hubertino/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @hubertino/mcp-server
claude mcp add hubertino-app-hubertino-mcp -- npx -y @hubertino/mcp-server
What is the Hubertino: Google Maps leads MCP server?
Hubertino: Google Maps leads is an MCP server listed in the public MCP registry as io.github.hubertino-app/hubertino-mcp. Scrape Google Maps business leads (phones, websites, emails, socials) with Hubertino. This page covers its npm package (@hubertino/mcp-server).
Is the Hubertino: Google Maps leads MCP server safe to use?
Hubertino: Google Maps leads 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 Hubertino: Google Maps leads MCP server expose?
Hubertino: Google Maps leads exposes 6 tools: start_scrape, get_scrape, wait_for_scrape, list_scrapes, get_results, download_export. Their descriptions and schemas cost roughly 1,557 tokens of context every time the server is loaded.
Is the Hubertino: Google Maps leads MCP server still maintained?
Hubertino: Google Maps leads 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 Hubertino: Google Maps leads MCP server under?
Hubertino: Google Maps leads 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 Hubertino: Google Maps leads MCP server?
VerifyMCP ran 15 checks on Hubertino: Google Maps leads, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Hubertino: Google Maps leads: Security disclosure. 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.