registry / record
mcp-server-kubernetes
> throne registry mcp-server-kubernetes
sealed
- scan id
- 0fa12e2999d447e2ae53e62e302038bb
- target
- mcp-server-kubernetes
- sealed at
- 2026-06-13 03:41:22Z
- evidence hash
- sha256:d4aec50f184c4e5b960d94a7dc704db08ca19c9b30329db7c4883709c8bbfbfa
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): 2 ok, 8 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
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/8 overlapping cleanup calls: max_observed_stable_concurrency=8; 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']
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): 2 ok, 8 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
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/8 overlapping cleanup calls: max_observed_stable_concurrency=8; 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:7paste 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.