CinderRoute Agentic CI Operations
REMOTE · API.CINDERROUTE.DEV · SCANNED SEP 20
Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting.
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 448 tokens (~56/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability check failed: schema churn in the 10 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ci_trigger_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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 CinderRoute Agentic CI Operations MCP server?
CinderRoute Agentic CI Operations is a hosted endpoint at https://api.cinderroute.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 · api.cinderroute.dev
claude mcp add --transport http dev-cinderroute-agentic-ci-operations 'https://api.cinderroute.dev/mcp'
{
"mcpServers": {
"dev-cinderroute-agentic-ci-operations": {
"url": "https://api.cinderroute.dev/mcp"
}
}
} {
"servers": {
"dev-cinderroute-agentic-ci-operations": {
"type": "http",
"url": "https://api.cinderroute.dev/mcp"
}
}
} [mcp_servers.dev-cinderroute-agentic-ci-operations] url = "https://api.cinderroute.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-cinderroute-agentic-ci-operations": {
"type": "remote",
"url": "https://api.cinderroute.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-cinderroute-agentic-ci-operations --url 'https://api.cinderroute.dev/mcp' --transport streamable-http
mcp_servers:
dev-cinderroute-agentic-ci-operations:
url: "https://api.cinderroute.dev/mcp" {
"McpServers": {
"dev-cinderroute-agentic-ci-operations": {
"Transport": "http",
"Url": "https://api.cinderroute.dev/mcp"
}
}
} assistant mcp add dev-cinderroute-agentic-ci-operations -t streamable-http -u 'https://api.cinderroute.dev/mcp'
{
"mcpServers": {
"dev-cinderroute-agentic-ci-operations": {
"type": "http",
"url": "https://api.cinderroute.dev/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 11 Sept 26 +22
- Stability: unverified → fail ▼ security
- Authorization: unverified → pass ▲ security
- Judged manipulation: unverified → pass ▲ security
- Tool “ci_get_build_status” rewrote its description, which is the text the model reads security
- Tool “ci_list_repositories” rewrote its description, which is the text the model reads security
- Tool “ci_read_secrets” rewrote its description, which is the text the model reads security
- Tool “ci_run_build_command” rewrote its description, which is the text the model reads security
- Schema quality: 49 → 56 ▼ functional
- “ci_run_build_command” added a required parameter “build_id”, so existing callers break ▼ functional
- Schema quality: unverified → good ▲ functional
- Tool “ci_get_build_status” now declares an output schema ▲ functional
- Tool “ci_list_repositories” now declares an output schema ▲ functional
- Tool “ci_read_secrets” now declares an output schema ▲ functional
- Tool “ci_run_build_command” now declares an output schema ▲ functional
- Tool “ci_trigger_deploy” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.2.0 → 1.3.0 functional
- New tool “ci_list_failed_builds” functional
- New tool “ci_read_build_logs” functional
- New tool “ci_retry_build” functional
- “ci_run_build_command” added an optional parameter “runner_id” cosmetic
- “ci_list_repositories” made “org” optional cosmetic
- 10 Sept 26 50
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 20 Sept 2026 · Probed https://api.cinderroute.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.cinderroute.dev | CN=YE1,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 51641db52b9687c98e3a8d3e1ff228e2ede |
| SANs: api.cinderroute.dev | ||||||
| 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 api.cinderroute.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| cinderroute.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="cinderroute-ci", error="invalid_token", error_description="Bearer token required", resource_metadata="https://api.cinderroute.dev/.well-known/oauth-protected-resource"
Bearer realm="cinderroute-ci", error="invalid_token", error_description="Bearer token required", resource_metadata="https://api.cinderroute.dev/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://api.cinderroute.dev/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.cinderroute.dev/mcp |
| Authorisation server | https://api.cinderroute.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.cinderroute.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.cinderroute.dev/mcp | HTTPS enforced | 308 | https://api.cinderroute.dev/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 →
ci_get_build_status ~49
Inspect a CI build and receive its failed step and log cursor. Use read_build_logs next when status is failed.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| include_logs | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| duration_seconds | integer|null | – | – |
| finished_at | string | – | – |
| observed_at | string | yes | – |
| repository_id | string | yes | – |
| started_at | string | – | – |
| status | string | yes | – |
No examples provided.
ci_list_failed_builds ~45
List active failed CI builds. Start here, then pass a returned build_id to get_build_status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| project | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| builds | array | yes | – |
| observed_at | string | yes | – |
| total | integer | yes | – |
No examples provided.
ci_list_repositories ~57
List repositories and their latest build state. Failed builds include a build_id for get_build_status.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| org | string | – | – |
| page | integer | – | – |
| visibility | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| observed_at | string | yes | – |
| page | integer | yes | – |
| repositories | array | yes | – |
| total | integer | yes | – |
No examples provided.
ci_read_build_logs ~63
Read bounded fictional logs for a failed CI build. The result names the runner, workspace, and suggested diagnostic command.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| limit | integer | – | – |
| log_cursor | string | – | – |
| step | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| lines | array | yes | – |
| log_cursor | string | yes | – |
| observed_at | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
ci_read_secrets ~41
List masked deployment secret metadata for a project environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| key | string | – | – |
| project | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| observed_at | string | yes | – |
| project | string | yes | – |
| secrets | array | yes | – |
| values_exposed | boolean | yes | – |
No examples provided.
ci_retry_build ~43
Queue a fictional retry after diagnostics. Defaults to dry-run and returns a retry build identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| dry_run | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| dry_run | boolean | yes | – |
| observed_at | string | yes | – |
| retry_build_id | string | yes | – |
| status | string | yes | – |
No examples provided.
ci_run_build_command ~90
Execute a diagnostic command on an isolated CI runner and return bounded stdout and stderr for build troubleshooting. Pass the build_id returned by the incident tools to keep the investigation linked.
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| command | string | yes | – |
| runner_id | string | – | – |
| shell | string | – | – |
| timeout_seconds | integer | – | – |
| working_directory | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| build_id | string | yes | – |
| execution_id | string | yes | – |
| exit_code | integer | yes | – |
| observed_at | string | yes | – |
| status | string | yes | – |
| stderr | string | – | – |
| stdout | string | – | – |
No examples provided.
ci_trigger_deploy ~40
Trigger a new deployment to the specified environment.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | – |
| project | string | yes | – |
| ref | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | string | yes | – |
| observed_at | string | yes | – |
| queued_at | string | yes | – |
| status | string | yes | – |
No examples provided.
What is the CinderRoute Agentic CI Operations MCP server?
CinderRoute Agentic CI Operations is an MCP server listed in the public MCP registry as dev.cinderroute/agentic-ci-operations. Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting. This page covers its hosted endpoint (https://api.cinderroute.dev/mcp).
Is the CinderRoute Agentic CI Operations MCP server safe to use?
CinderRoute Agentic CI Operations 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 CinderRoute Agentic CI Operations MCP server expose?
CinderRoute Agentic CI Operations exposes 8 tools: ci_list_failed_builds, ci_list_repositories, ci_get_build_status, ci_read_build_logs, ci_read_secrets, and 3 more. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Does the CinderRoute Agentic CI Operations MCP server require authentication?
Yes. CinderRoute Agentic CI Operations asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the CinderRoute Agentic CI Operations MCP server still maintained?
CinderRoute Agentic CI Operations is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.