rh_token_verdict — Paxie.Matrix Data API MCP Tool
rh_token_verdict
(rh token verdict) is one of 24 tools on the
Paxie.Matrix Data API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call rh_token_verdict from your client
- Claude Code Paxie.Matrix Data API rh_token_verdict run in your project directory
- Claude Desktop Paxie.Matrix Data API rh_token_verdict ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Paxie.Matrix Data API rh_token_verdict ~/.cursor/mcp.json
- VS Code Paxie.Matrix Data API rh_token_verdict .vscode/mcp.json
- Zed Paxie.Matrix Data API rh_token_verdict ~/.config/zed/settings.json
- Windsurf Paxie.Matrix Data API rh_token_verdict ~/.codeium/windsurf/mcp_config.json
- Cline Paxie.Matrix Data API rh_token_verdict ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Paxie.Matrix Data API rh_token_verdict ~/.gemini/settings.json
- Grok Paxie.Matrix Data API rh_token_verdict .mcp.json (in your project root)
- ChatGPT Paxie.Matrix Data API rh_token_verdict Settings → Connectors → Advanced → Developer mode
- Claude.ai Paxie.Matrix Data API rh_token_verdict Settings → Connectors → Add custom connector
- LangChain Paxie.Matrix Data API rh_token_verdict pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data https://api.paxie.fun/mcpOther tools on this server
- rh_token_rugcheck
- rh_bursts_live
- rh_bursts_history
- rh_pools_new
- rh_pool_flow
- rh_crews
- sol_bursts_live
- sol_bursts_history
- sol_wallet_leaders
- launch_snapshot
- rh_token_precall
- sol_token_verdict
- scanner_grade
- sol_callers_leaderboard
- sol_calls_outcomes
- sol_calls_live
- sol_grads_live
- sol_grads_history
- desk_trades
- sol_wallet_copy_stats
- stream_pass
- sample
- status
This list was read from the server itself, by connecting to it and calling tools/list on 9 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.