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.

P31 Governed Agent CLI

NPM · @P31CA/CLI · 3 COMPONENTS

Capability-routed CLI/MCP: signed provenance exports, WCAG-validated themes, sovereign deploy modes.

0 this week 44 Trust /100

Last scanned (17 hours ago)

Scores higher than 20% of npm servers

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects drizzle-orm 0.36.4, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 74 of 219 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to p31labs/p31-cli). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

What we tested

Checks we ran (9)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (5)

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.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

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.

  • 11 Nov 26 0
    • CVE-2026-115779 affects this package: high ▼ security
  • 7 Nov 26 +5
    • CVE-2026-41907 affects this package: high ▼ security
    • CVE-2026-114143 affects this package: high ▼ security
    • CVE-2026-39356 affects this package: high ▼ security
    • CVE-2026-114141 affects this package: high ▼ security
    • CVE-2026-114144 affects this package: high ▼ security
    • CVE-2026-114142 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Dependency health: unverified → 0.84 ▲ functional
  • 6 Nov 26 39

    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 22 Nov 2026 · Analysed npm/@p31ca/cli@3.1.6

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo p31labs/p31-cli
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/p31labs/p31-cli/.github/workflows/publish-npm.yml@refs/heads/main
Rekor log index 3716518220
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:512becdae384f37acf2d43d3e4badfc154eac39491b1cb07e4e9614c5744607a3f18b102d86c124518215b53b2c8ec7b8216c2714db3fdad9eded8063

Background: How many MCP packages publish verified provenance →

Vulnerabilities 8 findings
ID CVE Severity Vector Fix available
GHSA-gpj5-g38j-94v9 CVE-2026-39356 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-chp3-j5qr-2vfr CVE-2026-115779 medium yes
GHSA-4qx8-w7c3-pj3p CVE-2026-114141 high yes
GHSA-9j65-hcg3-gc64 CVE-2026-114143 high yes
GHSA-9qmh-m7c6-f92p CVE-2026-114144 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-h895-cgqg-jf52 CVE-2026-114142 high yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 219 packages
Packages resolved 219
Deprecated 2
Stale 70
No linked repository 2
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.

Install

How do I install the P31 Governed Agent CLI MCP server?

P31 Governed Agent CLI runs locally as an npm package, launched with npx -y @p31ca/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @p31ca/cli

# add to Claude Code
claude mcp add org-p31ca-governed-agent-cli -- npx -y @p31ca/cli
Common questions

What is the P31 Governed Agent CLI MCP server?

P31 Governed Agent CLI is an MCP server listed in the public MCP registry as org.p31ca/governed-agent-cli. Capability-routed CLI/MCP: signed provenance exports, WCAG-validated themes, sovereign deploy modes. This page covers its npm package (@p31ca/cli).

Is the P31 Governed Agent CLI MCP server safe to use?

P31 Governed Agent CLI scores 44 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 22 November 2026. It declares no install or post-install scripts. 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 P31 Governed Agent CLI MCP server still maintained?

P31 Governed Agent CLI is still listed as active in the MCP registry. We last reached this channel on 22 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 P31 Governed Agent CLI MCP server under?

P31 Governed Agent CLI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the P31 Governed Agent CLI MCP server?

VerifyMCP ran 9 checks on P31 Governed Agent CLI, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about P31 Governed Agent CLI: Schema quality, Stability, Tool coverage, Tool safety and 1 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.