# Linkora Source (remote · linkorasource.com)

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

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `linkorasource.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource.md), [page](https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource)

## Channel facts

- Endpoint: `https://linkorasource.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

### Claude

```bash
claude mcp add --transport http com-linkorasource-sourcing 'https://linkorasource.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-linkorasource-sourcing": {
      "url": "https://linkorasource.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-linkorasource-sourcing": {
      "type": "http",
      "url": "https://linkorasource.com/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-linkorasource-sourcing --url 'https://linkorasource.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-linkorasource-sourcing:
    url: "https://linkorasource.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-linkorasource-sourcing": {
      "Transport": "http",
      "Url": "https://linkorasource.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-linkorasource-sourcing -t streamable-http -u 'https://linkorasource.com/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-06 (score 77, +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.

### 2026-10-03 (score 76, +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.

### 2026-10-01 (score 75, +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.

### 2026-09-30 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-29 (score 74)

First indexed and scored.

## MCP tools (8)

### `get_company_profile` (~68 tokens)

Company profile

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.

### `list_services` (~53 tokens)

Services and scope

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.

### `get_pricing` (~53 tokens)

Published rates and payment terms

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.

### `estimate_fees` (~205 tokens)

Estimate fees from published rates

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.

Input parameters:

- `basic_factory_audits` (number): Number of basic factory audits (one day on site each).
- `beyond_100km_of_jinhua` (boolean): True if the factory is more than 100 km from Jinhua, Zhejiang (for example in Guangdong).
- `extra_audit_man_days` (number): Additional audit man-days beyond the basic scope.
- `inspection_man_days` (number): Inspection man-days. One SKU with standard sampling is typically one man-day; three SKUs on one order is one to two.
- `order_value_usd` (number): Order value in USD, for the full-engagement commission.
- `supplier_verifications` (number): Number of suppliers to verify.

### `list_buyer_types` (~70 tokens)

Buyer types and fit

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.

### `search_guides` (~92 tokens)

Search guides

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.

Input parameters:

- `limit` (integer): Maximum results (default 5).
- `query` (string, required): What the buyer is asking about, in English.

### `get_faq` (~82 tokens)

Frequently asked questions

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.

Input parameters:

- `query` (string): Optional keyword, e.g. 'NDA', 'payment', 'failed inspection'.

### `prepare_sourcing_brief` (~183 tokens)

Prepare a sourcing brief

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.

Input parameters:

- `brief` (string, required): Product, specifications, quantity, timing, known suppliers and what needs to be verified or decided. No personal contact details.
- `language` (string): Form language (default en).
- `order_value_band` (string): Optional; only used to work out the commission band.
- `primary_need` (string)
- `product_category` (string, required): e.g. 'Stainless steel kitchenware'.
- `target_market` (string, required): Where the goods will be sold, e.g. 'United States, Amazon FBA'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource#diagnostics

## Score history

- 2026-10-07: 77
- 2026-10-06: 77
- 2026-10-04: 76
- 2026-10-03: 76
- 2026-10-02: 75
- 2026-10-01: 75
- 2026-09-30: 74
- 2026-09-29: 74

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

## Links

- Remote endpoint: https://linkorasource.com/mcp
- Website: https://linkorasource.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource.json
- HTML version of this page: https://verifymcp.io/servers/com-linkorasource-sourcing/linkorasource