Model Context Protocol (MCP) server for Apollo.io API integration
GoodLeads 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
Find new business owner contacts the morning the state posts a filing. Preview free, pay per record.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http goodleads-mcp https://mcp.goodleads.club/mcp
# 2 — ask your agent for something these tools do
# find_lead_by_glid, data_quality_scorecard, field_fill_rates and 11 more
GoodLeads 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 goodleads-mcp https://mcp.goodleads.club/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.
14 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.
One record in full, by its Lead ID (e.g. GL-CO-00042). Use this when you already hold a Lead ID — from a file, a CRM, a receipt — and want everything we know about that business and its owner: the business, the primary contact, both scores, every attribute, and where each field came from. Args: glid: The Lead ID, e.g. GL-CO-00042 — the lead_ref field on every
| Parameter | Type | Required | Notes |
|---|---|---|---|
| glid | string | yes | — |
How clean is the data a buyer would receive in a state — numbers, not adjectives. The scorecard grades the records a buyer would receive on mechanical conformance across four dimensions — format (state/phone/email/zip), completeness (a name for who filed it, an address present), consistency (names in CRM-ready Title Case, not ALL-CAPS; the address's own state agrees with its Z
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | no | — | |
| sample_limit | integer | no | — |
How complete is every column in the file a buyer receives — exact counts, one call. Answers "what share of the records carries a value in each field?" for every delivered column, in the file's own order. It is exact (counted from stored values over every sellable record, not sampled) and always current (refreshed whenever the data changes; computed_at dates it). Use it before pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | no | — |
Browse leads — rows for a shape or a saved list, or (summary=True) its counts, facets and price. Type it the way your buyer says it. Filter values are understood, not matched literally: "residential", "cell", "CST", "Texas", "on fire", "Denver metro" and "working from home" all resolve (case, spacing, plurals and reviewed words), and every response echoes what was understood in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | no | — | |
| filters | no | — | |
| page | integer | no | — |
| page_size | integer | no | — |
| sort | no | — | |
| sort_dir | string | no | — |
| include_non_operating | boolean | no | — |
| include_existing | boolean | no | — |
| list_id | no | — | |
| states | no | — | |
| summary | boolean | no | — |
| lane | no | — | |
| cap | no | — | |
| group_by | no | — |
Start here: the buyer's own words become a list we can count, price and sell. Give it what the buyer would type ("cleaning companies in Texas", "denver plumbers formed last 30 days with a phone", "NAICS 238220", "SIC 1711", "MCC 5812", "google category plumber") and you get back a list shape in the one filter contract — states, filters, sort, lane, cap — with a one-s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| state | no | — | |
| current | no | — |
What this list costs before anyone pays: how many records name a person, and the price by grade. Pass a saved list (list_id, the 8-char id in #browse?list=<id>) or an inline shape (filters + states; omit states for every live state: CO, CT, FL, NY, TX, VA). You get the same numbers the buy page shows a person: matching, sellable, verified_one, verified_both, `no_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | no | — | |
| states | no | — | |
| filters | no | — | |
| include_held | boolean | no | — |
| lane | no | — | |
| cap | no | — | |
| offer_code | no | — | |
| include_existing | boolean | no | — |
| group_by | no | — |
Ready-made lists to start from: every live state × business type, with live counts and a starting price. Returns one document: {"count": N, "starters": [...]} — one entry per (state, business type): the display label, the exact filters the card opens with, the graded counts (matching, sellable, verified_one, verified_both) and price_from_cents (the name-and-address
No parameter schema on file.
Turn a quoted list into a payment link a person completes — the buyer gets the file within a minute of paying. Creating the link costs nothing and charges nobody — payment only happens if a human opens the returned checkout_url and completes it on Stripe's hosted page. Hand the URL to your human; do not represent the purchase as complete until they confirm payment. Nothing is ch
| Parameter | Type | Required | Notes |
|---|---|---|---|
| list_id | no | — | |
| filters | no | — | |
| states | no | — | |
| lane | string | no | — |
| cap | no | — | |
| delivery | string | no | — |
| customer_email | no | — | |
| crm_connection_id | no | — | |
| connector_crm_name | no | — | |
| offer_code | no | — | |
| include_existing | boolean | no | — |
The filter contract, from the schema endpoint (GET /api/v1/schema/attributes?include=grammar): fields, grammar, or recipes. Call this before building browse_leads filters you haven't used before. Each field lists the allowed_values when its vocabulary is closed and its accepted_words — the buyer's own words that mean a stored value ("cell" → mobile, "CST" → the Central zones)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | — |
Translate a classification code, or map YOUR word for a concept to this surface's fields — ask before concluding absence. Codes — the crosswalk. Every record carries NAICS, SIC, the Google Business category and the payment MCC, tied together by our own taxonomy. Give ANY one — term "MCC 5812", "SIC 1711", "NAICS 238220", "google category plumber" (or system = naics / sic /
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | — |
| system | no | — | |
| code | no | — |
Where we are live right now — the state codes, read from production, never a cached page. Call it before promising a buyer a state: a state not in this list is not live yet. Returns [{"state": "CO"}, ...] — codes only, no counts. For how many records a state holds, quote_list (or browse_leads(summary=True)) on that state returns the live graded counts.
No parameter schema on file.
What GoodLeads is, who buys it and how every record is built — call this to explain or vet us; to price a list, start with interpret_list. It is for anyone who wins by reaching a business owner first: to sell what a new owner needs now, to be the name they already know a year from now, to spot their own customer starting a business, or to build a product on every new business. Nev
No parameter schema on file.
The shelf — ready-made business type × state lists, with live counts. Returns the same live document list_starters returns — {"count": N, "starters": [...]}, one entry per (state, business type) with its display label, the exact filters it opens with, the graded counts (matching, sellable, verified_one, verified_both) and price_from_cents (the name-and-addres
No parameter schema on file.
Mint a hosted Stripe Checkout link for a list you shaped — the same code as checkout_list. Creating the link costs nothing and charges nobody — payment only happens if a human opens the returned checkout_url and completes it on Stripe's hosted page. Hand the URL to your human; do not represent the purchase as complete until they confirm payment. For new work, use the dedi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | no | — | |
| list_id | no | — | |
| filters | no | — | |
| states | no | — | |
| lane | string | no | — |
| cap | no | — | |
| delivery | string | no | — |
| customer_email | no | — | |
| crm_connection_id | no | — | |
| connector_crm_name | no | — | |
| offer_code | 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 GoodLeads 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.0.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 GoodLeads 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.