registry / record
mcp-server-kubernetes
Does mcp-server-kubernetes MCP work in Claude Code and Cursor? Throne executed mcp-server-kubernetes mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is mcp-server-kubernetes mcp safe? Static security scan: 3 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry mcp-server-kubernetes
sealed
- scan id
- 1e718ecc18874dd498970c3fec62fb85
- target
- mcp-server-kubernetes
- sealed at
- 2026-06-16 18:47:31Z
- evidence hash
- sha256:ef8f99ba090f336451beff8f7dc7845d32643a69e585cc354d49610ef1df65ce
initialize ok: server kubernetes 3.9.1, negotiated protocolVersion 2025-11-25, capabilities ['prompts', 'resources', 'tools']
supported: tools/list (23 tools), resources/list (5), prompts/list (1)
all 23 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 2 ok, 8 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: cleanup:accepted (returned result); kubectl_get:error(-32603); kubectl_describe:error(-32603); kubectl_apply:error(-32600); kubectl_delete:error(-32600); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: error(-32600); recovery: accepted (returned result); cancellation: error(-32600); 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
server answered with a structured error instead of completing the step, MCP error -32603: MCP error -32603: Failed to read resource: Error: HTTP protocol is not allowed when skipTLSVerify is not set or false
ladder 1 overlapping cleanup calls: max_observed_stable_concurrency=1; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server kubernetes 3.9.1, negotiated protocolVersion 2025-11-25, capabilities ['prompts', 'resources', 'tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (23 tools), resources/list (5), prompts/list (1); notes: connection 2 confirms 23 tools
all 23 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 2 ok, 8 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived, wrong_type_args: cleanup:accepted (returned result); kubectl_get:error(-32603); kubectl_describe:error(-32603); kubectl_apply:error(-32600); kubectl_delete:error(-32600); unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: error(-32600); recovery: accepted (returned result); cancellation: error(-32600); 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
server answered with a structured error instead of completing the step, MCP error -32603: MCP error -32603: Failed to read resource: Error: HTTP protocol is not allowed when skipTLSVerify is not set or false
ladder 1/2/4/6 overlapping cleanup calls: max_observed_stable_concurrency=6; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
execFileSync() called with a dynamically built command (heuristic, review): 'file, args, options);'
package/dist/security/kubectl-flags.js:1511 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: attacker (package/dist/security/kubectl-flags.d.ts:19)
package/dist/security/kubectl-flags.d.ts:19injection-style phrase in source string: 'exfiltrate'
package/dist/security/kubectl-flags.js:7- target
- mcp-server-kubernetes 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
- 16 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 18:47:31Z
- evidence hash
- sha256:ef8f99ba090f336451beff8f7dc7845d32643a69e585cc354d49610ef1df65ce
- 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/mcp-server-kubernetes)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.