dev.xroot/token-operations
REMOTE · API.XROOT.DEV · 2 COMPONENTS · SCANNED OCT 15
Read-only Solana and Robinhood Chain tools: wallet recovery, token safety, unlocks, upgrades, fees.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1868 tokens (~103/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the dev.xroot/token-operations MCP server?
dev.xroot/token-operations is a hosted endpoint at https://api.xroot.dev/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.xroot.dev
claude mcp add --transport http dev-xroot-token-operations 'https://api.xroot.dev/mcp/sse'
{
"mcpServers": {
"dev-xroot-token-operations": {
"url": "https://api.xroot.dev/mcp/sse"
}
}
} {
"servers": {
"dev-xroot-token-operations": {
"type": "http",
"url": "https://api.xroot.dev/mcp/sse"
}
}
} [mcp_servers.dev-xroot-token-operations] url = "https://api.xroot.dev/mcp/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-xroot-token-operations": {
"type": "remote",
"url": "https://api.xroot.dev/mcp/sse",
"enabled": true
}
}
} openclaw mcp add dev-xroot-token-operations --url 'https://api.xroot.dev/mcp/sse' --transport streamable-http
mcp_servers:
dev-xroot-token-operations:
url: "https://api.xroot.dev/mcp/sse" {
"McpServers": {
"dev-xroot-token-operations": {
"Transport": "http",
"Url": "https://api.xroot.dev/mcp/sse"
}
}
} assistant mcp add dev-xroot-token-operations -t streamable-http -u 'https://api.xroot.dev/mcp/sse'
{
"mcpServers": {
"dev-xroot-token-operations": {
"type": "http",
"url": "https://api.xroot.dev/mcp/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 77. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 50 to 60. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 15 Oct 2026 · Probed https://api.xroot.dev/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=xroot.dev | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9927a13f2cddcf690e65e83cadeeec3c |
| SANs: xroot.dev, *.xroot.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.xroot.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| xroot.dev. | present | 2371 | 13 | Verified |
| api.xroot.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://api.xroot.dev/mcp/sse | Verified | 200 | |
| http (plaintext) | http://api.xroot.dev/mcp/sse | HTTPS enforced | 301 | https://api.xroot.dev/mcp/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_token Audit token ~137
Run the free risk report on a token: who can still mint or freeze, transfer taxes and hooks, permanent delegates, liquidity status, holder concentration, and a verdict with a score. On Solana pass the mint address; on an EVM chain pass the token contract address. Use it when a user asks whether a token is safe, a rug, or a honeypot. Reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token's mint address (Solana, base58) or contract address (an EVM chain, 0x). |
| chain | string | – | Which chain the token lives on. Defaults to solana. |
No output schema declared.
No examples provided.
check_approvals Check approvals ~113
List the standing token approvals on an EVM wallet — contracts still allowed to move its tokens — ranked by risk, with unlimited allowances, expired permits and flagged spenders called out. A risk read, not money: revoking returns nothing. Nothing is revoked.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address (0x). Public data only; no connection or signature is involved. |
| chain | string | – | The EVM chain the wallet is on. May be omitted while approvals are checked on one chain only. |
No output schema declared.
No examples provided.
check_closable_programs Check closable programs ~78
Read the upgradeable programs a Solana wallet holds the upgrade authority for, and the gross rent their bytecode accounts hold. Closing a program is permanent, so this reads only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_dlmm_positions Check Meteora positions ~88
Read a Solana wallet's Meteora DLMM and DAMM v2 positions by status, how many can be closed now, and the gross SOL deposit those closable positions hold — what closing them returns before fees. Nothing is closed.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_failed_deploys Check failed deploys ~75
Read the program buffer accounts left behind by a Solana wallet's failed or interrupted program deploys, and the SOL recovering them returns net of fees. Nothing is recovered.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_frozen_tokens Check frozen tokens ~75
Read the permissioned (Token ACL) tokens a Solana wallet holds, and which of them the holder can unlock itself under the token's published rules. Nothing is unlocked.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_lookup_tables Check lookup tables ~79
Read the address lookup tables a Solana wallet owns: how many are ready to close, cooling down, or still active, and the gross rent each group holds. Nothing is deactivated or closed.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_lp_fees Check LP fees ~102
Count a Solana wallet's liquidity positions with trading fees waiting to be claimed, per venue: Orca Whirlpools, Meteora, and locked Raydium liquidity. Fees are owed in many different tokens, so the answer is a count of positions, never a summed figure. Nothing is claimed.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_reclaimable_rent Check reclaimable rent ~91
Read how much SOL a Solana wallet can reclaim from rent: the deposits parked in its empty token accounts, and the surplus the rent cut left in accounts it still uses. Returns counts and net figures in SOL. Nothing is closed or moved.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_subscriptions Check subscriptions ~83
Read the on-chain subscriptions and recurring allowances a Solana wallet has granted, by state, plus the rent their accounts would return to this wallet (a sponsored subscription's rent goes back to its sponsor). Nothing is cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_token_delegates Check token delegates ~79
List the standing token delegates and approvals on a Solana wallet — programs still allowed to move its tokens. A risk read, not money: revoking returns no SOL. Nothing is revoked.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_token_tax Check token tax ~72
List the transfer-tax tokens a Solana wallet launched through the platform, with each tax rate — the tokens whose withheld tax that wallet can collect. Nothing is collected.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
check_token_unlocks Check token unlocks ~83
Read a Solana token's on-chain locks: supply vesting and locked liquidity, per locker, with the cliff, start, period and released amounts each lock reports. Use it when a user asks when a token unlocks or whether its liquidity is locked. Reads public lock accounts only.
| Name | Type | Req | Description |
|---|---|---|---|
| mint | string | yes | The token's mint address (base58). |
No output schema declared.
No examples provided.
check_wallet Check wallet ~221
Read everything a wallet can get back, in one call: on Solana, the rent in empty token accounts, the surplus the rent cut left, wrapped SOL, failed-deploy buffers, closable programs, lookup tables, dead Meteora positions, subscriptions, LP fees waiting on Orca, Meteora and locked Raydium positions, standing token delegates (a risk, not money), transfer-tax tokens it launched, and permissioned tokens it can unlock; on an EVM chain, LP fees, creator fees, bridge withdrawals and the wrapped native coin. Every venue is read independently and reports ok, failed or unavailable, and whether it answered in full, so a failed read is never mistaken for nothing there. Use it for "what can this wallet recover"; use the per-venue tools for one venue in detail.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address: a base58 public key on Solana, a 0x address on an EVM chain. |
| chain | string | – | Which chain the address lives on. Defaults to solana. |
No output schema declared.
No examples provided.
check_wrapped_sol Check wrapped SOL ~77
Read the wrapped SOL (wSOL) sitting in a Solana wallet's token accounts, and what unwrapping it back to SOL returns net of fees. Nothing is unwrapped.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Solana wallet address to read (base58 public key). Public data only; no connection or signature is involved. |
No output schema declared.
No examples provided.
get_fee_estimate Get fee estimate ~113
Quote the exact cost of a token operation before anything is built: the platform fee for that service on that chain plus the estimated network fee (rent, base and priority), as decimal strings in the chain's currency. Use it when a user asks what a token deploy, authority revoke, airdrop or metadata update would cost. Reads only; nothing is prepared or sent.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | The operation intent — same shape the browser flow sends (chain, then service, then the service's fields). |
No output schema declared.
No examples provided.
list_upgrades List upgrades ~103
List Solana's protocol upgrades (feature gates) with their state on mainnet, testnet and devnet — pending with an activation estimate, active with its activation epoch, or not yet queued — as read from the chain. Use it when a user asks whether a SIMD or feature has activated, or what is coming next. Optionally filter by mainnet state.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Keep only gates in this mainnet state. Omit for all. |
No output schema declared.
No examples provided.
search_tokens Search tokens ~116
Find a token by name, symbol or address in the xroot.dev token directory — the trending and newest tokens the platform has indexed on an EVM chain — with each token's pool, price and cached audit verdict where one exists. Use it to resolve which of several same-named tokens a user means before auditing it.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | The chain whose directory to search. May be omitted while one chain's directory is indexed. |
| query | string | – | Name, symbol or address fragment. Empty returns the trending list. |
No output schema declared.
No examples provided.
What is the dev.xroot/token-operations MCP server?
dev.xroot/token-operations is an MCP server listed in the public MCP registry as dev.xroot/token-operations. Read-only Solana and Robinhood Chain tools: wallet recovery, token safety, unlocks, upgrades, fees. This page covers its hosted endpoint (https://api.xroot.dev/mcp/sse).
Is the dev.xroot/token-operations MCP server safe to use?
dev.xroot/token-operations scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.xroot/token-operations MCP server expose?
dev.xroot/token-operations exposes 18 tools: check_wallet, check_reclaimable_rent, check_wrapped_sol, check_token_delegates, check_failed_deploys, and 13 more. Their descriptions and schemas cost roughly 1,785 tokens of context every time the server is loaded.
Does the dev.xroot/token-operations MCP server require authentication?
No. We connected to dev.xroot/token-operations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.xroot/token-operations MCP server still maintained?
dev.xroot/token-operations is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.