io.github.lordbasilaiassistant-sudo/base-security-scanner-mcp
NPM · BASE-SECURITY-SCANNER-MCP · SCANNED AUG 3
MCP server to scan smart contracts on Base for honeypots, rug pulls, and vulnerabilities.
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 148 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 459 tokens (~57/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 · base-security-scanner-mcp
claude mcp add lordbasilaiassistant-sudo-base-security-scanner- -- npx -y base-security-scanner-mcp
codex mcp add lordbasilaiassistant-sudo-base-security-scanner- -- npx -y base-security-scanner-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lordbasilaiassistant-sudo-base-security-scanner-": {
"type": "local",
"command": [
"npx",
"-y",
"base-security-scanner-mcp"
],
"enabled": true
}
}
} openclaw mcp add lordbasilaiassistant-sudo-base-security-scanner- --command npx --arg -y --arg base-security-scanner-mcp
mcp_servers:
lordbasilaiassistant-sudo-base-security-scanner-:
command: "npx"
args: ["-y", "base-security-scanner-mcp"] {
"mcpServers": {
"lordbasilaiassistant-sudo-base-security-scanner-": {
"command": "npx",
"args": [
"-y",
"base-security-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 +48
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 +16
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −41
- 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/[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.
analyze_bytecode ~55
Disassemble contract bytecode on Base mainnet and identify known patterns (proxy, diamond, AMM, lending, ERC-20, ERC-721, etc).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address on Base mainnet |
No output schema declared.
No examples provided.
audit_report ~63
Generate a full security audit report for a token on Base mainnet. Combines contract scan, honeypot check, rug risk score, bytecode analysis, and permission checks into one comprehensive report.
| Name | Type | Req | Description |
|---|---|---|---|
| token_address | string | yes | Token contract address on Base mainnet |
No output schema declared.
No examples provided.
check_honeypot ~61
Check if a token on Base mainnet is a honeypot by simulating buy and sell via Uniswap V2 router. Returns buy/sell ability and estimated taxes.
| Name | Type | Req | Description |
|---|---|---|---|
| token_address | string | yes | Token contract address on Base mainnet |
No output schema declared.
No examples provided.
check_token_permissions ~52
Check owner permissions on a token: can mint? can pause? can blacklist? can change fees? Can disable trading? Ownership renounced?
| Name | Type | Req | Description |
|---|---|---|---|
| token_address | string | yes | Token contract address on Base mainnet |
No output schema declared.
No examples provided.
compare_bytecode ~56
Compare bytecode of two contracts on Base mainnet for clone detection. Returns similarity score and whether they share the same code.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | yes | First contract address |
| address2 | string | yes | Second contract address |
No output schema declared.
No examples provided.
detect_rug_risk ~59
Score rug pull risk 0-100 for a token on Base mainnet. Checks ownership, liquidity, dangerous functions, honeypot status, and contract patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| token_address | string | yes | Token contract address on Base mainnet |
No output schema declared.
No examples provided.
get_contract_info ~60
Get basic contract metadata on Base mainnet: is it a contract, bytecode size, ETH balance, transaction count. For tokens, also returns name/symbol/supply.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract or EOA address on Base mainnet |
No output schema declared.
No examples provided.
scan_contract ~53
Analyze a smart contract on Base mainnet for security issues including reentrancy patterns, access control, hidden mints, proxy patterns, and dangerous opcodes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address on Base mainnet |
No output schema declared.
No examples provided.