registry / record
@circleci/mcp-server-circleci
Does @circleci/mcp-server-circleci MCP work in Claude Code and Cursor? Throne executed @circleci/mcp-server-circleci mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is @circleci/mcp-server-circleci mcp safe? Static security scan: 1 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry @circleci/mcp-server-circleci
sealed
- scan id
- 74252e4521cd43b480d1261297568212
- target
- @circleci/mcp-server-circleci
- sealed at
- 2026-06-16 17:25:06Z
- evidence hash
- sha256:61df7d5dfa4f9b1488a1700cd5c3007da95c6b710f70e9690fde5e6fc09e218f
initialize ok: server mcp-server-circleci 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools']
supported: tools/list (17 tools); method not found (tolerated): resources/list, prompts/list
all 17 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 0 ok, 10 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: get_build_failure_logs:accepted (returned result); find_flaky_tests:accepted (returned result); get_latest_pipeline_status:accepted (returned result); get_job_test_results:accepted (returned result); config_helper:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1 overlapping get_build_failure_logs calls: max_observed_stable_concurrency=1; all ids answered exactly once, but every call returned an error (tool-level isError result), the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server mcp-server-circleci 1.0.0, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (17 tools); method not found (tolerated): resources/list, prompts/list; notes: connection 2 confirms 17 tools
all 17 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 0 ok, 10 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: get_build_failure_logs:accepted (returned result); find_flaky_tests:accepted (returned result); get_latest_pipeline_status:accepted (returned result); get_job_test_results:accepted (returned result); config_helper:accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
resources capability not declared
ladder 1/2/4/6 overlapping get_build_failure_logs calls: max_observed_stable_concurrency=6; all ids answered exactly once, but every call returned an error (tool-level isError result), the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
8 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: api (package/dist/clients/circleci/index.js:15), app (package/dist/clients/circleci/index.js:21), app.circleci.com (package/dist/lib/project-detection/index.js:33), circleci.atlassian.net (package/dist/lib/project-detection/vcsTool.js:3), circleci.com (package/dist/clients/circleci/index.js:13), circlet.ai (package/dist/clients/circlet/index.js:11), gist.githubusercontent.com (package/dist/tools/runEvaluationTests/handler.js:128), runner.circleci.com (package/dist/lib/telemetry/config.js:5)
package/dist/clients/circleci/index.js:13- target
- @circleci/mcp-server-circleci npm
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 17:25:06Z
- evidence hash
- sha256:61df7d5dfa4f9b1488a1700cd5c3007da95c6b710f70e9690fde5e6fc09e218f
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/circleci-mcp-server-circleci)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.