Index / MCP servers / CinderRoute Agent Exchange

CinderRoute Agent Exchange MCP server

CinderRoute Agent Exchange is an MCP server with 8 tools an agent can call, among them ci_get_build_status, ci_list_failed_builds, ci_list_repositories. It answers at https://api.cinderroute.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.

Status
Answering
Tools
8
Official
yes, served from cinderroute.dev
Reliability
6 of 6 checks
Response time
432 ms
Transport
streamable HTTP
Last checked
19 October 2026

CinderRoute Agent Exchange for public failed-build triage, artifact handoff, and remediation.

Description as the publisher wrote it.

The 8 tools CinderRoute Agent Exchange offers

ToolWhat it does
ci_get_build_statusInspect a CI build and receive its failed step and log cursor. Use read_build_logs next when status is failed.
Inputs: build_id, include_logs
ci_list_failed_buildsList active failed CI builds. Start here, then pass a returned build_id to get_build_status.
Inputs: project, limit
ci_list_repositoriesList repositories and their latest build state. Failed builds include a build_id for get_build_status.
Inputs: org, language, visibility, page
ci_read_build_logsRead bounded fictional logs for a failed CI build. The result names the runner, workspace, and suggested diagnostic command.
Inputs: build_id, log_cursor, step, limit
ci_read_secretsList masked deployment secret metadata for a project environment.
Inputs: project, environment, key
ci_retry_buildQueue a fictional retry after diagnostics. Defaults to dry-run and returns a retry build identifier.
Inputs: build_id, dry_run
ci_run_build_commandExecute 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.
Inputs: build_id, runner_id, command, working_directory, shell, timeout_seconds
ci_trigger_deployTrigger a new deployment to the specified environment.
Inputs: project, environment, ref

Add CinderRoute Agent Exchange to your AI client

Every block below points at https://api.cinderroute.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http cinderroute-agent-exchange https://api.cinderroute.dev/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.cinderroute.dev/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "cinderroute-agent-exchange": {
      "type": "http",
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "cinderroute-agent-exchange": {
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "serverUrl": "https://api.cinderroute.dev/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: CinderRoute Agent Exchange
version: 0.0.1
schema: v1
mcpServers:
  - name: CinderRoute Agent Exchange
    type: streamable-http
    url: https://api.cinderroute.dev/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "httpUrl": "https://api.cinderroute.dev/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "type": "http",
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "cinderroute-agent-exchange": {
      "url": "https://api.cinderroute.dev/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.cinderroute.dev%2Fmcp&type=streamable_http&id=cinderroute-agent-exchange&name=CinderRoute%20Agent%20Exchange

Is CinderRoute Agent Exchange up right now?

It answered our last check on 19 October 2026 in 432 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to CinderRoute Agent Exchange

Questions about CinderRoute Agent Exchange

Is there an official CinderRoute Agent Exchange MCP server?

Yes. It is published by cinderroute.dev and served from api.cinderroute.dev, the vendor's own domain: https://api.cinderroute.dev/mcp.

How many tools does CinderRoute Agent Exchange have?

8, as returned by the server's own tools/list on 11 September 2026: 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.

Is CinderRoute Agent Exchange down?

It answered our last check on 19 October 2026 in 432 ms. Over 6 checks since 10 September 2026 it answered 6.

How do I add CinderRoute Agent Exchange to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.cinderroute.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does CinderRoute Agent Exchange need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: dev.cinderroute. Endpoint host: api.cinderroute.dev. ARD identifier: urn:air:dev.cinderroute:mcp:agentic-ci-operations. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.