io.github.veriswarm/veriswarm-mcp
PYPI · VERISWARM-MCP
VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol
Available components
Last scanned (2 hours ago)
Scores higher than 58% of PyPI servers
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 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 veriswarm/veriswarm-sdk). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6522 tokens (~63/item across 102 items; 102 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill_agent" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 102 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +11
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.4.0 → 0.6.0 functional
- 2 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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/veriswarm-mcp@0.6.0
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 | veriswarm/veriswarm-sdk |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/veriswarm/veriswarm-sdk/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.6.0 |
| Rekor log index | 3678348090 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c13bde26ac0af8708cc1cae20a04c55f605bf6650f407a02394211b58029b940 |
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 →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
verify_response ~56
Cross-model verification — route a response through multiple LLMs and check consensus. Defends against memory poisoning (OWASP ASI06). Results are logged to Vault.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | – |
| response | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
workflow_stats ~46
Get workflow usage statistics: execution counts, success rates, and LLM costs. days: time period in days (default 30, max 90)
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.veriswarm/veriswarm-mcp server?
io.github.veriswarm/veriswarm-mcp runs locally as a PyPI package, launched with uvx veriswarm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · veriswarm-mcp
claude mcp add veriswarm-veriswarm-mcp -- uvx veriswarm-mcp
What is the io.github.veriswarm/veriswarm-mcp server?
io.github.veriswarm/veriswarm-mcp is listed in the public MCP registry as io.github.veriswarm/veriswarm-mcp. VeriSwarm MCP Server, Trust infrastructure for AI agents via Model Context Protocol. This page covers its PyPI package (veriswarm-mcp).
Is the io.github.veriswarm/veriswarm-mcp server safe to use?
io.github.veriswarm/veriswarm-mcp scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.
What tools does the io.github.veriswarm/veriswarm-mcp server expose?
io.github.veriswarm/veriswarm-mcp exposes 102 tools: check_trust, check_decision, get_my_score, get_score_history, get_score_breakdown, and 97 more. Their descriptions and schemas cost roughly 6,522 tokens of context every time the server is loaded.
Is the io.github.veriswarm/veriswarm-mcp server still maintained?
io.github.veriswarm/veriswarm-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.veriswarm/veriswarm-mcp server under?
io.github.veriswarm/veriswarm-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.