UCP Checker MCP server
com.ucpchecker/ucp-checkerucpchecker.comstreamable-httpv2.0.0Scanned
Check any domain for UCP support and resolve verified UCP storefronts. Read-only, keyless.
8 tools: 2 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the UCP Checker MCP server can do
The UCP Checker MCP server is published by ucpchecker.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: check-domain and discover-store), but cannot delete data. 6 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 2.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 2Claude Code: ask
check-domainCheck if a domain supports Universal Commerce Protocol (UCP).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 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.
Annotations the server declares
- readOnlyHint: true
discover-storeDiscover available shopping tools on a UCP-enabled store.1 finding
Why it is in this group
- The name "discover-store" says "store": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "discover-store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "discover-store" says "store": a word for a change.
Description, as the server wrote it 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"
Annotations the server declares
- readOnlyHint: true
Only reads 6Show 6 read-only tools
get-product-detailsGet full product details including variant IDs from a UCP-enabled store.No findings
Why it is in this group
- The name "get-product-details" says "get": a word for reading.
Description, as the server wrote it 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"
Annotations the server declares
- readOnlyHint: true
list-categoriesList store categories with store counts.No findings
Why it is in this group
- The name "list-categories" says "list": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
list-storesList verified UCP storefronts across every platform, best-evidenced first.No findings
Why it is in this group
- The name "list-stores" says "list": a word for reading.
Description, as the server wrote it 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 profile, 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.
Annotations the server declares
- readOnlyHint: true
search-allSearch for products across verified UCP stores at once.No findings
Why it is in this group
- The name "search-all" says "search": a word for reading.
Description, as the server wrote it 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
Annotations the server declares
- readOnlyHint: true
search-catalogSearch for products on any UCP-enabled Shopify store.No findings
Why it is in this group
- The name "search-catalog" says "search": a word for reading.
Description, as the server wrote it 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"
Annotations the server declares
- readOnlyHint: true
search-policiesSearch store policies on any UCP-enabled Shopify store.No findings
Why it is in this group
- The name "search-policies" says "search": a word for reading.
Description, as the server wrote it 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"
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ucpchecker.com/mcp: tools/list returned 8 tools to an anonymous client, including check-domain (write), discover-store (write)
Findings
Matches of fixed checks, with the text they matched.
- Warndiscover-store
The server marks "discover-store" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "discover-store" says "store": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:list-storesOnly readsinputSchema
Install
Pinned to version 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ucp-checker https://ucpchecker.com/mcpclaude mcp add --transport http ucp-checker https://ucpchecker.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ucp-checker__list-stores",
"mcp__ucp-checker__list-categories",
"mcp__ucp-checker__search-catalog",
"mcp__ucp-checker__search-all",
"mcp__ucp-checker__search-policies",
"mcp__ucp-checker__get-product-details"
],
"ask": [
"mcp__ucp-checker__check-domain",
"mcp__ucp-checker__discover-store"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ucp-checker. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.ucpchecker/ucp-checker/verify?hash=03e5c7f28ef3b6262453a22f1e679813957c5915d8f19143439c6c18b1fa9561" | jq -e '.changed == false'Pinned hash 03e5c7f28ef3, from Nov 14, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.ucpchecker/ucp-checker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.ucpchecker/ucp-checker)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
UCP Checker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the UCP Checker MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the UCP Checker MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the UCP Checker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the UCP Checker MCP server have?
- 8 tools: 2 write, 6 read. check-domain, discover-store, list-stores, list-categories, search-catalog, search-all, search-policies and get-product-details.
Does the UCP Checker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the UCP Checker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the UCP Checker MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.