Home / MCP registry index / ai.coingraph/coingraph
CoinGraph
ai.coingraph/coingraph in the official MCP registry.
Endpoint https://coingraph.ai/api/mcp. Source: github.com/eventgraphai/coingraph.
The registry describes it as: Pre-trade crypto intelligence: survival rating, order-book depth, unlocks and contract flags.
We read its 22 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_tokens get_token_snapshot get_token_timeline check_token get_token_brief ask_about_token watch_tokens get_market_overview lookup_address get_track_record get_proof get_service_status run_trade_gatekeeper run_wallet_guard run_due_diligence_analyst run_opportunity_scout run_leverage_radar run_whale_watch run_portfolio_checkup run_treasury_steward run_alert_watchtower run_daily_market_brief
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-coingraph-coingraph)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.