# Kryptheon (npm · kryptheon-mcp)

Record a flow through your app, check it after every change, and attack a copy of your database.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `kryptheon-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp.md), [page](https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp)

## Channel facts

- Registry: `npm`
- Package: `kryptheon-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add jhashantanu987-beep-kryptheon -- npx -y kryptheon-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "jhashantanu987-beep-kryptheon": {
      "command": "npx",
      "args": [
        "-y",
        "kryptheon-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jhashantanu987-beep-kryptheon": {
      "command": "npx",
      "args": [
        "-y",
        "kryptheon-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jhashantanu987-beep-kryptheon -- npx -y kryptheon-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jhashantanu987-beep-kryptheon": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "kryptheon-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jhashantanu987-beep-kryptheon --command npx --arg -y --arg kryptheon-mcp
```

### Hermes

```yaml
mcp_servers:
  jhashantanu987-beep-kryptheon:
    command: "npx"
    args: ["-y", "kryptheon-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "jhashantanu987-beep-kryptheon": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "kryptheon-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jhashantanu987-beep-kryptheon -t stdio -c npx -a -y kryptheon-mcp
```

### Other

```json
{
  "mcpServers": {
    "jhashantanu987-beep-kryptheon": {
      "command": "npx",
      "args": [
        "-y",
        "kryptheon-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 65)

First indexed and scored.

## MCP tools (4)

### `kryptheon_record` (~201 tokens)

Record a flow through the app

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.

Input parameters:

- `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, required): Address of the running app, e.g. https://my-app.lovable.app or http://localhost:3000

### `kryptheon_check` (~121 tokens)

Replay every recording and say what broke

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.

Input parameters:

- `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.

### `kryptheon_scan_database` (~139 tokens)

Attack a copy of the database

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.

Input parameters:

- `schema` (string): The schema the app lives in. Leave it out: it is "public" for almost everyone.

### `kryptheon_job` (~65 tokens)

Wait for a recording, check or scan to finish

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.

Input parameters:

- `job_id` (string, required): The id another kryptheon tool handed back, e.g. "check-1".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp#diagnostics

## Score history

- 2026-09-25: 65

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/kryptheon-mcp
- Socket report: https://socket.dev/npm/package/kryptheon-mcp
- Changelog RSS feed: https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jhashantanu987-beep-kryptheon/kryptheon-mcp