explain — Degenscan Intel MCP Tool
explain
(explain) is one of 30 tools on the
Degenscan Intel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain from your client
- Claude Code Degenscan Intel explain run in your project directory
- Claude Desktop Degenscan Intel explain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Degenscan Intel explain ~/.cursor/mcp.json
- VS Code Degenscan Intel explain .vscode/mcp.json
- Zed Degenscan Intel explain ~/.config/zed/settings.json
- Windsurf Degenscan Intel explain ~/.codeium/windsurf/mcp_config.json
- Cline Degenscan Intel explain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Degenscan Intel explain ~/.gemini/settings.json
- Grok Degenscan Intel explain .mcp.json (in your project root)
- ChatGPT Degenscan Intel explain Settings → Connectors → Advanced → Developer mode
- Claude.ai Degenscan Intel explain Settings → Connectors → Add custom connector
- LangChain Degenscan Intel explain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http degenscan-intel https://degenscan-intel.onrender.com/mcpOther tools on this server
- events_since
- impact_for
- exposure_graph
- regime_snapshot
- polymarket_context
- pulse
- price_for
- token_verdict
- funding_alerts
- whale_moves
- polymarket_top
- derivs_for
- news_for
- filings_for
- calendar
- oracle_forecast
- oracle_get
- polymarket_edge
- oracle_board
- oracle_track_record
- brief
- universe
- sources_status
- carry_funding_matrix
- carry_xdex
- carry_spot_perp
- carry_history
- carry_naked
- carry_watchdog
This list was read from the server itself, by connecting to it and calling tools/list on 4 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.