kryos-mcp
Governed code execution for AI agents that type-checks, runs, and capability-verifies Kryos code, ensuring agents only run code with declared and allowed capabilities.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
NORTHTEKDevs
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
KRYOS_BINRequires the [Kryos toolchain](https://github.com/NORTHTEKDevs/kryos-lang) on PATH (or set ).All four hints declared on every tool
4/5 tools missing one or more hints — kryos_check (missing: destructiveHint, idempotentHint); capability_manifest (missing: destructiveHint, idempotentHint); verify_capabilities (missing: destructiveHint, idempotentHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool annotations match behaviour
4 read-only tools perform write/delete/exec — kryos_check (line 33: fs.mkdirSync(dir, { recursive: true })); capability_manifest (line 33: fs.mkdirSync(dir, { recursive: true })); verify_capabilities (line 33: fs.mkdirSync(dir, { recursive: true }))
Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.
Destructive tools are labelled
5 tools perform destructive updates without destructiveHint — kryos_check deletes at line 44 (fs.rmSync(dir, { recursive: true, force: true })); kryos_run deletes at line 44 (fs.rmSync(dir, { recursive: true, force: true })); capability_manifest deletes at line 44 (fs.rmSync(dir, { recursive: true, force: true }))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/northtekdevs/kryos-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check