My Lead Fox MCP server

A searchable dataset of e-commerce shops -- filter, download and enrich domains through the My Lead Fox API.

Connect My Lead Fox All connectors

Tools: 5
Read-only: 5
Write: 0; Off by default
Destructive: 0; Flagged distinctly

What it does

My Lead Fox through an assistant

My Lead Fox holds structured records for e-commerce shops -- platform, traffic, apps installed, revenue estimates, categories, country, contact details -- and this connector lets an assistant query them in plain language. Every call spends real money from one of three metered credit pools, so the whole surface is shaped around that: size a segment before downloading it, see the balance on every result, and never mistake a pool running out for an answer. Everything here is read-only; nothing in this connector can create, change or delete anything.

Size a segment first -- a count and a reusable searchId, before a single row is paid for
Nineteen filter operators across text, numeric, dropdown, tag and date columns
Page rows out of any search, with any page directly addressable
Look up shops by domain when you already have the list
Find email and phone contacts for a domain (opt-in, and the scarcest pool by far)
Remaining balance on every result, and partial results named as partial rather than reported as the answer

Ask your assistant

What people actually ask

Real questions, answered from live My Lead Fox data.

“How many Shopify stores in the UK sell coffee and do over $1M a year?”

myleadfox_list_columnsmyleadfox_search

“Give me the first hundred of those with their domain, traffic and apps installed.”

myleadfox_searchmyleadfox_get_rows

“I have a list of 40 domains -- which are in My Lead Fox, and what do you know about them?”

myleadfox_lookup_domains

Tool catalogue

5 My Lead Fox tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

All tools

5 tools5 read-only · 0 write

Showing 5 of 5 tools

myleadfox_enrich_domains
Read-only
Find email and phone contacts for domains already in the My Lead Fox dataset. THE SCARCEST CREDIT POOL BY A LONG WAY -- a typical account holds a few hundred enrich credits against hundreds of thousands of download credits. Do not loop this over a large list. Enrichment is synchronous and each domain is checked live, so keep batches small; roughly one 100-domain batch per minute is the sustainable rate. Every domain comes back in exactly one of SIX outcomes and only `enriched` is charged. Read them before concluding anything: `no_contact_found` means the shop genuinely has no contacts, but `skipped_no_credit` means the balance ran out and `not_attempted` means the call timed out -- neither is evidence about the shop, and `not_attempted` domains should simply be sent again. COSTS: spends the "enrich" credit pool.
myleadfox_get_rows
Read-only
The only tool that returns shop data. Page a searchId from myleadfox_search, or pass filters inline. Any page is directly addressable -- page 500 needs no walk through 1-499. CHARGED PER ROW DELIVERED, up to 100 per call. Ask for `columns` you actually need. If the download balance is smaller than the page, you receive as many rows as you can afford and the result says `truncatedByCredits: true` -- that means the balance ran out, NOT that only that many shops matched. Never report a truncated page as the full result. A null value means the field has never been measured for that shop. It does not mean zero and does not mean empty. COSTS: spends the "download" credit pool.
myleadfox_list_columns
Read-only
List the queryable columns, grouped by theme, with the filter kind each one takes. Call this before building filters -- My Lead Fox has no column-discovery endpoint, so this is the only way to know what exists. FREE: it makes no API call and spends no credits. The list comes from My Lead Fox's documentation rather than from the API, so it can lag behind new fields. The API is the authority and validates every name: a column that does not exist is a 400 naming it, never a silently dropped field. So a column you expect but do not see here is worth trying anyway. Costs no credits and makes no API call.
myleadfox_lookup_domains
Read-only
Fetch shop records for up to 100 domains you already have. Use this instead of filtering when you know the domains. CHARGED PER DOMAIN FOUND -- misses cost nothing and are named. THREE lists come back and they mean different things. `rows` were found. `missing` are not in the My Lead Fox dataset and will still be missing tomorrow. `withheldForCredits` ARE in the dataset but past your download balance -- they are real shops you simply could not afford this call, and reporting them as not found would be wrong. Top up and ask for those again. A null field means never measured, not zero. COSTS: spends the "download" credit pool.
myleadfox_search
Read-only
Count how many shops match a filter set, WITHOUT returning any rows. Returns a total and a searchId you can then page with myleadfox_get_rows. Do this first. Rows are charged per row delivered, so sizing a segment before downloading it is how you avoid spending download credits discovering that a filter matched two million shops. Charges 1 search credit even when nothing matches. Use myleadfox_list_columns to see what can be filtered on. COSTS: spends the "search" credit pool.

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Your own credential

You supply your own My Lead Fox key, scoped however you like on their side. It is encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect My Lead Fox in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect My Lead Fox.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}

On Claude you paste one URL and sign in — no token to copy. See the setup guide for each client.