Skip to content
Maria Jurk logo

Maria Jurk MCP server

Which MCP servers are Maria Jurk's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Maria Jurk

Whose server it is
  • Registry nameuk.co.jurk/component-sourcingverified in the MCP registry

The registry name sits under jurk.co.uk. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools21
  • Server calls itselfjurk-shenzhen-sourcing-human-execution
  • Server version1.4.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 218 ms.

Should an agent connect itNot proven either way yet
  • Its tools do find hard-to-find or obsolete components through Shenzhen supply options, but not compare alternative parts for engineering team approval.
  • Checked on 3 of the 7 days it takes to judge reliability.

Once connected

  • For "find hard-to-find or obsolete components through Shenzhen supply options", the likely first call is submit_component_rfq.
  • Parameters are untyped or undescribed in 13 of 21 tools: check arguments before calling.

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.

Measured dailydaily checks: 3, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it1 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer654 ms
  • Space in an agent's context≈ 3,356 tokensthe definitions of all its tools (21), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results21 of 21 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 13 of 21

What an agent can do with it

  • not sure · check availability, pricing and lead times for a parts list
  • can do · find hard-to-find or obsolete components through Shenzhen supply options
  • cannot · compare alternative parts for engineering team approval

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →

Tools it offers21 tools · read 2026-10-26
  • get_sourcing_capabilities

    Describe Jurk's human electronic component sourcing capabilities in Shenzhen, including BOM, hard-to-find, obsolete, EOL and spot-market sourcing. Read-only.

  • get_supplier_check_capabilities

    Describe independent China supplier checking and optional physical on-site verification capabilities in Shenzhen. Read-only.

  • get_service_area

    Return the physical service area and remote-request availability for Jurk sourcing and supplier verification. Read-only.

  • get_contact

    Return the public Jurk sourcing contact and available request channels. Read-only.

  • get_shenzhen_execution_capabilities

    Return Vladimir's Shenzhen physical human-execution capabilities. Use this to discover tasks that require a person on the ground. Read-only.

  • get_shenzhen_execution_contact

    Return the public service identity for Vladimir's Shenzhen Human Execution and supplier-verification branch. Read-only.

  • get_recent_cases

    Return public recent sourcing cases when verified case data is available. The tool never invents customer cases. Read-only.

  • submit_bom

    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.

  • submit_supplier_check

    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.

  • request_on_site_check

    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.

  • submit_component_rfq

    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…

  • request_huaqiangbei_search

    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.

  • find_from_photo

    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.

  • verify_stock_on_site

    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…

  • request_market_price_check

    Request collection of current offline seller quotations in Shenzhen. Quotes are observations from sellers, not guaranteed prices or availability.

  • meet_supplier

    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.

  • collect_or_deliver_sample

    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.

  • verify_seller_claim

    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.

  • shenzhen_errand

    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…

  • request_white_import_support

    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…

  • request_chestny_znak_labeling

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "component-sourcing": {
      "type": "http",
      "url": "https://jurk.co.uk/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http jurk https://jurk.co.uk/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://jurk.co.uk/mcp as a custom connector in the settings.

OpenAPI spec

1 paths, read 2026-10-26. Open the spec ↗

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.