io.github.iinniitt/defi-guard-mcp
NPM · @INIIT/DEFI-GUARD-MCP
DeFi safety checks on Base before you sign: honeypot, owner-power scan, approval risk, Aave health.
Available components
Last scanned (20 hours ago)
Scores higher than 66% of npm 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 109 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 118 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 667 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → 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 4 Nov 2026 · Analysed npm/@iniit/defi-guard-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| 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 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 30 |
| 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 →
aave_position_health ~69
Check the live health of an Aave V3 position on Base: health factor, total collateral/debt (USD), LTV and liquidation threshold. A health factor below 1.0 means the position is liquidatable.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM address of the position owner |
No output schema declared.
No examples provided.
approval_risk ~141
Assess the risk of an existing ERC-20 approval on Base BEFORE it can be abused: reads the live allowance an owner has granted a spender, flags UNLIMITED approvals (the allowance-drain vector — a compromised or malicious spender can pull up to the allowance), and reports whether the spender is a contract. Unlimited allowance to an EOA is a classic scam setup. Use before signing an approval, or to audit standing approvals.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | The wallet that granted the approval |
| spender | string | yes | The address allowed to spend (router, contract, or EOA) |
| token | string | yes | The ERC-20 token address |
No output schema declared.
No examples provided.
quote_swap ~111
Real exact-input swap quote on Base via Uniswap V3 QuoterV2. Tries all fee tiers (0.01%, 0.05%, 0.3%, 1%) and returns the best executable output. Amounts are human units (e.g. '0.5').
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | Human-readable input amount, e.g. '0.5' |
| tokenIn | string | yes | Input token address |
| tokenOut | string | yes | Output token address |
No output schema declared.
No examples provided.
scan_dangerous_capabilities ~135
Scan a token/contract's DEPLOYED BYTECODE on Base for owner-only powers that can harm holders — mint, pause, blacklist, adjustable fees/taxes, max-tx limits, trading toggles, and proxy upgradeability. Flags the PRESENCE of each capability (a selector match in the code), i.e. what the operator COULD do, independent of the token's claims. No explorer API key needed. Heuristic: matches 4-byte selectors in runtime bytecode; a minimal proxy hides its real logic in the implementation (reported).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Contract/token address on Base |
No output schema declared.
No examples provided.
token_risk_snapshot ~88
Liquidity risk snapshot of an ERC-20 on Base: metadata plus REAL market depth measured by round-trip quotes (WETH -> token -> WETH) at two trade sizes. High round-trip loss = thin/illiquid or high-fee market; a token you cannot exit is a risk regardless of its chart.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | ERC-20 token address on Base |
No output schema declared.
No examples provided.
token_safety_screen ~123
Pre-trade safety screen for an ERC-20 on Base — the 'is this safe to buy/approve BEFORE I sign' check. Verifies you can actually SELL it back (honeypot detection), measures the real round-trip cost (buy+sell fees/tax), and reports whether ownership is renounced (a live owner can often change taxes, pause, or mint). Returns a single risk verdict. On-chain only; no oracle, no trust in the token's own claims.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | ERC-20 token address on Base |
No output schema declared.
No examples provided.
How do I install the io.github.iinniitt/defi-guard-mcp server?
io.github.iinniitt/defi-guard-mcp runs locally as an npm package, launched with npx -y @iniit/defi-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @iniit/defi-guard-mcp
claude mcp add iinniitt-defi-guard-mcp -- npx -y @iniit/defi-guard-mcp
What is the io.github.iinniitt/defi-guard-mcp server?
io.github.iinniitt/defi-guard-mcp is listed in the public MCP registry as io.github.iinniitt/defi-guard-mcp. DeFi safety checks on Base before you sign: honeypot, owner-power scan, approval risk, Aave health. This page covers its npm package (@iniit/defi-guard-mcp).
Is the io.github.iinniitt/defi-guard-mcp server safe to use?
io.github.iinniitt/defi-guard-mcp scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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.iinniitt/defi-guard-mcp server expose?
io.github.iinniitt/defi-guard-mcp exposes 6 tools: aave_position_health, quote_swap, token_risk_snapshot, token_safety_screen, scan_dangerous_capabilities, approval_risk. Their descriptions and schemas cost roughly 667 tokens of context every time the server is loaded.
Is the io.github.iinniitt/defi-guard-mcp server still maintained?
io.github.iinniitt/defi-guard-mcp 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 io.github.iinniitt/defi-guard-mcp server under?
io.github.iinniitt/defi-guard-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.