
Linkora Source MCP server
Which servers in the official MCP registry are Linkora Source's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.linkorasource/sourcingverified in the MCP registry
The registry name sits under linkorasource.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools8
- Server calls itselflinkora-source
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 446 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer485 ms
- Space in an agent's context≈ 1,264 tokensthe definitions of all its tools (8), which an agent carries on every turn
- Tool definitionsA · 98 of 100
- Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 8
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_company_profileWho 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…
list_servicesThe 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…
get_pricingPublished 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.
estimate_feesArithmetic 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…
list_buyer_typesThe 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…
search_guidesSearch 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…
get_faqPublished 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.
prepare_sourcing_briefWhen 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"sourcing": {
"type": "http",
"url": "https://linkorasource.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http linkorasource https://linkorasource.com/mcpclaude.ai, ChatGPT and other clients: add https://linkorasource.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.