UCP Checker
REMOTE · UCPCHECKER.COM · SCANNED SEP 25
Check any domain for UCP support and resolve verified UCP storefronts. Read-only, keyless.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2417 tokens (~302/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the UCP Checker MCP server?
UCP Checker is a hosted endpoint at https://ucpchecker.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.
remote · ucpchecker.com
claude mcp add --transport http com-ucpchecker-ucp-checker 'https://ucpchecker.com/mcp'
{
"mcpServers": {
"com-ucpchecker-ucp-checker": {
"url": "https://ucpchecker.com/mcp"
}
}
} {
"servers": {
"com-ucpchecker-ucp-checker": {
"type": "http",
"url": "https://ucpchecker.com/mcp"
}
}
} [mcp_servers.com-ucpchecker-ucp-checker] url = "https://ucpchecker.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ucpchecker-ucp-checker": {
"type": "remote",
"url": "https://ucpchecker.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-ucpchecker-ucp-checker --url 'https://ucpchecker.com/mcp' --transport streamable-http
mcp_servers:
com-ucpchecker-ucp-checker:
url: "https://ucpchecker.com/mcp" {
"McpServers": {
"com-ucpchecker-ucp-checker": {
"Transport": "http",
"Url": "https://ucpchecker.com/mcp"
}
}
} assistant mcp add com-ucpchecker-ucp-checker -t streamable-http -u 'https://ucpchecker.com/mcp'
{
"mcpServers": {
"com-ucpchecker-ucp-checker": {
"type": "http",
"url": "https://ucpchecker.com/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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57.
- 16 Sept 26 0
- Schema quality: 274 → 302 ▼ functional
- Resource “verified-stores” was removed ▼ functional
- 15 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search-all” rewrote its description, which is the text the model reads security
- 14 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list-categories” rewrote its description, which is the text the model reads security
- Tool “search-all” rewrote its description, which is the text the model reads security
- Tool “check-domain” rewrote its description, which is the text the model reads security
- Tool “list-stores” rewrote its description, which is the text the model reads security
- Schema quality: 216 → 265 ▼ functional
- Schema quality: 216 → 256 ▼ functional
- “list-stores” added an optional parameter “platform” cosmetic
- “list-stores” reworded the description of “category” cosmetic
- “search-all” reworded the description of “category” cosmetic
- “list-stores” dropped the optional parameter “min_score” cosmetic
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 25 Sept 2026 · Probed https://ucpchecker.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ucpchecker.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a36446fd32ef9c1f0ed8f297990ddd80 |
| SANs: ucpchecker.com, *.ucpchecker.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ucpchecker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ucpchecker.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ucpchecker.com/mcp | Verified | 200 | |
| http (plaintext) | http://ucpchecker.com/mcp | HTTPS enforced | 301 | https://ucpchecker.com/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 →
check-domain Check Domain ~244
Check if a domain supports Universal Commerce Protocol (UCP). Returns the UCP status, manifest 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 presented as a verdict about the store. The domain is automatically normalized (removes protocol, www, paths). Examples: "shopify.com", "https://www.example.com/path" → "example.com" A negative result is information, not permission. It reports what UCP Checker has observed — it does not say a store cannot be used, and it is not a reason to stop. If a store matters to your task, try discover-store or connect to it directly regardless of what this returns.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check for UCP support (e.g., "shopify.com", "example.com"). Protocol, www prefix, and paths are automatically removed. |
No output schema declared.
No examples provided.
discover-store Discover Store ~88
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"
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The store domain to discover (e.g., "allbirds.com") |
No output schema declared.
No examples provided.
get-product-details Get Product Details ~129
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"
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
list-categories List Categories ~68
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-stores List Stores ~302
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 catalogue - `catalogued` — we have read its catalogue - `resolvable` — its endpoint resolves, we have not probed it yet - `declared` — a valid manifest, nothing observed beyond it Filter by `platform` (shopify, wix, woocommerce, bigcommerce, shopware…). `category` narrows to the smaller set of deeply audited stores (see list-categories), so leave it out unless the user asks for a category. Developer previews and staging hosts are not listed.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional. Limit to the deeply audited stores in one category (e.g., "footwear"); see list-categories. Most browsing is better without it. |
| limit | integer | – | Maximum number of stores to return (default: 10, max: 50) |
| platform | string | – | Restrict to one platform, e.g. "wix", "shopify", "woocommerce". |
No output schema declared.
No examples provided.
search-all Search All ~282
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 the words no store carries and the closest weak matches, so you can go to a store you know instead of rewording. Slow or failing stores are skipped. `category` narrows the fan-out to the smaller set of deeply audited stores; leave it out for most queries. Example: query: "mattress topper", maxStores: 5
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 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 | – | ISO country code for localized pricing (e.g., "US", "GB"). Optional. |
| maxStores | integer | – | Maximum number of stores to search (default: 5, max: 10) |
| query | string | yes | Product search term (e.g., "running shoes", "hoodie") |
No output schema declared.
No examples provided.
search-catalog Search Catalog ~177
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"
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO country code for localized pricing/inventory (e.g., "US", "GB", "CA"). Optional — defaults to store default. |
| 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") |
No output schema declared.
No examples provided.
search-policies Search Policies ~153
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?" Example: domain: "allbirds.com", query: "return policy"
| Name | Type | Req | Description |
|---|---|---|---|
| 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") |
No output schema declared.
No examples provided.
What is the UCP Checker MCP server?
UCP Checker is an MCP server listed in the public MCP registry as com.ucpchecker/ucp-checker. Check any domain for UCP support and resolve verified UCP storefronts. Read-only, keyless. This page covers its hosted endpoint (https://ucpchecker.com/mcp).
Is the UCP Checker MCP server safe to use?
UCP Checker scores 76 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 UCP Checker MCP server expose?
UCP Checker exposes 8 tools: list-stores, list-categories, check-domain, discover-store, search-catalog, and 3 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the UCP Checker MCP server require authentication?
No. We connected to UCP Checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UCP Checker MCP server still maintained?
UCP Checker is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.