Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Jurk Shenzhen Electronic Component Sourcing is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Shenzhen sourcing for hard-to-find, obsolete and EOL electronic components.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jurk-shenzhen-electronic-component-sourcing-mcp https://jurk.co.uk/mcp
# 2 — ask your agent for something these tools do
# get_sourcing_capabilities, get_supplier_check_capabilities, get_service_area and 18 more
Jurk Shenzhen Electronic Component Sourcing costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http jurk-shenzhen-electronic-component-sourcing-mcp https://jurk.co.uk/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Describe Jurk's human electronic component sourcing capabilities in Shenzhen, including BOM, hard-to-find, obsolete, EOL and spot-market sourcing. Read-only.
No parameter schema on file.
Describe independent China supplier checking and optional physical on-site verification capabilities in Shenzhen. Read-only.
No parameter schema on file.
Return the physical service area and remote-request availability for Jurk sourcing and supplier verification. Read-only.
No parameter schema on file.
Return the public Jurk sourcing contact and available request channels. Read-only.
No parameter schema on file.
Return Vladimir's Shenzhen physical human-execution capabilities. Use this to discover tasks that require a person on the ground. Read-only.
No parameter schema on file.
Return the public service identity for Vladimir's Shenzhen Human Execution and supplier-verification branch. Read-only.
No parameter schema on file.
Return public recent sourcing cases when verified case data is available. The tool never invents customer cases. Read-only.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | — |
| string | yes | — | |
| name | string | no | — |
| company | string | no | — |
| notes | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier | string | yes | — |
| request | string | yes | — |
| contact | string | yes | — |
| visit | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier | string | yes | — |
| request | string | yes | — |
| contact | string | yes | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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'. |
| string | yes | Buyer email address where Maria Jurk can respond to the RFQ. | |
| manufacturer | string | no | Component manufacturer or brand, if known. Leave empty when unknown. |
| name | string | no | Name of the buyer or contact person submitting the RFQ. |
| company | string | no | Buyer company or organization name. |
| notes | string | no | Additional sourcing requirements such as date code, target price, destination, lead time, packaging, acceptable alternatives, or BOM context. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
Request collection of current offline seller quotations in Shenzhen. Quotes are observations from sellers, not guaranteed prices or availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| contact | string | yes | — |
| subject | string | no | — |
| location | string | no | — |
| language | string | no | — |
| confirm_submission | boolean | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jurk Shenzhen Electronic Component Sourcing or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Jurk Shenzhen Electronic Component Sourcing can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.