Home / MCP registry index / dev.xroot/token-operations
dev.xroot/token-operations
dev.xroot/token-operations in the official MCP registry.
Endpoint https://api.xroot.dev/mcp.
The registry describes it as: Read-only Solana and Robinhood Chain tools: wallet recovery, token safety, unlocks, upgrades, fees.
We read its 18 tools on 2026-10-22. 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
check_wallet check_reclaimable_rent check_wrapped_sol check_token_delegates check_failed_deploys check_closable_programs check_lookup_tables check_lp_fees check_dlmm_positions check_subscriptions check_token_tax check_frozen_tokens audit_token check_token_unlocks search_tokens list_upgrades check_approvals get_fee_estimate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-xroot-token-operations)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.