Home / MCP registry index / fun.paxie.api/data
Paxie.Matrix Data API
fun.paxie.api/data in the official MCP registry.
Endpoint https://api.paxie.fun/mcp.
The registry describes it as: Memecoin intel for agents: Robinhood Chain + Solana bursts, rug checks, call verdicts. Pay via x402.
We read its 24 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
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
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 rh_token_verdict 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
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/fun-paxie-api-data)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.