Unified 5-in-1 B2B ATS job and signal feed: Greenhouse, Workday, Ashby, Lever, SmartRecruiters.
Nothing to run from here
Ecommerce Leads 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.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Ecommerce store metrics by domain: revenue, ad spend, traffic. Log in to search 600k+ stores.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ecommerce-leads-mcp https://getecommerceleads.com/api/mcp
# 2 — ask your agent for something these tools do
# lookupStore, searchStores, getStoreChart and 18 more
Ecommerce Leads costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GEAll 1 server
getecommerceleads1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 ecommerce-leads-mcp https://getecommerceleads.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
21 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.
Look up one ecommerce store by domain. The reply has company data, estimated revenue, marketing budget, traffic, Google and Meta ad spend, ad counts, a Conversion Rate Score, buying signals, the store phone number, and social and ad-library links. Decision-maker contact fields are not in the fields list. With OAuth access, the decisionMakers object shows the contacts that you revealed. When other
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain, for example example.com. A full URL also works. |
Search the store catalog like the Ecommerce Leads dashboard. Returns 30 rows per page. Stores you have not revealed show masked values for the hidden fields; revealed stores show the real values. By default, each row has storeId, 9 key columns (Industry, Country, revenue, Total Traffic, Google and Meta ad spend, Buying Signals, Buying Signals List, Status) and a short "reveal" object (revealed, co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tab | string | no | Which stores to search: all (default), revealed, set:{id} for a signal set, or watchlist:{id} for a watchlist. Free plans can use all and revealed only. |
| filters | array | no | Column filters. All filters must match. |
| sort | object | no | — |
| page | integer | no | Page number, starting at 1. |
| columns | array | no | The column keys to return in each row. Use ["*"] for all columns. If you omit it, the default set is returned. An unknown key gives an error that lists the valid keys. |
| includeColumns | boolean | no | Set to true to get the column list (key, label, type) in the result. Default false. |
Get the latest 24 points of one metric for a store, for a chart. Values use your currency.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain, for example example.com. |
| metric | string | yes | The metric name. |
List your signal sets, with the signal catalog and the ICP columns you can use in criteria. Paid plans only.
No parameter schema on file.
Get one of your signal sets, with its criteria. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | integer | yes | The signal set id from listSignalSets. |
Check whether candidate signal criteria match enough stores (80 or more). Returns {"enough": true|false}. It does not save anything. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| criteria | object | yes | Either {"root": node} with a recursive tree, or the flat form {"signalIds": [...], "legacyCategories": [...], "icpFilters": [...]}. A node is {"type":"group","op":"AND"|"OR","children":[...]}, {"type" |
| setId | integer | no | Optional. The id of a set you are editing. |
List your watchlists and your blacklist, with the domain count of each. Paid plans only.
No parameter schema on file.
Get the domains of one watchlist or the blacklist, 100 per page. To see store data for a watchlist, call searchStores with tab "watchlist:{id}". Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listId | integer | yes | The list id from listWatchlists. |
| page | integer | no | Page number, starting at 1. |
Preview the credit cost of a reveal. Nothing is charged and nothing is revealed. Returns the cost of each action (details, ceo, marketing, ecommerce) for the selected stores.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| selection | object | yes | The stores to price. Pass either "ids", or "tab" with optional "filters" and "deselected". |
Check the status of contact searches you started in the dashboard, and your credit balance. Read only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| storeIds | array | yes | Store ids to check. |
Reveal data for stores. THIS SPENDS CREDITS. Before you call it, call getRevealCost for the same selection and tell the user the cost, or state the cost of 1 credit per store, then ask the user to confirm. Never call it without the confirmation. details unlocks the profile links, buying signals and phone. ceo, marketing and ecommerce start a decision-maker contact search (1 credit per store, +1 fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | What to reveal. |
| selection | object | yes | The stores to price. Pass either "ids", or "tab" with optional "filters" and "deselected". |
Create a signal set, or replace the criteria of an existing one. Without setId it creates a new set (the plan limit applies). With setId it updates that set and replaces all its signals, legacy categories and ICP filters with the new criteria. Conditions that you did not set (saved custom SQL conditions) stay on the set, joined with AND. Then the reply has preservedConditions, the number of these
| Parameter | Type | Required | Notes |
|---|---|---|---|
| criteria | object | yes | The criteria, in the same format as previewSignalSet. |
| setId | integer | no | Optional. The id of the set to update. Leave it out to create a set. |
| name | string | no | Optional. The name of a new set. |
Delete one of your signal sets. The set stops matching stores and disappears from listSignalSets and from the dashboard tabs. You cannot undo this. Ask the user to confirm before you call it. Say the name of the set in your question. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setId | integer | yes | The set id from listSignalSets. |
Create an empty watchlist. You can have at most 10 lists, including the blacklist. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The list name. |
Rename one of your watchlists. The blacklist cannot be renamed. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listId | integer | yes | The list id from listWatchlists. |
| name | string | yes | The new name. |
Delete one of your watchlists with all its domains. The blacklist cannot be deleted. Ask the user to confirm before you call it. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listId | integer | yes | The list id from listWatchlists. |
Remove one domain from a watchlist or from the blacklist. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listId | integer | yes | The list id from listWatchlists. |
| domain | string | yes | The exact domain as getWatchlist shows it. |
Add domains to a watchlist (merge, nothing is removed). THIS SPENDS CREDITS: 1 credit per domain that is new to the list. Before you call it, tell the user the cost of 1 credit per store and how many domains you will add, then ask the user to confirm. Never call it without the confirmation. If you have too few credits, the result shows the cost and your balance, and nothing is added. Paid plans on
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listId | integer | yes | The list id from listWatchlists. |
| domains | array | yes | The store domains to add, for example example.com. At most 50 per call. |
Set the outreach status of one store that you revealed. Use the storeId from a searchStores row. If you did not reveal the store, the tool returns an error. Use revealStores first. A store in a revealed group is accepted at no credit cost.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| storeId | integer | yes | The store id (the storeId field of a searchStores row). |
| status | string | yes | — |
Send a feedback message to the Ecommerce Leads team. Limit: 5 messages per hour.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | The feedback text. |
Export revealed stores as CSV text. Stores you have not revealed are skipped. The result holds the header row and at most 200 data rows; it says when it cut the rows. For a larger export, narrow the selection or download the file in the dashboard. Paid plans only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| selection | object | yes | The stores to price. Pass either "ids", or "tab" with optional "filters" and "deselected". |
| visibleColumns | array | no | Optional. The column names to export. Leave it out for all columns. |
Free
$0 forever
- 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 Ecommerce Leads or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.1.1 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest9d6e897c67232206064bcdcb3d93e0174a378e1d6cfa50b3734ebdad9346b094
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| lookupStore | no tags | |
| searchStores | untrusted-input | untrusted-input: keyword "fetch" |
| getStoreChart | no tags | |
| listSignalSets | no tags | |
| getSignalSet | no tags | |
| previewSignalSet | no tags | |
| listWatchlists | no tags | |
| getWatchlist | no tags | |
| getRevealCost | no tags | |
| getRevealStatus | no tags | |
| revealStores | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| saveSignalSet | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| deleteSignalSet | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| createWatchlist | state-write | state-write: declares readOnlyHint: false |
| renameWatchlist | state-write | state-write: declares readOnlyHint: false |
| deleteWatchlist | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| removeFromWatchlist | state-write | state-write: declares readOnlyHint: false |
| addToWatchlist | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| updateOutreachStatus | state-write | state-write: declares readOnlyHint: false |
| sendFeedback | state-write | state-write: declares readOnlyHint: false |
| exportStores | untrusted-input | untrusted-input: keyword "download" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9d6e897c67232206
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.1.1.
1.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Ecommerce Leads can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.