Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
UCP Checker 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
Check any domain for UCP support and resolve verified UCP storefronts. Read-only, keyless.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ucp-checker-router-mcp https://ucpchecker.com/mcp
# 2 — ask your agent for something these tools do
# list-stores, list-categories, check-domain and 5 more
UCP Checker 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 ucp-checker-router-mcp https://ucpchecker.com/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.
8 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.
List verified UCP storefronts across every platform, best-evidenced first. Use when the user wants to browse stores — e.g., "what stores can I shop at?" or "show me Wix stores". To find stores that sell something, prefer search-all. Each store carries what we have actually observed about it, not what it claims: - transactable — declares checkout and we have read its ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | Restrict to one platform, e.g. "wix", "shopify", "woocommerce". |
| category | string | no | Optional. Limit to the deeply audited stores in one category (e.g., "footwear"); see list-categories. Most browsing is better without it. |
| limit | integer | no | Maximum number of stores to return (default: 10, max: 50) |
List store categories with store counts. Categories exist only for the deeply audited subset of verified stores, so this is a way to browse, not the whole index: list-stores and search-all cover every verified storefront. Sorted by number of stores (most first).
No parameter schema on file.
Check if a domain supports Universal Commerce Protocol (UCP). Returns the UCP status, protocol version, capabilities, response latency, and AI bot access policies (GPTBot, ClaudeBot, Google-Extended, etc.). If the store's edge rate-limits the live attempt, the result says so and reports the last OBSERVED state and when it was observed — an unobserved attempt is never pres
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The domain to check for UCP support (e.g., "shopify.com", "example.com"). Protocol, www prefix, and paths are automatically removed. |
Discover available shopping tools on a UCP-enabled store. Connects to the store's MCP endpoint and lists all available tools (search, cart, shipping, etc.). Use this to understand what a store supports before shopping. Example: domain: "allbirds.com"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain to discover (e.g., "allbirds.com") |
Search for products on any UCP-enabled Shopify store. Searches the store's live product catalog via UCP/MCP and returns matching products with titles, prices, variants, and images. Examples: - domain: "allbirds.com", query: "tree topper" - domain: "gymshark.com", query: "hoodie"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain (e.g., "allbirds.com", "gymshark.com"). Must be a UCP-enabled Shopify store. |
| query | string | yes | Product search term (e.g., "tree topper", "wool runners", "hoodie") |
| country | string | no | ISO country code for localized pricing/inventory (e.g., "US", "GB", "CA"). Optional — defaults to store default. |
Search for products across verified UCP stores at once. Fans the query out, concurrently, to the stores whose observed catalogue best matches it, and returns results grouped by store with each store's UCP score and evidence. Rare query words count for more than common ones. If no store's catalogue matches well enough, it searches no one and says "No strong match", naming t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Product search term (e.g., "running shoes", "hoodie") |
| category | string | no | Optional. Limit the fan-out to the deeply audited stores in one category (e.g., "footwear"); see list-categories. Most queries search better without it. |
| country | string | no | ISO country code for localized pricing (e.g., "US", "GB"). Optional. |
| maxStores | integer | no | Maximum number of stores to search (default: 5, max: 10) |
Search store policies on any UCP-enabled Shopify store. Query return policies, shipping policies, refund policies, privacy policies, terms of service, or any other store policy. Returns the matching policy text. Use this when a user asks about a store's policies before or after purchase — e.g., "what is the return policy?", "do they offer free shipping?", "refund window?"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain (e.g., "allbirds.com") |
| query | string | yes | Policy search term (e.g., "return policy", "shipping", "refund window", "privacy policy") |
Get full product details including variant IDs from a UCP-enabled store. Use after search-catalog to see a product's full declared detail, including its variants. Pass the Product ID from search results to get all variants with their IDs. Example: domain: "allbirds.com", productId: "gid://shopify/Product/123456"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The store domain (e.g., "allbirds.com") |
| productId | string | yes | The product ID from search-catalog results (e.g., "gid://shopify/Product/123456") |
- 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 UCP Checker 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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list-stores | untrusted-input | untrusted-input: keyword "browse" |
| list-categories | no tags | |
| check-domain | no tags | |
| discover-store | no tags | |
| search-catalog | no tags | |
| search-all | no tags | |
| search-policies | no tags | |
| get-product-details | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 2.0.0.
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 UCP Checker 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.