Base Security Scanner Mcp

io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.3Updated Oct 24, 2026

MCP server to scan smart contracts on Base for honeypots, rug pulls, and vulnerabilities.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that lets an assistant scan smart contracts on the Base network for honeypots, rug pulls and vulnerabilities.

What you can do
  • Scan smart contracts on Base for honeypot and rug-pull patterns.
  • Check contracts for security vulnerabilities.
  • Query Base mainnet through a configurable RPC endpoint.
  • No individual tools are documented in the supplied listing, so the exact operations are not described.
When to use it
Useful when you are evaluating or interacting with a Base token or contract and want an assistant to run a quick safety check before committing funds or integrating it.
Requirements
Runs as a local process over stdio, installed from the npm package base-security-scanner-mcp (Node.js required). Desktop client only; no web execution. Optional RPC_URL environment variable for a Base mainnet RPC endpoint, defaulting to the public Base RPC.
Before you install
The scanner reports are heuristic and may miss issues or flag safe contracts; do not treat a clean result as an audit or guarantee. A custom RPC_URL may carry an API key, so keep it out of shared configs. No tools or README are documented, so review the package before running it.

Installation

In SourceWeft

  1. Open Base Security Scanner Mcp in the dashboard and add it to a workspace.
  2. 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

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 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.