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.

karst

PYPI · KARST

Code context for AI dev tools: pack-scoped, cited code retrieval over MCP.

Available components

pypi · karst 44
+15 this week 44 Trust /100

Last scanned (1 day ago)

Scores higher than 43% of PyPI servers

Category Code Search and Documentation

Recent critical change

CVE-2026-112398 affects this package (24 Oct 2026). See the changelog before you install this server.

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 Security99
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 74 of 76 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 74 of 76 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to Moin105/upgraded-garbanzo). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 28 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 25 Oct 26 +29
    • CVE-2026-112403 no longer affects this package ▲ security
    • CVE-2026-112900 no longer affects this package ▲ security
    • CVE-2026-96639 no longer affects this package ▲ security
    • CVE-2026-112398 no longer affects this package ▲ security
    • CVE-2026-112393 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
    • Score status: failed → scored ▲ functional
  • 24 Oct 26 0
    • CVE-2026-112398 affects this package: high ▼ critical
  • 23 Oct 26 0
    • CVE-2026-96639 affects this package: high ▼ critical
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 5 Nov 2026 · Analysed pypi/karst@0.2.9

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 Moin105/upgraded-garbanzo
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Moin105/upgraded-garbanzo/.github/workflows/publish.yml@refs/tags/v0.2.9
Rekor log index 1931658068
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:c35fe09f38063c0f01b43074754bdc256f8c7bf1a1fbc0cabe25bc505cbed33d

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

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

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the karst MCP server?

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

pypi · karst

# add to Claude Code
claude mcp add moin105-karst -- uvx karst
Common questions

What is the karst MCP server?

karst is an MCP server listed in the public MCP registry as io.github.Moin105/karst. Code context for AI dev tools: pack-scoped, cited code retrieval over MCP. This page covers its PyPI package (karst).

Is the karst MCP server safe to use?

karst scores 44 out of 100 on VerifyMCP. 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.

Is the karst MCP server still maintained?

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

karst declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.