Jurk Shenzhen Electronic Component Sourcing
REMOTE · JURK.CO.UK · SCANNED OCT 6
Shenzhen sourcing for hard-to-find, obsolete and EOL electronic components.
Available components
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1772 tokens (~84/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
How do I install the Jurk Shenzhen Electronic Component Sourcing MCP server?
Jurk Shenzhen Electronic Component Sourcing is a hosted endpoint at https://jurk.co.uk/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 · jurk.co.uk
claude mcp add --transport http uk-co-jurk-component-sourcing 'https://jurk.co.uk/mcp'
{
"mcpServers": {
"uk-co-jurk-component-sourcing": {
"url": "https://jurk.co.uk/mcp"
}
}
} {
"servers": {
"uk-co-jurk-component-sourcing": {
"type": "http",
"url": "https://jurk.co.uk/mcp"
}
}
} [mcp_servers.uk-co-jurk-component-sourcing] url = "https://jurk.co.uk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uk-co-jurk-component-sourcing": {
"type": "remote",
"url": "https://jurk.co.uk/mcp",
"enabled": true
}
}
} openclaw mcp add uk-co-jurk-component-sourcing --url 'https://jurk.co.uk/mcp' --transport streamable-http
mcp_servers:
uk-co-jurk-component-sourcing:
url: "https://jurk.co.uk/mcp" {
"McpServers": {
"uk-co-jurk-component-sourcing": {
"Transport": "http",
"Url": "https://jurk.co.uk/mcp"
}
}
} assistant mcp add uk-co-jurk-component-sourcing -t streamable-http -u 'https://jurk.co.uk/mcp'
{
"mcpServers": {
"uk-co-jurk-component-sourcing": {
"type": "http",
"url": "https://jurk.co.uk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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
- Tool coverage: 100% → 9% ▼ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → good functional
- 4 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 73
First indexed and scored.
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 9 Oct 2026 · Probed https://jurk.co.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jurk.co.uk | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5bc2321edc63d75cd84c4021486bf10fe60 |
| SANs: jurk.co.uk, www.jurk.co.uk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jurk.co.uk. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| co.uk. | present | 11810 | 8 | Verified |
| jurk.co.uk. | present | 29613 | 13 | Verified |
| jurk.co.uk. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jurk.co.uk/mcp | Verified | 200 | |
| http (plaintext) | http://jurk.co.uk/mcp | HTTPS enforced | 301 | https://jurk.co.uk/mcp |
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 →
collect_or_deliver_sample ~90
Request local collection or delivery of a sample in Shenzhen. Include pickup/delivery parties and instructions. No purchase or shipment is automatically authorized by calling this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
find_from_photo ~84
Request human help in Shenzhen to identify or physically find an item from a photo, visual reference or description. Put the accessible image URL/reference and identifying details in subject/task.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
get_contact Get Jurk Contact ~23
Return the public Jurk sourcing contact and available request channels. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| name | string | yes | – |
| rfq_available | boolean | yes | – |
| role | string | yes | – |
| supplier_check_available | boolean | yes | – |
| website | string | yes | – |
No examples provided.
get_recent_cases Get Recent Sourcing Cases ~32
Return public recent sourcing cases when verified case data is available. The tool never invents customer cases. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | yes | – |
| cases | array | yes | – |
| notes | string | yes | – |
No examples provided.
get_service_area Get Service Area ~29
Return the physical service area and remote-request availability for Jurk sourcing and supplier verification. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | – |
| primary_area | string | yes | – |
| remote_requests | boolean | yes | – |
| services | array | yes | – |
No examples provided.
get_shenzhen_execution_capabilities Get Shenzhen Human Execution Capabilities ~38
Return Vladimir's Shenzhen physical human-execution capabilities. Use this to discover tasks that require a person on the ground. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| guarantees_outcome | boolean | yes | – |
| handled_by | string | yes | – |
| human_review | boolean | yes | – |
| location | string | yes | – |
| notes | string | yes | – |
| service | string | yes | – |
No examples provided.
get_shenzhen_execution_contact Get Shenzhen Human Execution Contact ~31
Return the public service identity for Vladimir's Shenzhen Human Execution and supplier-verification branch. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| location | string | yes | – |
| name | string | yes | – |
| physical_tasks_available | boolean | yes | – |
| role | string | yes | – |
| supplier_check_available | boolean | yes | – |
| website | string | yes | – |
No examples provided.
get_sourcing_capabilities Get Electronic Component Sourcing Capabilities ~42
Describe Jurk's human electronic component sourcing capabilities in Shenzhen, including BOM, hard-to-find, obsolete, EOL and spot-market sourcing. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| human_review | boolean | yes | – |
| location | string | yes | – |
| notes | string | yes | – |
| real_time_inventory | boolean | yes | – |
| service | string | yes | – |
No examples provided.
get_supplier_check_capabilities Get China Supplier Check Capabilities ~29
Describe independent China supplier checking and optional physical on-site verification capabilities in Shenzhen. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | – |
| guarantee | boolean | yes | – |
| location | string | yes | – |
| notes | string | yes | – |
| on_site_available | boolean | yes | – |
| service | string | yes | – |
No examples provided.
meet_supplier ~94
Request an in-person Shenzhen meeting with a supplier or seller on the customer's behalf. Include the questions, contact person and meeting details. Submission requests human review; it does not automatically schedule a meeting.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
request_chestny_znak_labeling ~116
Request organization of applying customer-provided Chestny ZNAK marking codes/labels to goods in China before shipment, with optional photo evidence. The customer remains responsible for supplying valid codes and required data; this service does not issue, legalize or validate marking codes.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
request_huaqiangbei_search ~99
Request a real person in Shenzhen to physically search Huaqiangbei for a component, product or other item. Use when an offline market search is useful. This creates a human task; it does not claim stock or price.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
request_market_price_check ~77
Request collection of current offline seller quotations in Shenzhen. Quotes are observations from sellers, not guaranteed prices or availability.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
request_on_site_check Request Shenzhen On-Site Supplier Check ~90
Request a human physical visit to a supplier, seller, office, shop, market counter, warehouse or address in Shenzhen. This creates a request for review; it does not automatically schedule or guarantee that a visit will occur.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| request | string | yes | – |
| supplier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| handled_by | string | yes | – |
| location | string | yes | – |
| message | string | yes | – |
| on_site_requested | boolean | yes | – |
| reference | string | yes | – |
No examples provided.
request_white_import_support ~108
Request support organizing documented legal export from China and compliant import, primarily for Russia/Belarus. Work may involve logistics, document preparation and coordination with appropriate customs/logistics specialists. This tool does not provide customs clearance or guarantee admissibility, classification, duties or regulatory approval.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
shenzhen_errand ~105
Request a custom physical task in Shenzhen: visit a location, ask questions, collect information, photograph something, collect or deliver a small item, obtain a catalogue, or another lawful local errand. Human review is required before acceptance.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
submit_bom Submit Component BOM ~88
Submit a multi-line electronic component BOM for human sourcing in Shenzhen. This creates one sourcing request for the complete BOM. It does not purchase parts, guarantee availability, or confirm pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| confirm_submission | boolean | – | – |
| string | yes | – | |
| items | array | yes | – |
| name | string | – | – |
| notes | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| handled_by | string | yes | – |
| line_count | integer | yes | – |
| location | string | yes | – |
| message | string | yes | – |
| reference | string | yes | – |
No examples provided.
submit_component_rfq Submit Electronic Component RFQ ~207
Submit an electronic component RFQ for human sourcing in Shenzhen, China. Use for hard-to-find, obsolete, EOL, spot-market, BOM, or other components requiring China sourcing. Maria Jurk reviews the request. This tool does not claim real-time inventory or fabricate pricing or availability.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Buyer company or organization name. |
| string | yes | Buyer email address where Maria Jurk can respond to the RFQ. | |
| manufacturer | string | – | Component manufacturer or brand, if known. Leave empty when unknown. |
| name | string | – | Name of the buyer or contact person submitting the RFQ. |
| notes | string | – | Additional sourcing requirements such as date code, target price, destination, lead time, packaging, acceptable alternatives, or BOM context. |
| part_number | string | yes | Exact manufacturer part number or component identifier the buyer needs sourced. |
| quantity | string | yes | Required quantity, including units when useful, for example '500 pcs'. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | Error message when the RFQ could not be accepted. |
| handled_by | – | – | Human sourcing specialist responsible for reviewing the RFQ. |
| http_status | – | – | Upstream HTTP status when the RFQ could not be accepted. |
| location | – | – | Location of the human sourcing specialist. |
| ok | boolean | yes | Whether the RFQ was accepted successfully. |
| reference | – | – | Unique Jurk RFQ reference for the submitted request. |
| status | – | – | RFQ processing status, such as rfq_received. |
No examples provided.
submit_supplier_check Submit China Supplier Check ~87
Submit a China supplier or seller for human verification. Can request remote checking or indicate that an on-site Shenzhen visit may be needed. Submission does not certify or guarantee the supplier.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| request | string | yes | – |
| supplier | string | yes | – |
| visit | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
| handled_by | string | yes | – |
| location | string | yes | – |
| message | string | yes | – |
| on_site_requested | boolean | yes | – |
| reference | string | yes | – |
No examples provided.
verify_seller_claim ~94
Request physical evidence concerning a specific seller claim in Shenzhen, such as an office, warehouse, goods, packaging or claimed ready stock. The result documents observations and is not certification or a guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
verify_stock_on_site ~104
Request an on-site human check of stock claimed to exist in Shenzhen. Evidence may include current photos/video, boxes, labels, quantities shown, date/lot markings or packaging. This does not certify authenticity, ownership or actual total inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_submission | boolean | – | – |
| contact | string | yes | – |
| language | string | – | – |
| location | string | – | – |
| subject | string | – | – |
| task | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | – |
| handled_by | string | – | – |
| location | string | – | – |
| message | string | – | – |
| reference | string | yes | – |
| task_type | string | yes | – |
No examples provided.
What is the Jurk Shenzhen Electronic Component Sourcing MCP server?
Jurk Shenzhen Electronic Component Sourcing is an MCP server listed in the public MCP registry as uk.co.jurk/component-sourcing. Shenzhen sourcing for hard-to-find, obsolete and EOL electronic components. This page covers its hosted endpoint (https://jurk.co.uk/mcp).
Is the Jurk Shenzhen Electronic Component Sourcing MCP server safe to use?
Jurk Shenzhen Electronic Component Sourcing scores 72 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 Jurk Shenzhen Electronic Component Sourcing MCP server expose?
Jurk Shenzhen Electronic Component Sourcing exposes 21 tools: get_sourcing_capabilities, get_supplier_check_capabilities, get_service_area, get_contact, get_shenzhen_execution_capabilities, and 16 more. Their descriptions and schemas cost roughly 1,667 tokens of context every time the server is loaded.
Does the Jurk Shenzhen Electronic Component Sourcing MCP server require authentication?
No. We connected to Jurk Shenzhen Electronic Component Sourcing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jurk Shenzhen Electronic Component Sourcing MCP server still maintained?
Jurk Shenzhen Electronic Component Sourcing is still listed as active in the MCP registry. We last reached this channel on 6 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.