Kryptheon
NPM · KRYPTHEON-MCP · SCANNED SEP 25
Record a flow through your app, check it after every change, and attack a copy of your database.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 634 tokens (~158/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Kryptheon MCP server?
Kryptheon runs locally as an npm package, launched with npx -y kryptheon-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kryptheon-mcp
claude mcp add jhashantanu987-beep-kryptheon -- npx -y kryptheon-mcp
{
"mcpServers": {
"jhashantanu987-beep-kryptheon": {
"command": "npx",
"args": [
"-y",
"kryptheon-mcp"
]
}
}
} {
"servers": {
"jhashantanu987-beep-kryptheon": {
"command": "npx",
"args": [
"-y",
"kryptheon-mcp"
]
}
}
} codex mcp add jhashantanu987-beep-kryptheon -- npx -y kryptheon-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jhashantanu987-beep-kryptheon": {
"type": "local",
"command": [
"npx",
"-y",
"kryptheon-mcp"
],
"enabled": true
}
}
} openclaw mcp add jhashantanu987-beep-kryptheon --command npx --arg -y --arg kryptheon-mcp
mcp_servers:
jhashantanu987-beep-kryptheon:
command: "npx"
args: ["-y", "kryptheon-mcp"] {
"McpServers": {
"jhashantanu987-beep-kryptheon": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"kryptheon-mcp"
]
}
}
} assistant mcp add jhashantanu987-beep-kryptheon -t stdio -c npx -a -y kryptheon-mcp
{
"mcpServers": {
"jhashantanu987-beep-kryptheon": {
"command": "npx",
"args": [
"-y",
"kryptheon-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/kryptheon-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
kryptheon_check Replay every recording and say what broke ~121
Replays every recording in the folder and reports, in plain English, what still works and what broke - with the button or page that went missing and a line to paste back into an AI tool. Call it after every change to the app, and do not call a change done until it passes. If it says nothing has been recorded, use kryptheon_record first.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Absolute path of the project folder - normally the workspace root. Recordings are kept in its tests/ folder. Defaults to the folder this server was started in. |
No output schema declared.
No examples provided.
kryptheon_job Wait for a recording, check or scan to finish ~65
Waits up to 45 seconds for a job started by another kryptheon tool, then returns what it said. Call it again while it is still running.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The id another kryptheon tool handed back, e.g. "check-1". |
No output schema declared.
No examples provided.
kryptheon_record Record a flow through the app ~201
Opens the app in a browser window ON THE PERSON'S SCREEN and records what they do, as a test that kryptheon_check can replay after every change. Only a person can do the recording: tell them the window is open, to click through one short flow (sign in with an existing account, open a page), and to close the window when done. Returns while the window is still open; call kryptheon_job afterwards to learn whether it was saved. A folder that is not set up yet is set up first (package.json and a local kryptheon install). Never record a sign-up or a log-out.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | Absolute path of the project folder - normally the workspace root. Recordings are kept in its tests/ folder. Defaults to the folder this server was started in. |
| url | string | yes | Address of the running app, e.g. https://my-app.lovable.app or http://localhost:3000 |
No output schema declared.
No examples provided.
kryptheon_scan_database Attack a copy of the database ~139
Copies the SHAPE of the Postgres/Supabase database (never its rows) into a throwaway schema, attacks the copy - can a stranger read or change data, can the same thing exist twice, can a half-finished write survive - reports in plain English, and deletes the copy. The connection string is read from this server's KN_DATABASE_URL environment variable. NEVER ask the person to paste it into the chat. Takes 2-3 minutes; returns a job to follow with kryptheon_job.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | The schema the app lives in. Leave it out: it is "public" for almost everyone. |
No output schema declared.
No examples provided.
What is the Kryptheon MCP server?
Kryptheon is an MCP server listed in the public MCP registry as io.github.jhashantanu987-beep/kryptheon. Record a flow through your app, check it after every change, and attack a copy of your database. This page covers its npm package (kryptheon-mcp).
Is the Kryptheon MCP server safe to use?
Kryptheon scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Kryptheon MCP server expose?
Kryptheon exposes 4 tools: kryptheon_record, kryptheon_check, kryptheon_scan_database, kryptheon_job. Their descriptions and schemas cost roughly 526 tokens of context every time the server is loaded.
Is the Kryptheon MCP server still maintained?
Kryptheon is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Kryptheon MCP server under?
Kryptheon declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.