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

io.github.SureshKhemka/constraints-registry

PYPI · CONSTRAINTS-REGISTRY · SCANNED AUG 3

Policy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep.

+10 this week 34 Trust /100
Trust breakdown (6 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 →

Supply Chain Security91
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects mcp 1.23.3, reached via semgrep > mcp. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 3 of 78 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

pypi · constraints-registry

# add to Claude Code
claude mcp add sureshkhemka-constraints-registry -- uvx constraints-registry
# add to Codex CLI
codex mcp add sureshkhemka-constraints-registry -- uvx constraints-registry
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sureshkhemka-constraints-registry": {
      "type": "local",
      "command": [
        "uvx",
        "constraints-registry"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sureshkhemka-constraints-registry --command uvx --arg constraints-registry
# ~/.hermes/config.yaml
mcp_servers:
  sureshkhemka-constraints-registry:
    command: "uvx"
    args: ["constraints-registry"]
// mcp.json
{
  "mcpServers": {
    "sureshkhemka-constraints-registry": {
      "command": "uvx",
      "args": [
        "constraints-registry"
      ]
    }
  }
}
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.

  • 3 Aug 26 +9
    • CVE-2026-52869 affects this package: high security
    • CVE-2026-59950 affects this package: high security
    • CVE-2026-52870 affects this package: high security
    • Known CVEs: unverified → fail security
    • Dependency health: unverified → 0.98 functional
  • 2 Aug 26 +20
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • The scripts that run when this package is installed changed: build_backend security
    • License: unverified → fail functional
    • Security disclosure: fail → unverified functional
    • Maintenance: unverified → pass functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Licence: Apache Software License functional
  • 1 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 24

    First indexed and scored.

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 3 Aug 2026 · Analysed pypi/[email protected]

Provenance none

Ecosystem: pypi · Outcome: none

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build
Vulnerabilities 6 findings
ID CVE Severity Vector Fix available
GHSA-hvrp-rf83-w775 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
PYSEC-2026-3481 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes
Dependencies 78 packages

78 packages in the resolved dependency tree · 3 stale.

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.

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.