io.github.rudimentall1/agentic-wallet-guardian-v3
PYPI · AGENTIC-WALLET-GUARDIAN-MCP
Explainable ALLOW/WARN/BLOCK risk decisions for AI agent actions before execution, signed as OAA.
Available components
Last scanned (16 hours ago)
Scores higher than 72% of PyPI servers
Category Crypto and Web3
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 Security82
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects mcp 2.0.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 332 tokens (~166/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 26 +1
- Stability: 0.90 → pass security
- 16 Oct 26 −5
- CVE-2026-59951 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −3
- Stability: pass → 0.83 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass security
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 −3
- Stability: pass → 0.80 functional
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 Oct 2026 · Analysed pypi/agentic-wallet-guardian-mcp@3.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-84m7-p3x7-pcfv | CVE-2026-59951 | 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 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
evaluate_action ~281
Evaluate a proposed blockchain action before executing it. Call this BEFORE submitting any transaction on behalf of a user or agent. Returns a JSON object with a decision ("ALLOW", "WARN", or "BLOCK"), a 0-100 risk score, and a human-readable explanation of which signals drove the decision. Treat "BLOCK" as a hard stop and "WARN" as something that needs explicit user confirmation before proceeding. Args: agent_id: Stable identifier for the calling agent (used for reputation history - reuse the same id across calls). wallet: The wallet address initiating the action. chain: Chain name, e.g. "ethereum", "base", "arbitrum", "polygon". action_type: One of "swap", "transfer", "approve", "contract_call", "bridge". target: Contract or recipient address, if applicable. from_token: Token symbol being sent/sold, if applicable. to_token: Token symbol being received/bought, if applicable. amount: Transaction amount in the relevant unit.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| agent_id | string | yes | – |
| amount | – | – | – |
| chain | string | yes | – |
| from_token | – | – | – |
| target | – | – | – |
| to_token | – | – | – |
| wallet | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_agent_history ~51
Return this agent's past decisions and current reputation score. Useful before evaluate_action if you want to check standing first, or after a WARN/BLOCK to review why.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.rudimentall1/agentic-wallet-guardian-v3 MCP server?
io.github.rudimentall1/agentic-wallet-guardian-v3 runs locally as a PyPI package, launched with uvx agentic-wallet-guardian-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 · agentic-wallet-guardian-mcp
claude mcp add rudimentall1-agentic-wallet-guardian-v3 -- uvx agentic-wallet-guardian-mcp
What is the io.github.rudimentall1/agentic-wallet-guardian-v3 MCP server?
io.github.rudimentall1/agentic-wallet-guardian-v3 is an MCP server listed in the public MCP registry as io.github.rudimentall1/agentic-wallet-guardian-v3. Explainable ALLOW/WARN/BLOCK risk decisions for AI agent actions before execution, signed as OAA. This page covers its PyPI package (agentic-wallet-guardian-mcp).
Is the io.github.rudimentall1/agentic-wallet-guardian-v3 MCP server safe to use?
io.github.rudimentall1/agentic-wallet-guardian-v3 scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 22 October 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.
What tools does the io.github.rudimentall1/agentic-wallet-guardian-v3 MCP server expose?
io.github.rudimentall1/agentic-wallet-guardian-v3 exposes 2 tools: evaluate_action, get_agent_history. Their descriptions and schemas cost roughly 332 tokens of context every time the server is loaded.
Is the io.github.rudimentall1/agentic-wallet-guardian-v3 MCP server still maintained?
io.github.rudimentall1/agentic-wallet-guardian-v3 is still listed as active in the MCP registry. We last reached this channel on 22 October 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.rudimentall1/agentic-wallet-guardian-v3 MCP server under?
io.github.rudimentall1/agentic-wallet-guardian-v3 declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.