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.

Deus Witness

PYPI · DEUS-WITNESS

MCP proxy: holds risky tool calls for passkey approval; signed receipts you can check offline.

Available components

pypi · deus-witness 50
0 this week 50 Trust /100

Last scanned (1 day ago)

Scores higher than 51% of PyPI servers

Category Security

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to sipkigroup/witness). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, 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.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.2.54 → 0.2.56 functional
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.51 → 0.2.54 functional
  • 31 Oct 26 0
    • Malware scan: pass → unverified ▼ security
    • Package version: 0.2.50 → 0.2.51 functional
  • 30 Oct 26 0
    • Package version: 0.2.47 → 0.2.50 functional
    • Package version: 0.2.47 → 0.2.49 functional
  • 29 Oct 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
    • Package version: 0.2.45 → 0.2.47 functional
    • Package version: 0.2.45 → 0.2.46 functional
  • 28 Oct 26 0
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. 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
    • 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
    • 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
    • Package version: 0.2.41 → 0.2.45 functional
    • Package version: 0.2.41 → 0.2.44 functional
    • Package version: 0.2.41 → 0.2.43 functional
    • Package version: 0.2.41 → 0.2.42 functional
  • 27 Oct 26 0
    • Package version: 0.2.39 → 0.2.41 functional
    • Package version: 0.2.39 → 0.2.40 functional
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.2.36 → 0.2.39 functional
    • Package version: 0.2.36 → 0.2.38 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 4 Nov 2026 · Analysed pypi/deus-witness@0.2.56

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 sipkigroup/witness
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sipkigroup/witness/.github/workflows/release.yml@refs/heads/main
Rekor log index 3672255270
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:35d88ec6b3debcf5a8186f3c398ee78df34afa064f3fbd94d15c9dc00e97e08e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Dependencies 32 packages
Packages resolved 32
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 Deus Witness MCP server?

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

pypi · deus-witness

# add to Claude Code
claude mcp add sipkigroup-witness -- uvx deus-witness
Common questions

What is the Deus Witness MCP server?

Deus Witness is an MCP server listed in the public MCP registry as io.github.sipkigroup/witness. MCP proxy: holds risky tool calls for passkey approval; signed receipts you can check offline. This page covers its PyPI package (deus-witness).

Is the Deus Witness MCP server safe to use?

Deus Witness scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.

Is the Deus Witness MCP server still maintained?

Deus Witness 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 Deus Witness MCP server under?

Deus Witness 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.