Contract Security Scanner
NPM · @FINO314-OSS/CONTRACT-SCANNER-MCP
Scans Base L2 smart contracts for security risks. Risk score 0-100, detects backdoors & proxies.
Available components
Last scanned (8 hours ago)
Scores higher than 62% of npm servers
Category Security
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 102 dependencies flagged as unhealthy. 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 232 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 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.
- 19 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/@fino314-oss/contract-scanner-mcp@1.0.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 31 |
| 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 →
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.
How do I install the Contract Security Scanner MCP server?
Contract Security Scanner runs locally as an npm package, launched with npx -y @fino314-oss/contract-scanner-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @fino314-oss/contract-scanner-mcp
claude mcp add fino-oss-contract-scanner -- npx -y @fino314-oss/contract-scanner-mcp
What is the Contract Security Scanner MCP server?
Contract Security Scanner is an MCP server listed in the public MCP registry as io.github.fino-oss/contract-scanner. Scans Base L2 smart contracts for security risks. Risk score 0-100, detects backdoors & proxies. This page covers its npm package (@fino314-oss/contract-scanner-mcp).
Is the Contract Security Scanner MCP server safe to use?
Contract Security Scanner scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 Contract Security Scanner MCP server expose?
Contract Security Scanner exposes 3 tools: scan_contract, batch_scan, interpret_risk. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.
Is the Contract Security Scanner MCP server still maintained?
Contract Security Scanner is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Contract Security Scanner MCP server under?
Contract Security 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.