- Home
- MCP servers
- Honeypot Detector
Honeypot Detector
- python
2
GitHub Stars
python
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"kukapay-honeypot-detector-mcp": {
"command": "uv",
"args": [
"--directory",
"/path/to/honeypot-detector-mcp",
"run",
"main.py"
]
}
}
}You can deploy and run the Honeypot Detector MCP server to assess token contracts on Ethereum, BSC, and Base. It analyzes a token address to determine honeypot risk and outputs a detailed Markdown report including buy/sell taxes and contract status so you can make informed decisions.
How to use
You interact with the Honeypot Detector MCP server through an MCP client. Use the provided stdio configuration to run the server locally, and then invoke the check_honeypot tool with a token address to generate a Markdown-style report. The report includes the token name, address, honeypot status, risk level, taxes, and whether the contract code is open source.
How to install
Prerequisites you need before installing:
• Python 3.10 or higher
• uv (recommended package manager)
Step 1: Clone the repository
git clone https://github.com/kukapay/honeypot-detector-mcp.git
cd honeypot-detector-mcp
Step 2: Install dependencies
uv sync
Step 3: Install as a Claude Desktop MCP (optional desktop deployment)
uv run mcp install main.py --name "Honeypot Detector"
Configuration snippet you may adapt for your environment
{
"mcpServers": {
"Honeypot Detector": {
"command": "uv",
"args": [ "--directory", "/path/to/honeypot-detector-mcp", "run", "main.py" ]
}
}
}
Replace /path/to/honeypot-detector-mcp with your actual installation path.
## Additional configuration notes
The server is designed to run as a local MCP server using the stdio interface. If you need to adapt the path or command, modify the `args` array in the MCP server configuration accordingly and ensure the working directory points to your installation.
## Examples and available tool
The Honeypot Detector exposes the `check_honeypot` tool. It accepts a token address as input and returns a Markdown report containing the token name, address, honeypot status, risk level, buy/sell/transfer taxes, and contract code openness.
Input example
Please check if the token at address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 is a honeypot.
Output Markdown
Honeypot Analysis for USDC
- Address: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
- Is Honeypot: False
- Risk Level: Low
- Buy Tax: 0%
- Sell Tax: 0%
- Transfer Tax: 0%
- Contract Code Open Source: True
## Available tools
### check\_honeypot
Takes a token address as input and returns a Markdown report with honeypot status, risk level, taxes, and contract openness.