solana_token_risk_scan — agentforge MCP Tool
solana_token_risk_scan
(solana token risk scan) is one of 20 tools on the
agentforge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call solana_token_risk_scan from your client
- Claude Code agentforge solana_token_risk_scan run in your project directory
- Claude Desktop agentforge solana_token_risk_scan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agentforge solana_token_risk_scan ~/.cursor/mcp.json
- VS Code agentforge solana_token_risk_scan .vscode/mcp.json
- Zed agentforge solana_token_risk_scan ~/.config/zed/settings.json
- Windsurf agentforge solana_token_risk_scan ~/.codeium/windsurf/mcp_config.json
- Cline agentforge solana_token_risk_scan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agentforge solana_token_risk_scan ~/.gemini/settings.json
- Grok agentforge solana_token_risk_scan .mcp.json (in your project root)
- ChatGPT agentforge solana_token_risk_scan Settings → Connectors → Advanced → Developer mode
- Claude.ai agentforge solana_token_risk_scan Settings → Connectors → Add custom connector
- LangChain agentforge solana_token_risk_scan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentforge https://agentforge-taupe.vercel.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.