io.github.tim777z/utopia-megastore
REMOTE · UTOPIA-ORDERS.PRECOGSECURITY.WORKERS.DEV
Tech store for AI agents: search, bundles, negotiation, payment splits, PayPal checkout.
Available components
Last scanned (22 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 754 tokens (~107/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “list_products” rewrote its description, which is the text the model reads security
- Schema quality: 654 → 754 ▼ functional
- New tool “list_sets” functional
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Nov 26 65
First indexed and scored.
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 21 Nov 2026 · Probed https://utopia-orders.precogsecurity.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=precogsecurity.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60821c8db0ea8348110de1829473f1f58f4 |
| SANs: *.precogsecurity.workers.dev, precogsecurity.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of utopia-orders.precogsecurity.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://utopia-orders.precogsecurity.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://utopia-orders.precogsecurity.workers.dev/mcp | Inconclusive | 405 |
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 →
create_checkout Create an order and get a payment link ~122
Create an order and receive a PayPal payment URL (cards, Google Pay, Apple Pay, Venmo). Nothing is charged here: the URL must be approved by whoever holds the funds. On payment capture the order is forwarded automatically to CJ Dropshipping with USPS last-mile.
| Name | Type | Req | Description |
|---|---|---|---|
| caller | string | – | Identifier of the requesting agent |
| string | yes | Buyer email for the order receipt | |
| items | array | yes | Line items to purchase |
| split | array | – | Optional multi-payer allocation |
| total | number | yes | Order total in USD |
No output schema declared.
No examples provided.
list_products List products and bundles ~64
Return the full catalog: 15 products (id, name, price, bulk discount text, category, image, description, cj_vid, fits_with add-on ids), 4 bundles and 6 cross-subsidized sets, plus payment methods and free-shipping threshold.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sets List cross-subsidized sets and add-ons ~72
Return the 6 curated sets. Each set discounts the big-ticket item while cheap fittings/add-ons keep near-retail margin, and exposes per-line bundle_price (sums to the set price) plus addon_options at set-only prices. Use this before create_checkout when a buyer wants a whole setup rather than single items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
negotiate_price Negotiate a price ~89
Propose a target total for a set of items. The server replies with the lowest price it can legally accept; the floor is supplier cost + 12% margin, and matching bundles override per-item pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Target total in USD |
| caller | string | – | Stable identifier for the negotiating agent or buyer email |
| items | array | yes | Product ids to negotiate over |
No output schema declared.
No examples provided.
search_products Search the catalog ~52
Fuzzy/semantic product search over the catalog. Returns ranked matches with prices and any bundles that contain a match.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What the buyer is looking for, e.g. "charger for laptop" |
No output schema declared.
No examples provided.
suggest_bundle Build a set within a budget ~91
Given the item ids a buyer wants and an optional budget, return the fixed bundles plus custom cross-subsidised combinations. Each custom entry gives retail, bundle price, savings and a per-line allocation so a multi-party split stays fair.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Maximum total the buyer will pay in USD |
| items | array | – | Product ids of interest, e.g. ["hi-res-earbuds"] |
No output schema declared.
No examples provided.
validate_split Validate a multi-agent payment split ~65
Check that a proposed multi-recipient allocation sums exactly to the order total. Returns allocOk plus the discrepancy. Use before create_checkout when several agents share the cost.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Line items being purchased |
| split | array | yes | Each payer and what they owe |
No output schema declared.
No examples provided.
How do I install the io.github.tim777z/utopia-megastore MCP server?
io.github.tim777z/utopia-megastore is a hosted endpoint at https://utopia-orders.precogsecurity.workers.dev/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 · utopia-orders.precogsecurity.workers.dev
claude mcp add --transport http tim777z-utopia-megastore 'https://utopia-orders.precogsecurity.workers.dev/mcp'
What is the io.github.tim777z/utopia-megastore MCP server?
io.github.tim777z/utopia-megastore is an MCP server listed in the public MCP registry as io.github.tim777z/utopia-megastore. Tech store for AI agents: search, bundles, negotiation, payment splits, PayPal checkout. This page covers its hosted endpoint (https://utopia-orders.precogsecurity.workers.dev/mcp).
Is the io.github.tim777z/utopia-megastore MCP server safe to use?
io.github.tim777z/utopia-megastore scores 71 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 io.github.tim777z/utopia-megastore MCP server expose?
io.github.tim777z/utopia-megastore exposes 7 tools: list_products, list_sets, search_products, suggest_bundle, negotiate_price, and 2 more. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.
Does the io.github.tim777z/utopia-megastore MCP server require authentication?
No. We connected to io.github.tim777z/utopia-megastore without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.tim777z/utopia-megastore MCP server still maintained?
io.github.tim777z/utopia-megastore is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.tim777z/utopia-megastore MCP server?
VerifyMCP ran 12 checks on io.github.tim777z/utopia-megastore, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.tim777z/utopia-megastore: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.