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.

io.github.selvage-lab/selvage

PYPI · SELVAGE · SCANNED SEP 24

An LLM-based code review MCP server with AST-powered smart context extraction

Available components

pypi · selvage 19
0 this week 19 Trust /100
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 Security32
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects click 8.1.8, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 7 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package 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 →

Install

How do I install the io.github.selvage-lab/selvage MCP server?

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

pypi · selvage

# add to Claude Code
claude mcp add selvage-lab-selvage -- uvx selvage
// .cursor/mcp.json
{
  "mcpServers": {
    "selvage-lab-selvage": {
      "command": "uvx",
      "args": [
        "selvage"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "selvage-lab-selvage": {
      "command": "uvx",
      "args": [
        "selvage"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add selvage-lab-selvage -- uvx selvage
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "selvage-lab-selvage": {
      "type": "local",
      "command": [
        "uvx",
        "selvage"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add selvage-lab-selvage --command uvx --arg selvage
# ~/.hermes/config.yaml
mcp_servers:
  selvage-lab-selvage:
    command: "uvx"
    args: ["selvage"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "selvage-lab-selvage": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "selvage"
      ]
    }
  }
}
# add to Vellum
assistant mcp add selvage-lab-selvage -t stdio -c uvx -a selvage
// mcp.json
{
  "mcpServers": {
    "selvage-lab-selvage": {
      "command": "uvx",
      "args": [
        "selvage"
      ]
    }
  }
}
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.

  • 24 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 23 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 22 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 21 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 20 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 19 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 18 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
  • 17 Sept 26 0
    • CVE-2026-55380 affects this package: high ▼ security
    • CVE-2024-47081 affects this package: high ▼ security
    • CVE-2026-42308 affects this package: high ▼ security
    • CVE-2026-25990 affects this package: high ▼ security
    • CVE-2026-59200 affects this package: high ▼ security
    • CVE-2026-55798 affects this package: high ▼ security
    • CVE-2026-55379 affects this package: high ▼ security
    • CVE-2026-59199 affects this package: high ▼ security
    • CVE-2026-54059 affects this package: high ▼ security
    • CVE-2026-7246 affects this package: high ▼ security
    • CVE-2026-54058 affects this package: high ▼ security
    • CVE-2026-59205 affects this package: high ▼ security
    • CVE-2026-59198 affects this package: high ▼ security
    • CVE-2026-42311 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-59204 affects this package: high ▼ security
    • CVE-2026-42310 affects this package: high ▼ security
    • CVE-2026-42309 affects this package: high ▼ security
    • CVE-2026-54060 affects this package: high ▼ security
    • CVE-2026-33682 affects this package: high ▼ security
    • CVE-2026-10804 affects this package: high ▼ security
    • CVE-2026-59197 affects this package: high ▼ security
    • CVE-2026-40192 affects this package: high ▼ security
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 24 Sept 2026 · Analysed pypi/selvage@0.4.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

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 →

Vulnerabilities 45 findings
ID CVE Severity Vector Fix available
PYSEC-2026-2132 CVE-2026-7246 high CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H yes
GHSA-45hq-cxwh-f6vc CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4x4j-2g7c-83w6 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
GHSA-5x94-69rx-g8h2 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-5xmw-vc9v-4wf2 CVE-2026-42309 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-62p4-gmf7-7g93 CVE-2026-54058 high yes
GHSA-6r8x-57c9-28j4 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8v84-f9pq-wr9x CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9hw9-ch79-4vh6 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-cfh3-3jmp-rvhc CVE-2026-25990 high yes
GHSA-fj7v-r99m-22gq CVE-2026-59198 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L yes
GHSA-jjj6-mw9f-p565 CVE-2026-59200 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-phj9-mv4w-65pm CVE-2026-55380 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-pwv6-vv43-88gr CVE-2026-42311 high yes
GHSA-r73j-pqj5-w3x7 CVE-2026-42310 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-vjc4-5qp5-m44j CVE-2026-59204 high yes
GHSA-whj4-6x5x-4v2j CVE-2026-40192 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-wjx4-4jcj-g98j CVE-2026-42308 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xj96-63gp-2gmr CVE-2026-59197 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes
PYSEC-2026-165 CVE-2026-42308 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2249 CVE-2026-25990 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2250 CVE-2026-40192 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2251 CVE-2026-42309 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2252 CVE-2026-42311 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2253 CVE-2026-54059 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2254 CVE-2026-54060 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2255 CVE-2026-55379 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2256 CVE-2026-55380 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2257 CVE-2026-55798 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L yes
PYSEC-2026-2874 CVE-2026-42310 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3451 CVE-2026-59199 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3453 CVE-2026-59205 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3454 CVE-2026-59197 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H yes
PYSEC-2026-3493 CVE-2026-54058 none yes
PYSEC-2026-3494 CVE-2026-59198 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L yes
PYSEC-2026-3495 CVE-2026-59200 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3496 CVE-2026-59204 none yes
GHSA-9hjg-9r4m-mvj7 CVE-2024-47081 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-gc5v-m9x4-r6x2 CVE-2026-25645 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N yes
PYSEC-2026-1872 CVE-2024-47081 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N yes
PYSEC-2026-2275 CVE-2026-25645 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-7p48-42j8-8846 CVE-2026-33682 medium CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-vqwp-45wm-r9r5 CVE-2026-10804 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L yes
PYSEC-2026-212 CVE-2026-10804 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
PYSEC-2026-2285 CVE-2026-33682 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 104 packages
Packages resolved 104
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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.

Common questions

What is the io.github.selvage-lab/selvage MCP server?

io.github.selvage-lab/selvage is an MCP server listed in the public MCP registry as io.github.selvage-lab/selvage. An LLM-based code review MCP server with AST-powered smart context extraction. This page covers its PyPI package (selvage).

Is the io.github.selvage-lab/selvage MCP server safe to use?

io.github.selvage-lab/selvage scores 19 out of 100 on VerifyMCP. We recorded 45 known advisories against it as of 24 September 2026. 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 io.github.selvage-lab/selvage MCP server still maintained?

io.github.selvage-lab/selvage is still listed as active in the MCP registry. We last reached this channel on 24 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 io.github.selvage-lab/selvage MCP server under?

io.github.selvage-lab/selvage 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.