base-security-scanner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_contractB | Analyze a smart contract on Base mainnet for security issues including reentrancy patterns, access control, hidden mints, proxy patterns, and dangerous opcodes. |
| check_honeypotA | 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. |
| detect_rug_riskA | Score rug pull risk 0-100 for a token on Base mainnet. Checks ownership, liquidity, dangerous functions, honeypot status, and contract patterns. |
| analyze_bytecodeA | Disassemble contract bytecode on Base mainnet and identify known patterns (proxy, diamond, AMM, lending, ERC-20, ERC-721, etc). |
| check_token_permissionsA | Check owner permissions on a token: can mint? can pause? can blacklist? can change fees? Can disable trading? Ownership renounced? |
| get_contract_infoA | Get basic contract metadata on Base mainnet: is it a contract, bytecode size, ETH balance, transaction count. For tokens, also returns name/symbol/supply. |
| compare_bytecodeB | Compare bytecode of two contracts on Base mainnet for clone detection. Returns similarity score and whether they share the same code. |
| audit_reportA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap: analyze_bytecode identifies patterns, audit_report generates comprehensive reports, check_honeypot simulates trading, check_token_permissions examines ownership controls, compare_bytecode detects clones, detect_rug_risk scores risk, get_contract_info retrieves metadata, and scan_contract analyzes security issues. The descriptions precisely differentiate their functions, eliminating any ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, such as analyze_bytecode, check_honeypot, and detect_rug_risk. This uniformity makes the set predictable and easy to navigate, with no deviations in style or structure across the eight tools.
With 8 tools, the count is well-scoped for a security scanner focused on Base mainnet smart contracts. Each tool serves a specific, necessary function in the domain, from basic metadata retrieval to advanced risk analysis, without being excessive or insufficient for the server's purpose.
The tool set provides complete coverage for smart contract security analysis on Base mainnet, including bytecode analysis, honeypot detection, permission checks, risk scoring, contract comparison, metadata retrieval, and comprehensive scanning. There are no obvious gaps; agents can perform end-to-end security assessments without dead ends.