io.cycloid.mcp/server
REMOTE · MCP.CYCLOID.IO
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Available components
Last scanned (14 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CI/CD and DevOps
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
- Authorisation not fully verified: no authorisation is required to call this server, and 2 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1320 tokens (~73/item across 18 items; 13 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Checks we ran (12)
- TLS certificate
- HTTPS
- 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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 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.
- 18 Nov 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.
- 16 Nov 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.
- 14 Nov 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.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 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
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://mcp.cycloid.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.cycloid.io | CN=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA256-RSA | 6a8cf6cbf5ff4191a0601dfc37b15809370 |
| SANs: *.cycloid.io, cycloid.io | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cycloid.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| cycloid.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cycloid.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cycloid.io/mcp | HTTPS enforced | 308 | https://mcp.cycloid.io/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 →
CYCLOID_BLUEPRINT_LIST ~34
List all available blueprints with their details. The LLM can filter the results based on user requirements.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_BLUEPRINT_STACK_CREATE ~123
Create a new Cycloid stack from a blueprint. CRITICAL: When elicitation context (ctx) is provided, the tool will ALWAYS use interactive elicitation to ask for parameters one by one, REGARDLESS of any parameters provided. The LLM should ONLY provide the 'ref' parameter and let elicitation handle the rest. DO NOT provide name, use_case, or service_catalog_source_canonical when elicitation is available.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | The blueprint reference (e.g., "cycloid-io:terraform-sample") |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
CYCLOID_CATALOG_REPO_LIST ~37
List all available service catalog repositories with their details. The LLM can filter the results based on user requirements.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_COMPONENT_GET ~60
Get the state of one or more components in a project environment.
| Name | Type | Req | Description |
|---|---|---|---|
| canonicals | array | yes | List of component canonicals to fetch. |
| env | string | yes | The environment canonical. |
| project | string | yes | The project canonical. |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_COMPONENT_LIST ~39
List components in a project environment.
| Name | Type | Req | Description |
|---|---|---|---|
| env | string | yes | The environment canonical. |
| project | string | yes | The project canonical. |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_EVENT_LIST ~332
List organization events with optional filters. To filter by WHAT HAPPENED, use `action` (e.g. create, update, delete, configure, pause, unpause) and/or `entity` (e.g. component, ci_build, ci_job, pipeline, credential) — these are matched case-insensitively against each event's actual `action`/`entity` tag VALUE (note: the entity is `ci_build`, not `build`). If a filter matches nothing while events exist, the response lists the available_actions/available_entities to retry with. `type` is ONLY the high-level category: Cycloid, AWS, Monitoring, Custom (do NOT pass an action/entity name as `type`). `severity` is one of: info, warn, err, crit. `begin`/`end` are Unix timestamps in SECONDS (strings); omit any filter to include all of its values. Returns full event payload including tags. Actor identity is in tags as {key: 'user', value: '<username>'}.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | – | Filter by the event's `action` tag (e.g. create, configure, pause). |
| begin | – | – | Unix timestamp (string) start date. |
| end | – | – | Unix timestamp (string) end date. |
| entity | – | – | Filter by the event's `entity` tag (e.g. component, ci_build, pipeline). |
| severity | – | – | Event severities to include (info, warn, err, crit). |
| type | – | – | Event categories to include (Cycloid, AWS, Monitoring, Custom). |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_MEMBER_LIST ~57
List all members of the organization. Use this to look up a member's numeric `id` from their `username`. The `id` field is required to build member URLs: /organizations/<org>/members/<id>.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_PIPELINE_LIST ~20
List all pipelines from Cycloid.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_PROJECT_EVENTS ~371
List events scoped to a specific project's components. Walks project → envs → components, then filters org-wide events by project tag. Returns events, count, and a deduplicated actors list extracted from tags[key=user]. Actor usernames can be cross-referenced with CYCLOID_MEMBER_LIST to get numeric ids for building member URLs. Hard cap: aborts with a structured error if total components exceed the configured maximum (default 50). Use begin/end/severity/type/action/entity to narrow results. Filter by WHAT HAPPENED with `action` (e.g. create, update, delete, configure, pause, unpause) and/or `entity` (e.g. component, ci_build, ci_job, pipeline) — matched case-insensitively against each event's actual tag VALUE (the entity is `ci_build`, not `build`). If a filter matches nothing while events exist, the response lists available_actions/available_entities to retry with. `type` is ONLY the high-level category: Cycloid, AWS, Monitoring, Custom (do NOT pass an action/entity name as `type`). `severity` is one of: info, warn, err, crit.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | – | Filter by the event's `action` tag (e.g. create, configure, pause). |
| begin | – | – | Unix timestamp (string) start date. |
| end | – | – | Unix timestamp (string) end date. |
| entity | – | – | Filter by the event's `entity` tag (e.g. component, ci_build, pipeline). |
| project | string | yes | The project canonical (required). |
| severity | – | – | Event severities to include (info, warn, err, crit). |
| type | – | – | Event categories to include (Cycloid, AWS, Monitoring, Custom). |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_PROJECT_GET ~35
Get one or more projects by canonical.
| Name | Type | Req | Description |
|---|---|---|---|
| canonicals | array | yes | List of project canonicals to fetch. |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_PROJECT_LIST ~19
List all projects in the organization.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_PROJECT_LIST_ENV ~29
List environments in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | The project canonical. |
Structured output declared, but exposes no named fields.
No examples provided.
CYCLOID_STACKFORMS_VALIDATE ~62
Validate a StackForms (.forms.yml) file using the Cycloid CLI. This tool can validate StackForms configuration and provide detailed feedback for fixing issues.
| Name | Type | Req | Description |
|---|---|---|---|
| forms_content | string | yes | The content of the .forms.yml file to validate |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.cycloid.mcp/server server?
io.cycloid.mcp/server is a hosted endpoint at https://mcp.cycloid.io/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 · mcp.cycloid.io
claude mcp add --transport http io-cycloid-mcp-server 'https://mcp.cycloid.io/mcp'
What is the io.cycloid.mcp/server server?
io.cycloid.mcp/server is listed in the public MCP registry as io.cycloid.mcp/server. An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform. This page covers its hosted endpoint (https://mcp.cycloid.io/mcp).
Is the io.cycloid.mcp/server server safe to use?
io.cycloid.mcp/server scores 77 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.cycloid.mcp/server server expose?
io.cycloid.mcp/server exposes 13 tools: CYCLOID_CATALOG_REPO_LIST, CYCLOID_COMPONENT_GET, CYCLOID_COMPONENT_LIST, CYCLOID_EVENT_LIST, CYCLOID_PROJECT_EVENTS, and 8 more. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.
Does the io.cycloid.mcp/server server require authentication?
No. We connected to io.cycloid.mcp/server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.cycloid.mcp/server server still maintained?
io.cycloid.mcp/server 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.cycloid.mcp/server server?
VerifyMCP ran 12 checks on io.cycloid.mcp/server, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.cycloid.mcp/server: Authorization. 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.