deployer-reputation-mcp
Related Servers
Alternatives to deployer-reputation-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRug pull risk scores and on-chain forensics for memecoins on Solana, Ethereum, Base and Robinhood Chain - launch-bundle detection, funding-origin tracing, deployer history, insider networks and whale flow. 15 read-only tools.2315239 npmMIT
- AlicenseAqualityAmaintenanceSolana memecoin rug check and token risk for trading agents in the trenches: pump.fun launches, calibrated rug probability with a published hit rate, sniper, insider and bundle detection, holder clusters, KOL trades, wallet history and a live sellability check for memecoins. Available as a remote MCP endpoint (OAuth or API key) and as an npm stdio package.2648 npm3MIT

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.517 npmMIT- FlicenseNot gradedqualityDmaintenanceAgent-native scored launch intelligence for Base blockchain, providing opportunity/risk scores and AVOID/WATCH/HOT decisions per fresh launch via x402 pay-per-call API. Enables trading/research agents to act directly on structured launch data.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to query real-time labelled pump.fun intelligence—launch risk cards, creator reputation, rug/graduation flags, wallet profiles, and market regime—with paid endpoints settled per request via x402 USDC on Solana and free sample/regime tools.MIT
- AlicenseAqualityBmaintenanceOn-chain Solana cabal & rug detection as an MCP server. Scans any Solana token mint before your agent buys and returns an Exit-Liquidity Risk verdict.1184 npmMIT
TDQS
Scored across 2 tools
The two tools are closely related but clearly differentiated by purpose: cluster_launches provides membership and counts, while deployer_reputation produces heuristic scores and evidence. The descriptions explicitly tell the agent which tool to use based on whether scores are needed, minimizing misselection risk.
Both names are compound nouns with underscore separation, following a similar pattern. 'cluster_launches' could be misread as an imperative verb, but 'deployer_reputation' is clearly a noun, and the overall naming style is consistent and legible.
With only two tools, the server sits on the thin side of the acceptable range. However, both tools serve distinct and necessary steps in the same workflow, so each earns its place, even though the count feels minimal.
The server covers the two core operations of the domain: grouping launches into clusters and scoring those clusters with evidence. Minor gaps exist—such as no tool for single-deployer lookup or label verification—but the descriptions explicitly scope those responsibilities to the caller's upstream pipeline.