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.

io.github.iinniitt/defi-guard-mcp

NPM · @INIIT/DEFI-GUARD-MCP · SCANNED SEP 20

DeFi safety checks on Base before you sign: honeypot, owner-power scan, approval risk, Aave health.

0 this week 84 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Install

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

# add to Claude Code
claude mcp add iinniitt-defi-guard-mcp -- npx -y @iniit/defi-guard-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "iinniitt-defi-guard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@iniit/defi-guard-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "iinniitt-defi-guard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@iniit/defi-guard-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add iinniitt-defi-guard-mcp -- npx -y @iniit/defi-guard-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iinniitt-defi-guard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@iniit/defi-guard-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add iinniitt-defi-guard-mcp --command npx --arg -y --arg @iniit/defi-guard-mcp
# ~/.hermes/config.yaml
mcp_servers:
  iinniitt-defi-guard-mcp:
    command: "npx"
    args: ["-y", "@iniit/defi-guard-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "iinniitt-defi-guard-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@iniit/defi-guard-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add iinniitt-defi-guard-mcp -t stdio -c npx -a -y @iniit/defi-guard-mcp
// mcp.json
{
  "mcpServers": {
    "iinniitt-defi-guard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@iniit/defi-guard-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 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 20 Sept 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 →

Dependencies 111 packages
Packages resolved 111
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~667 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
addressstringyesEVM 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.

NameTypeReqDescription
ownerstringyesThe wallet that granted the approval
spenderstringyesThe address allowed to spend (router, contract, or EOA)
tokenstringyesThe 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').

NameTypeReqDescription
amountInstringyesHuman-readable input amount, e.g. '0.5'
tokenInstringyesInput token address
tokenOutstringyesOutput 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).

NameTypeReqDescription
tokenstringyesContract/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.

NameTypeReqDescription
tokenstringyesERC-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.

NameTypeReqDescription
tokenstringyesERC-20 token address on Base

No output schema declared.

No examples provided.

Common questions

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 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.