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.

Linkora Source

REMOTE · LINKORASOURCE.COM · SCANNED OCT 7

China sourcing, inspection and supplier verification: published rates, scope and fee estimates.

+3 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 997 tokens (~124/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Linkora Source MCP server?

Linkora Source is a hosted endpoint at https://linkorasource.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · linkorasource.com

# add to Claude Code
claude mcp add --transport http com-linkorasource-sourcing 'https://linkorasource.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-linkorasource-sourcing": {
      "url": "https://linkorasource.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-linkorasource-sourcing": {
      "type": "http",
      "url": "https://linkorasource.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-linkorasource-sourcing]
url = "https://linkorasource.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-linkorasource-sourcing": {
      "type": "remote",
      "url": "https://linkorasource.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-linkorasource-sourcing --url 'https://linkorasource.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-linkorasource-sourcing:
    url: "https://linkorasource.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-linkorasource-sourcing": {
      "Transport": "http",
      "Url": "https://linkorasource.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-linkorasource-sourcing -t streamable-http -u 'https://linkorasource.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-linkorasource-sourcing": {
      "type": "http",
      "url": "https://linkorasource.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 6 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 29 Sept 26 74

    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 8 Oct 2026 · Probed https://linkorasource.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=linkorasource.com CN=WE1,O=Google Trust Services,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA256 bea5437ad979e48a135361c41899fcaf
SANs: linkorasource.com, *.linkorasource.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of linkorasource.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
linkorasource.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://linkorasource.com/mcp Verified 200
http (plaintext) http://linkorasource.com/mcp HTTPS enforced 301 https://linkorasource.com/mcp
MCP tools · 8 exposed · ~806 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 ~53

The four services — China sourcing (full order engagement), quality inspection, factory audit and 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.

Common questions

What is the Linkora Source MCP server?

Linkora Source is an MCP server listed in the public MCP registry as com.linkorasource/sourcing. China sourcing, inspection and supplier verification: published rates, scope and fee estimates. This page covers its hosted endpoint (https://linkorasource.com/mcp).

Is the Linkora Source MCP server safe to use?

Linkora Source scores 77 out of 100 on VerifyMCP. 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 Linkora Source MCP server expose?

Linkora Source exposes 8 tools: get_company_profile, list_services, get_pricing, estimate_fees, list_buyer_types, and 3 more. Their descriptions and schemas cost roughly 806 tokens of context every time the server is loaded.

Does the Linkora Source MCP server require authentication?

No. We connected to Linkora Source without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Linkora Source MCP server still maintained?

Linkora Source is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.