Kryptheon

io.github.jhashantanu987-beepPublished by GitHub account jhashantanu987-beepv0.1.1Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Kryptheon records flows through your app, re-checks them after each change, and attacks a copy of your database to surface security issues.

What you can do
  • Record a user flow through your app and replay it as a check after every change.
  • Verify recorded flows still pass, so regressions in app behavior are caught.
  • Run attack-style scans against a copy of a Postgres or Supabase database.
  • Report findings from flow checks and database scans back to the assistant.
When to use it
Useful when you want an assistant to keep an eye on app flows between changes and to probe a copy of your database for weaknesses before shipping.
Requirements
Runs as a local stdio process installed from the npm package kryptheon-mcp, so Node.js is needed. The database scan requires a Postgres or Supabase connection string supplied through the KN_DATABASE_URL environment variable; no other authentication is declared.
Before you install
The server asks for a database connection string (KN_DATABASE_URL), which is a powerful credential; point it at a copy or test database rather than production, and keep it in the environment rather than in chat. Recorded flows and scans act on your app and database, so review what they run before use.

Installation

In SourceWeft

  1. Open Kryptheon in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 25, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.