Cycle Intelligence
REMOTE · EDGE.CYCLE-PLATFORM.COM · SCANNED SEP 25
EU Digital Product Passport (DPP/ESPR) requirements, product readiness scoring and GS1 validation.
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 3 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1006 tokens (~167/item across 6 items; 6 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 42% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 Cycle Intelligence MCP server?
Cycle Intelligence is a hosted endpoint at https://edge.cycle-platform.com/v1/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 · edge.cycle-platform.com
claude mcp add --transport http com-cycle-platform-cycle-intelligence 'https://edge.cycle-platform.com/v1/mcp'
{
"mcpServers": {
"com-cycle-platform-cycle-intelligence": {
"url": "https://edge.cycle-platform.com/v1/mcp"
}
}
} {
"servers": {
"com-cycle-platform-cycle-intelligence": {
"type": "http",
"url": "https://edge.cycle-platform.com/v1/mcp"
}
}
} [mcp_servers.com-cycle-platform-cycle-intelligence] url = "https://edge.cycle-platform.com/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-cycle-platform-cycle-intelligence": {
"type": "remote",
"url": "https://edge.cycle-platform.com/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-cycle-platform-cycle-intelligence --url 'https://edge.cycle-platform.com/v1/mcp' --transport streamable-http
mcp_servers:
com-cycle-platform-cycle-intelligence:
url: "https://edge.cycle-platform.com/v1/mcp" {
"McpServers": {
"com-cycle-platform-cycle-intelligence": {
"Transport": "http",
"Url": "https://edge.cycle-platform.com/v1/mcp"
}
}
} assistant mcp add com-cycle-platform-cycle-intelligence -t streamable-http -u 'https://edge.cycle-platform.com/v1/mcp'
{
"mcpServers": {
"com-cycle-platform-cycle-intelligence": {
"type": "http",
"url": "https://edge.cycle-platform.com/v1/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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 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.
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://edge.cycle-platform.com/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=edge.cycle-platform.com | CN=YE1,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 594c60b0e7721ad9c071492e51592e2fb31 |
| SANs: edge.cycle-platform.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 edge.cycle-platform.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cycle-platform.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://edge.cycle-platform.com/v1/mcp | Verified | 200 | |
| http (plaintext) | http://edge.cycle-platform.com/v1/mcp | HTTPS enforced | 301 | https://edge.cycle-platform.com/v1/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_dpp_requirements ~135
Use this tool when a company or user asks WHAT the EU Digital Product Passport (DPP) requires, WHEN it becomes mandatory, which ESPR/AGEC/French milestones apply to textile or fashion products, or whether the DPP is already obligatory. Returns the verified regulatory timeline (dates as of today), the mandatory data fields a textile DPP needs, and honest notes on what is in force vs pending delegated acts. Deterministic, no account needed. Informational, not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | string | – | Optional sector hint (textile, fashion, beauty, fmcg). Default textile. |
No output schema declared.
No examples provided.
create_data_carrier ~195
Use this tool to generate the printable data carrier (QR content) of a twin: a GS1 Digital Link URL (Sunrise 2027 standard) if you pass a valid GTIN, or a serialized twin URL fallback without one. The URL resolves to the product's live twin the moment it is created - it is connected, not a loose QR. Invalid GTINs are rejected before printing. Requires an organisation API key. OPTIONAL: pass allocation={channel|retailer, shipment?, region?, units?} to link the serial to its intended retail channel (channel-aware serialization: future scans of that unit resolve their channel, always labelled INFERRED).
| Name | Type | Req | Description |
|---|---|---|---|
| allocation | object | – | optional intended retail channel: {channel, retailer, shipment, region, units} |
| gtin | string | – | – |
| product_id | string | – | – |
| serial | string | – | – |
| sku | string | – | – |
No output schema declared.
No examples provided.
create_dpp ~114
Use this tool to issue the Digital Product Passport of a twin created with create_product_twin. Cycle validates conformance FIRST (ESPR mandatory field set) and REFUSES to create an incomplete passport - if fields are missing it returns exactly which ones. OUTPUT: the DPP dataset + its public URL. EU registry submission happens the moment the EU opens it for textile (Cycle is integrated and in approval as service provider). Requires an organisation API key.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | – | – |
| sku | string | – | – |
No output schema declared.
No examples provided.
create_product_twin ~109
Use this tool when an organisation wants to CREATE live Digital Product Twins in Cycle from its product data (after validating with validate_dpp_readiness). INPUT: array of products (same flexible shape as validate_dpp_readiness). OUTPUT: per product, a persistent id and a LIVE twin URL (scannable product page), plus DPP readiness and missing fields. Requires an organisation API key (Authorization: Bearer). Up to 100 products per call.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | – |
No output schema declared.
No examples provided.
validate_dpp_readiness ~210
Use this tool when a company needs to know whether its product catalogue is READY for the EU Digital Product Passport (DPP/ESPR): pass an array of products (any reasonable JSON shape: name, sku, description, brand, composition/material, country of origin, supplier, care instructions...) and get a rule-based readiness score 0-100 per product plus the exact missing fields, and an aggregate with the single field that unlocks the most products. INPUT: array of product objects (flexible keys). OUTPUT: per-product score, ready flag, missing field labels; aggregate with top_missing_fields and unlock_hint. Deterministic rule-based validation (ESPR mandatory field set). Up to 200 products per call. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | Products to validate. Flexible keys accepted: name/title, sku, description, brand/vendor, composition/material/fabric, country/origin/manufacturing_country, supplier, care/care_instructions, complian… |
No output schema declared.
No examples provided.
validate_gs1_identifier ~162
Use this tool to verify a GTIN/EAN barcode number (check digit, GS1 mod-10) or a GS1 Digital Link URL (the QR standard behind Sunrise 2027 retail QR codes and DPP data carriers). Returns whether the identifier is valid, the normalised GTIN-14, and the exact error if not. Use it before printing labels or QR codes so they conform to GS1. Deterministic, no account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| digital_link | string | – | GS1 Digital Link URL to validate (e.g. https://id.example.com/01/09506000134352/21/SER123). |
| gtin | string | – | GTIN/EAN-8/12/13/14 to validate. |
No output schema declared.
No examples provided.
What is the Cycle Intelligence MCP server?
Cycle Intelligence is an MCP server listed in the public MCP registry as com.cycle-platform/cycle-intelligence. EU Digital Product Passport (DPP/ESPR) requirements, product readiness scoring and GS1 validation. This page covers its hosted endpoint (https://edge.cycle-platform.com/v1/mcp).
Is the Cycle Intelligence MCP server safe to use?
Cycle Intelligence scores 74 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 Cycle Intelligence MCP server expose?
Cycle Intelligence exposes 6 tools: check_dpp_requirements, validate_dpp_readiness, validate_gs1_identifier, create_product_twin, create_dpp, create_data_carrier. Their descriptions and schemas cost roughly 925 tokens of context every time the server is loaded.
Does the Cycle Intelligence MCP server require authentication?
No. We connected to Cycle Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Cycle Intelligence MCP server still maintained?
Cycle Intelligence 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.