
Contract Scanner
io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.2Updated Oct 24, 2026
Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding
Overview
A local MCP server that scans smart contracts for vulnerabilities, assigns risk scores and decodes calldata for an AI assistant.
- What you can do
- Scan smart contracts for security vulnerabilities and receive risk scores for the findings, according to the registry description. Decode calldata so an assistant can explain what a transaction or function call is doing. Fetch verified contract source code through the Basescan or Etherscan API keys when scanning contracts on those networks. Point scans at a chosen RPC endpoint, which defaults to Base mainnet. The manifest lists no individual tools, so the exact commands and outputs are not documented here.
- When to use it
- Useful when reviewing or auditing smart contracts and you want an assistant to surface vulnerabilities, risk ratings and decoded transaction data in the same conversation. Suited to developers or security reviewers working on EVM contracts, especially on Base or networks covered by Etherscan.
- Requirements
- Runs as a local process installed from the npm package, so Node.js is needed. Requires a BASESCAN_API_KEY and/or ETHERSCAN_API_KEY to fetch verified source code, and an optional RPC_URL (defaults to Base mainnet). A THRYX_API_KEY is offered for unlimited scans. Network access to the relevant APIs and RPC endpoint is required.
Installation
In SourceWeft
- Open Contract Scanner in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.