honeypot-detector-mcp
Related Servers
Alternatives to honeypot-detector-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server that provides AI agents with crypto token safety checks (honeypot, liquidity, rug risk) and alpha signals (smart money buys, fresh rug radar) across PulseChain, Monad, Base, and BSC.48 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that detects potential risks in Solana meme tokens using Solsniffer API, helping AI agents avoid rug pulls and unsafe projects.MIT
- AlicenseAqualityCmaintenanceAn MCP server for AI agents to discover and trade new token launches on Base chain.517 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that detects potential risks in Solana meme tokens, helping AI agents avoid rug pulls and unsafe projects.21MIT
- AlicenseAqualityCmaintenanceAn MCP server that tracks newly created liquidity pools on Pancake Swap.110MIT
- AlicenseAqualityDmaintenanceReal-time DeFi analytics MCP server for AI agents. Provides token risk analysis, yield scanning, and wallet exposure checking across Base, Ethereum, and Arbitrum.37 npm1MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clearly defined purpose: checking if a token address is a honeypot.
The single tool name 'check_honeypot' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations to assess.
A single tool is too few for a server with 'detector' in its name, suggesting a broader scope. While the tool is functional, the server lacks supporting tools like listing recent honeypots, checking multiple addresses, or getting detailed statistics, making it feel thin and incomplete.
The server's purpose appears to be honeypot detection, but with only a check tool, there are significant gaps. Missing operations include batch checks, historical analysis, risk scoring, or integration with other security tools, which limits agent workflows and creates dead ends for complex tasks.