approval_risk

2 registry entries were observed exposing a tool named approval_risk — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 11,211 of 35,763 scannable entries (31%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. @celorodrigues/token-safety-mcpMCPcommunitylivetrust 60/100 · B
    v2.0.2
    ↓ 457/wk

    MCP server for Base L2 token safety: bytecode scans, swap simulations, approval and liquidity risk, and the live new-pool channel — six paid x402 surfaces plus x402 infrastructure tools, with payment handled server-side.

    ClaudeCursorCopilotChatGPTGemini
    io.github.baianomarceloeduardo-jpgMIT2d agonpmGitHubobserved · static extraction
    mcpmodel-context-protocolx402basetoken-securityhoneypot
  2. @iniit/defi-guard-mcpMCPcommunitytrust 60/100 · B
    v0.2.0

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

    ClaudeCursorCopilotGemini
    io.github.iinniittUnknown2mo agonpmGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for approval_risk