Contract Security Scanner
NPM · @FINO314-OSS/CONTRACT-SCANNER-MCP · SCANNED AUG 3
Scans Base L2 smart contracts for security risks. Risk score 0-100, detects backdoors & proxies.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 138 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 351 tokens (~117/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @fino314-oss/contract-scanner-mcp
claude mcp add fino-oss-contract-scanner -- npx -y @fino314-oss/contract-scanner-mcp
codex mcp add fino-oss-contract-scanner -- npx -y @fino314-oss/contract-scanner-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fino-oss-contract-scanner": {
"type": "local",
"command": [
"npx",
"-y",
"@fino314-oss/contract-scanner-mcp"
],
"enabled": true
}
}
} openclaw mcp add fino-oss-contract-scanner --command npx --arg -y --arg @fino314-oss/contract-scanner-mcp
mcp_servers:
fino-oss-contract-scanner:
command: "npx"
args: ["-y", "@fino314-oss/contract-scanner-mcp"] {
"mcpServers": {
"fino-oss-contract-scanner": {
"command": "npx",
"args": [
"-y",
"@fino314-oss/contract-scanner-mcp"
]
}
}
} 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.
- 2 Aug 26 +32
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@fino314-oss/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 104 packages
104 packages in the resolved dependency tree · 102 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
batch_scan ~79
Scans multiple contracts at once and returns a risk comparison table. Useful for: - Comparing multiple DeFi protocols before choosing one - Auditing all contracts in a project - Quick portfolio risk assessment Scans up to 5 contracts in parallel.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | List of 2-5 contract addresses on Base L2 |
No output schema declared.
No examples provided.
interpret_risk ~115
Given a risk score and findings from a scan, provides an actionable recommendation. Returns: SAFE_TO_USE / PROCEED_WITH_CAUTION / HIGH_RISK / DO_NOT_USE
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Type of contract being evaluated |
| has_backdoor | boolean | — | Whether rescueTokens/withdrawAll detected |
| has_unverified_source | boolean | yes | Whether source code is unverified |
| risk_label | string | yes | Risk label from scan_contract |
| risk_score | number | yes | Risk score from scan_contract |
No output schema declared.
No examples provided.
scan_contract ~157
Scans an EVM smart contract on Base L2 for security risks. Analyzes: - Source code verification status - Risky function selectors (mint, blacklist, pause, backdoors, etc.) - Proxy / upgradeability patterns - Contract age (new contracts = higher risk) - Transaction activity Returns a risk score (0-100) and categorized findings (critical/high/medium/good). Use this before: - Interacting with an unknown contract - Approving a token spend - Investing in a DeFi protocol - Auditing a smart contract
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address on Base L2 to scan |
| include_raw | boolean | — | Include raw findings array in response (default: false) |
No output schema declared.
No examples provided.