linkora-source
Registry code: e36f4e12d9ee8e2c
Linkora Source is a China-based sourcing service in Jinhua, Zhejiang, for overseas B2B buyers: supplier verification, factory audits, pre-shipment inspection and full order coordination, with published rates. Buyers pay factories directly; Linkora Source never holds order money.
Use get_company_profile or list_services to decide whether a buyer's need is in scope, get_pricing or estimate_fees for cost, list_buyer_types to match the buyer's situation, and search_guides or get_faq to answer process questions with a citable URL. Every figure is the one published on https://linkorasource.com; cite…
- endpoint
- https://linkorasource.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is linkora-source live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
- Is linkora-source free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does linkora-source have?
- 8 tools: estimate_fees, search_guides, list_buyer_types, prepare_sourcing_brief, list_services, get_pricing, get_faq, get_company_profile.
- Is linkora-source safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 98.7%· all time 98.7%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get china sourcing service pricing
- estimate factory audit and inspection fees
- search sourcing guides
- prepare a sourcing brief
- takes → gives
- text, data → data, text
- tools
- 8 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_services reads open 6h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_pricing reads open 6h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_faq reads open 3h ago
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.
{ "type": "object", "properties": { "query": { "type": "string", "description": "Optional keyword, e.g. 'NDA', 'payment', 'failed inspection'." } }, "additionalProperties": false }arguments 10 linesget_company_profile reads open 24h ago
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesestimate_fees reads unknown 24h ago
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.
{ "type": "object", "properties": { "order_value_usd": { "type": "number", "minimum": 0, "description": "Order value in USD, for the full-engagement commission." }, "inspection_man_days": { "type": "number", "minimum": 0, "description": "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": { "type": "number", "minimum": 0, "description": "Number of basic factory audits (one day on site each)." }, "extra_audit_man_days": { "type": "number", "minimum": 0, "description": "Additional audit man-days beyond the basic scope." }, "beyond_100km_of_jinhua": { "type": "boolean", "description": "True if the factory is more than 100 km from Jinhua, Zhejiang (for example in Guangdong)." }, "supplier_verifications": { "type": "number", "minimum": 0, "description": "Number of suppliers to verify." } }, "additionalProperties": false }arguments 35 linessearch_guides reads unknown 6h ago
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.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "Maximum results (default 5)." }, "query": { "type": "string", "minLength": 3, "description": "What the buyer is asking about, in English." } }, "additionalProperties": false }arguments 20 lineslist_buyer_types reads unknown never probed
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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesprepare_sourcing_brief reads unknown 24h ago
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.
{ "type": "object", "required": [ "product_category", "target_market", "brief" ], "properties": { "brief": { "type": "string", "maxLength": 1500, "minLength": 30, "description": "Product, specifications, quantity, timing, known suppliers and what needs to be verified or decided. No personal contact details." }, "language": { "enum": [ "en", "zh" ], "type": "string", "description": "Form language (default en)." }, "primary_need": { "enum": [ "sourcing", "supplier-verification", "factory-audit", "quality-inspection", "delivery-coordination" ], "type": "string" }, "target_market": { "type": "string", "maxLength": 120, "minLength": 2, "description": "Where the goods will be sold, e.g. 'United States, Amazon FBA'." }, "order_value_band": { "enum": [ "under-5k", "5k-25k", "25k-100k", "over-100k", "evaluating" ], "type": "string", "description": "Optional; only used to work out the commission band." }, "product_category": { "type": "string", "maxLength": 160, "minLength": 2, "description": "e.g. 'Stainless steel kitchenware'." } }, "additionalProperties": false }arguments 58 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide36f4e12d9ee8e2c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e36f4e12d9ee8e2c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e36f4e12d9ee8e2c?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.