CinderRoute Agentic CI Operations
connectsapi.cinderroute.dev
Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting.
https://api.cinderroute.dev/mcpWebsiteNo authMCP 2025-11-25v2.2.0last checked 27 Oct 2026spoke MCP on 100% of 90 checks (30 days)initialize in 444 msLast checked 27 Oct 2026
- ✓Answered the MCP handshake (MCP 2025-11-25)
- ✓Auth detected: No auth
- ✓Lists 5 tools
- ✓No blockers or warnings
- ✓Spoke MCP on 90 of 90 checks (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The endpoint answers an anonymous handshake, so no credential is needed.
claude mcp add --transport http cinderroute-agentic-ci-operations https://api.cinderroute.dev/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Connectors → Add custom connector, then paste https://api.cinderroute.dev/mcp.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The endpoint answers an anonymous handshake, so no credential is needed.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.cinderroute.dev/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"mcpServers": {
"cinderroute-agentic-ci-operations": {
"url": "https://api.cinderroute.dev/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The endpoint answers an anonymous handshake, so no credential is needed.
{
"servers": {
"cinderroute-agentic-ci-operations": {
"type": "http",
"url": "https://api.cinderroute.dev/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 27 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | No auth |
|---|---|
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 5 tools listable |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Breaking: ci_get_build_status, ci_list_failed_builds, ci_list_repositories, ci_read_build_logs, ci_read_secrets, ci_retry_build, ci_run_build_command, ci_trigger_deploy, cinderroute://status/failed-builds, triage_failed_build
Instructions rewritten: ci_list_failed_builds, ci_read_build_logs, ci_retry_build. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/cinderroute-agentic-ci-operations)