io.github.lordbasilaiassistant-sudo/contract-scanner

MCPcommunity
v1.0.2io.github.lordbasilaiassistant-sudoUnknownUpdated 6mo agonpmGitHub

Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding

Smart contract security scanner for AI agents. Analyze any Solidity contract for vulnerabilities before interacting with it. Add to your MCP client config: Tool | Description | Tier | ------|-------------|------| | Full security report with risk score 0-100, vulnerability findings, and actionable recommendations | Pro | | Compare two contracts side-by-side for clone detection and risk comparison…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
6mo agoLast update
Package
Authorio.github.lordbasilaiassistant-sudo
LicenseUnknown
Version1.0.2
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies60 resolved · 1 with advisories
Tool surface4 tools · none privileged
Security scan✓ Cleanv1.0.2 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev1.0.2 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

scanner_check_addressNo description published

This tool published no description. Forge does not invent one.

scanner_decode_calldataNo description published

This tool published no description. Forge does not invent one.

scanner_analyze_contractNo description published

This tool published no description. Forge does not invent one.

scanner_compare_contractsNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Smart contract security scanner for AI agents. Analyze any Solidity contract for vulnerabilities before interacting with it. Add to your MCP client config: Tool | Description | Tier | ------|-------------|------| | Full security report with risk score 0-100, vulnerability findings, and actionable recommendations | Pro | | Compare two contracts side-by-side for clone detection and risk comparison | Pro | | Quick check — contract vs EOA, verification status, risk flags | Free | | Decode raw…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.