Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Koschei

PYPI · KOSCHEI-LANG

Run agent-written code under a capability policy: see what a program can touch before it runs.

Available components

+3 this week 66 Trust /100

Last scanned (18 hours ago)

Scores higher than 58% of PyPI servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency87
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to bugsbuny243/koschei-lang). View diagnostics → Pass
  • License check failed: the license (LicenseRef-Koschei-Lang-1.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 260 tokens (~86/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 13 Nov 26 0
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.12.0 → 0.14.0 functional
    • Package version: 0.12.0 → 0.13.0 functional
  • 12 Nov 26 +16
    • Stability: 0.03 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.10.1 → 0.12.0 functional
    • Package version: 0.10.1 → 0.11.0 functional
Diagnostics

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 21 Nov 2026 · Analysed pypi/koschei-lang@0.14.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo bugsbuny243/koschei-lang
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/bugsbuny243/koschei-lang/.github/workflows/publish-pypi.yml@refs/heads/main
Rekor log index 3849712033
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:cbe042755b476c49edf5256dcc6eb539c1db5f11a82b89e78e6d4d49a3d26e9f

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~211 tokens

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 →

Tool Tokens
koschei_check ~87

Compiles a Koschei program without running it and reports its capability manifest: every disk path, network origin and other authority it asks for, and whether this server's policy would allow it. Nothing executes.

NameTypeReqDescription
sourcestringyesComplete Koschei source with a `main` function. Call koschei_guide first if you have not written Koschei before.

No output schema declared.

No examples provided.

koschei_guide ~33

Returns a reference for writing Koschei, a capability-secure language. Read it before writing a program.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

koschei_run ~91

Compiles and runs a Koschei program under this server's policy. Allowed: clock; random. A program that asks for anything else is rejected before a single line executes. The result includes the capability manifest and the output.

NameTypeReqDescription
sourcestringyesComplete Koschei source with a `main` function. Call koschei_guide first if you have not written Koschei before.

No output schema declared.

No examples provided.

Install

How do I install the Koschei MCP server?

Koschei runs locally as a PyPI package, launched with uvx koschei-lang. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · koschei-lang

# add to Claude Code
claude mcp add bugsbuny243-koschei -- uvx koschei-lang
Common questions

What is the Koschei MCP server?

Koschei is an MCP server listed in the public MCP registry as io.github.bugsbuny243/koschei. Run agent-written code under a capability policy: see what a program can touch before it runs. This page covers its PyPI package (koschei-lang).

Is the Koschei MCP server safe to use?

Koschei scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 Koschei MCP server expose?

Koschei exposes 3 tools: koschei_guide, koschei_check, koschei_run. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.

Is the Koschei MCP server still maintained?

Koschei is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Koschei MCP server under?

Koschei declares the LicenseRef-Koschei-Lang-1.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the Koschei MCP server?

VerifyMCP ran 15 checks on Koschei, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Koschei: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.