crypto-inspector-mcp
Related Servers
Alternatives to crypto-inspector-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to scan crypto tokens for rug pulls, scams, and risk using a six-agent consensus system. It provides real-time security audits and risk scoring for tokens on Solana, Ethereum, Base, and BSC.62MIT
- AlicenseNot gradedqualityCmaintenanceToken safety oracle for AI agents. Honeypot detection, 17 scam pattern checks, LP lock verification across 6 EVM chains. Score 0-100 with risk flags. ERC Token Safety Score standard.1MIT
- AlicenseAqualityDmaintenanceSafety layer for autonomous DeFi agents. Scans contracts for exploit patterns, simulates transactions, blocks honeypots.4101MIT
- AlicenseBqualityDmaintenanceReal-time smart contract security for autonomous AI agents, offering tools for contract verification, wallet monitoring, drain detection, threat reporting, and leaderboards.197MIT

AgentRisk MCPofficial
FlicenseAqualityCmaintenanceEnables AI agents on Base to call a check_token_risk tool before trading, providing honeypot detection, LP-lock verification, brand impersonation checks, and live sell simulation across Uniswap V2/V3/V4 and Aerodrome with a clear risk score and should-trade decision.1-
SolSentry MCPofficial
AlicenseAqualityBmaintenanceProvides post-deploy Solana threat intelligence, enabling AI agents to check operators, tokens, and network stats for detecting rug pulls and malicious activity.527MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusing it with another. The single inspect_token tool has a clearly defined purpose, so an agent cannot misselect it.
The only tool name follows a clear verb_noun convention (inspect_token) and accurately reflects its function. There is no set of tools to establish a broader naming pattern, but the name is well-formed and self-explanatory.
The server exposes only one tool for what is described as a comprehensive security and liquidity check. This feels too thin for the as a token inspection MCP, which would typically benefit from separately callable tools for specific aspects such as liquidity details, holder analysis, or price data.
The tool surface is extremely limited, offering only a single monolithic action. While the description claims a comprehensive check, there are no additional tools for focused queries, comparing tokens, or retrieving specific aspects of the analysis, leaving obvious gaps in an inspection workflow.