Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/sourcelens

NPM · @RENETURCIOS/SOURCELENS · 2 COMPONENTS

China sourcing, inspection and supplier verification: rates, fees, guides.

70 Trust /100

Last scanned (13 hours ago)

Scores higher than 41% of npm servers

Category E-commerce

Trust breakdown (7 categories)

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
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 808 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

Changelog

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.

  • 16 Nov 26 70

    First indexed and scored.

Diagnostics

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/@reneturcios/sourcelens@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 →

MCP tools · 8 exposed · ~808 tokens

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 →

Tool Tokens
estimate_fees ~205

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.

NameTypeReqDescription
basic_factory_auditsnumber–Number of basic factory audits (one day on site each).
beyond_100km_of_jinhuaboolean–True if the factory is more than 100 km from Jinhua, Zhejiang (for example in Guangdong).
extra_audit_man_daysnumber–Additional audit man-days beyond the basic scope.
inspection_man_daysnumber–Inspection man-days. One SKU with standard sampling is typically one man-day; three SKUs on one order is one to two.
order_value_usdnumber–Order value in USD, for the full-engagement commission.
supplier_verificationsnumber–Number of suppliers to verify.

No output schema declared.

No examples provided.

get_company_profile ~68

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_faq ~82

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.

NameTypeReqDescription
querystring–Optional keyword, e.g. 'NDA', 'payment', 'failed inspection'.

No output schema declared.

No examples provided.

get_pricing ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_buyer_types ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_services ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

prepare_sourcing_brief ~183

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 arguments.

NameTypeReqDescription
briefstringyesProduct, specifications, quantity, timing, known suppliers and what needs to be verified or decided. No personal contact details.
languagestring–Form language (default en).
order_value_bandstring–Optional; only used to work out the commission band.
primary_needstring––
product_categorystringyese.g. 'Stainless steel kitchenware'.
target_marketstringyesWhere the goods will be sold, e.g. 'United States, Amazon FBA'.

No output schema declared.

No examples provided.

search_guides ~92

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.

NameTypeReqDescription
limitinteger–Maximum results (default 5).
querystringyesWhat the buyer is asking about, in English.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/sourcelens MCP server?

io.github.CloudCorpRecords/sourcelens runs locally as an npm package, launched with npx -y @reneturcios/sourcelens mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/sourcelens

# add to Claude Code
claude mcp add cloudcorprecords-sourcelens -- npx -y @reneturcios/sourcelens mcp
Common questions

What is the io.github.CloudCorpRecords/sourcelens MCP server?

io.github.CloudCorpRecords/sourcelens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sourcelens. China sourcing, inspection and supplier verification: rates, fees, guides. This page covers its npm package (@reneturcios/sourcelens).

Is the io.github.CloudCorpRecords/sourcelens MCP server safe to use?

io.github.CloudCorpRecords/sourcelens scores 70 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 io.github.CloudCorpRecords/sourcelens MCP server expose?

io.github.CloudCorpRecords/sourcelens exposes 8 tools: get_company_profile, list_services, get_pricing, estimate_fees, list_buyer_types, and 3 more. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/sourcelens MCP server still maintained?

io.github.CloudCorpRecords/sourcelens 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 io.github.CloudCorpRecords/sourcelens MCP server under?

io.github.CloudCorpRecords/sourcelens 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 io.github.CloudCorpRecords/sourcelens MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/sourcelens, 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 io.github.CloudCorpRecords/sourcelens: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.