io.github.lordbasilaiassistant-sudo/contract-scanner
NPM · @THRYX/CONTRACT-SCANNER-MCP-SERVER · SCANNED SEP 20
Smart contract security scanner — vulnerabilities, risk scores, and calldata decoding
Available components
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
- 32 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 166 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 503 tokens (~125/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.lordbasilaiassistant-sudo/contract-scanner MCP server?
io.github.lordbasilaiassistant-sudo/contract-scanner runs locally as an npm package, launched with npx -y @thryx/contract-scanner-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @thryx/contract-scanner-mcp-server
claude mcp add lordbasilaiassistant-sudo-contract-scanner -- npx -y @thryx/contract-scanner-mcp-server
{
"mcpServers": {
"lordbasilaiassistant-sudo-contract-scanner": {
"command": "npx",
"args": [
"-y",
"@thryx/contract-scanner-mcp-server"
]
}
}
} {
"servers": {
"lordbasilaiassistant-sudo-contract-scanner": {
"command": "npx",
"args": [
"-y",
"@thryx/contract-scanner-mcp-server"
]
}
}
} codex mcp add lordbasilaiassistant-sudo-contract-scanner -- npx -y @thryx/contract-scanner-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lordbasilaiassistant-sudo-contract-scanner": {
"type": "local",
"command": [
"npx",
"-y",
"@thryx/contract-scanner-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add lordbasilaiassistant-sudo-contract-scanner --command npx --arg -y --arg @thryx/contract-scanner-mcp-server
mcp_servers:
lordbasilaiassistant-sudo-contract-scanner:
command: "npx"
args: ["-y", "@thryx/contract-scanner-mcp-server"] {
"McpServers": {
"lordbasilaiassistant-sudo-contract-scanner": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@thryx/contract-scanner-mcp-server"
]
}
}
} assistant mcp add lordbasilaiassistant-sudo-contract-scanner -t stdio -c npx -a -y @thryx/contract-scanner-mcp-server
{
"mcpServers": {
"lordbasilaiassistant-sudo-contract-scanner": {
"command": "npx",
"args": [
"-y",
"@thryx/contract-scanner-mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −8
- Source repository: pass → fail ▼ security
- 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 −2
- Stability: pass → 0.83 functional
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/@thryx/contract-scanner-mcp-server@1.0.2
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 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 32 |
| 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 →
scanner_analyze_contract ~132
BEFORE interacting with ANY smart contract, call this to get a full security report. Fetches source code (if verified), analyzes bytecode, detects vulnerabilities (reentrancy, hidden mint, backdoors, proxy risks, access control issues), and returns a risk score 0-100 with actionable findings. One call = complete analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address to analyze (0x...) |
| api_key | string | – | Premium API key for unlimited scans. Free tier: 5 scans/hour. |
| chain | string | – | Chain: base, ethereum, arbitrum (default: base) |
No output schema declared.
No examples provided.
scanner_check_address ~115
Quick safety check on any address — is it a contract or EOA? Verified? Has selfdestruct, proxy, mint, pause, or blacklist? Returns risk flags in <1 second. Use this for fast triage before deciding whether to run a full scanner_analyze_contract scan.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to check (0x...) |
| api_key | string | – | Optional premium API key to bypass rate limits. |
| chain | string | – | Chain: base, ethereum, arbitrum (default: base) |
No output schema declared.
No examples provided.
scanner_compare_contracts ~134
Compare two smart contracts to see which is safer. Detects clones (identical bytecode), compares risk scores, identifies differences in access control and vulnerabilities. Use when choosing between two similar contracts (e.g., two DEX routers, two token versions).
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | yes | First contract address to compare (0x...) |
| address2 | string | yes | Second contract address to compare (0x...) |
| api_key | string | – | Premium API key for unlimited scans. Free tier: 5 scans/hour. |
| chain | string | – | Chain: base, ethereum, arbitrum (default: base) |
No output schema declared.
No examples provided.
scanner_decode_calldata ~122
Decode raw transaction calldata into human-readable function calls. Identifies the function being called, decodes parameters, and flags dangerous operations (unlimited approve, delegatecall, ownership transfers). Use BEFORE signing any transaction you don't fully understand.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | string | – | Contract ABI as JSON string for full parameter decoding. If not provided, common selectors (ERC-20, Uniswap, etc.) are matched automatically. |
| api_key | string | – | Optional premium API key to bypass rate limits. |
| calldata | string | yes | Raw calldata hex string (0x...) |
No output schema declared.
No examples provided.
What is the io.github.lordbasilaiassistant-sudo/contract-scanner MCP server?
io.github.lordbasilaiassistant-sudo/contract-scanner is an MCP server listed in the public MCP registry as io.github.lordbasilaiassistant-sudo/contract-scanner. Smart contract security scanner, vulnerabilities, risk scores, and calldata decoding. This page covers its npm package (@thryx/contract-scanner-mcp-server).
Is the io.github.lordbasilaiassistant-sudo/contract-scanner MCP server safe to use?
io.github.lordbasilaiassistant-sudo/contract-scanner scores 79 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.lordbasilaiassistant-sudo/contract-scanner MCP server expose?
io.github.lordbasilaiassistant-sudo/contract-scanner exposes 4 tools: scanner_analyze_contract, scanner_compare_contracts, scanner_check_address, scanner_decode_calldata. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Is the io.github.lordbasilaiassistant-sudo/contract-scanner MCP server still maintained?
io.github.lordbasilaiassistant-sudo/contract-scanner 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.lordbasilaiassistant-sudo/contract-scanner MCP server under?
io.github.lordbasilaiassistant-sudo/contract-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.