Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
Sourcelens 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
China sourcing, inspection and supplier verification: rates, fees, guides.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user sourcelens-mcp '--' npx -y @reneturcios/sourcelens mcp
# 2 — ask your agent for something these tools do
# get_company_profile, list_services, get_pricing and 5 more
Sourcelens 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. This one runs on your machine: your client starts Sourcelens as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user sourcelens-mcp '--' npx -y @reneturcios/sourcelens mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
8 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Who Linkora Source is, where it operates (Jinhua, Zhejiang, China), how money flows (buyer pays the factory directly), the buyer types it serves, what it explicitly does not do, and how to contact it. Start here to decide whether a buyer's need is in scope.
No parameter schema on file.
The four services — China sourcing agent, product inspection in China, factory audit in China and China supplier verification — each with what happens, what the buyer provides, what the buyer receives, cost and timing, and what is not included.
No parameter schema on file.
Published prices in USD: per-job checks (supplier verification, inspection per man-day, basic factory audit), commission bands for a full order engagement, the monthly retainer, worked examples, exclusions, travel and payment conditions.
No parameter schema on file.
Arithmetic on the published rates: per-job checks and/or the commission for a given order value. Returns line items, the commission band, payment timing and exclusions. An estimate, not a quotation; travel beyond 100 km of Jinhua is flagged rather than priced.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| order_value_usd | number | no | Order value in USD, for the full-engagement commission. |
| supplier_verifications | number | no | Number of suppliers to verify. |
| inspection_man_days | number | no | Inspection man-days. One SKU with standard sampling is typically one man-day; three SKUs on one order is one to two. |
| basic_factory_audits | number | no | Number of basic factory audits (one day on site each). |
| extra_audit_man_days | number | no | Additional audit man-days beyond the basic scope. |
| beyond_100km_of_jinhua | boolean | no | True if the factory is more than 100 km from Jinhua, Zhejiang (for example in Guangdong). |
The six buyer types served (Amazon sellers, retail brands, DTC brands, wholesale importers, OEM/ODM projects, promotional-product buyers), each with explicit 'fits when' and 'does not fit when' conditions and the page URL. Use it to match a buyer's situation without inference.
No parameter schema on file.
Search Linkora Source's guides and comparisons (supplier verification, pre-shipment inspection, factory audits, Incoterms, samples, moulds, FBA labelling and more). Returns titles, URLs, a direct answer and the last-updated date, for citing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the buyer is asking about, in English. |
| limit | integer | no | Maximum results (default 5). |
Published answers on scope, minimum order, payment, failed inspections, refunds, NDAs, samples, cover when the founder is away, and what is not offered (freight, customs, warehousing, design). Optionally filter by a keyword.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional keyword, e.g. 'NDA', 'payment', 'failed inspection'. |
When a buyer wants a quotation, turn their requirement into a pre-filled brief link for the Linkora Source form, plus WhatsApp and email alternatives. Nothing is submitted: the buyer opens the link, adds their own name, company and email, and sends it. Never include personal details in the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_category | string | yes | e.g. 'Stainless steel kitchenware'. |
| target_market | string | yes | Where the goods will be sold, e.g. 'United States, Amazon FBA'. |
| brief | string | yes | Product, specifications, quantity, timing, known suppliers and what needs to be verified or decided. No personal contact details. |
| primary_need | string | no | — |
| order_value_band | string | no | Optional; only used to work out the commission band. |
| language | string | no | Form language (default en). |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Sourcelens 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
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
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
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 Sourcelens 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.