Skip to content

xsolana MCP server

io.github.XGamesFun/solana-kitXGamesFunstreamable-httpv0.29.2Scanned

Design, check, simulate and review game economies for Solana: a JSON spec, no contract to write.

11 tools: 7 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 7 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the xsolana MCP server can do

The xsolana MCP server is published by the GitHub account XGamesFun. It has 11 tools. It can create or change data (7 tools: xsolana_check, xsolana_simulate, xsolana_cost, xsolana_review and 3 more), but cannot delete data. 4 tools only read.

2 tools bring in text other people can write (xsolana_status and xsolana_token).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.29.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Changes things 7Claude Code: ask
  • xsolana_checkCheck an economy spec: refusals (each with a code, what it means and its fix) stop it from going live; warnings are what the person must hear (chance that pays money, revenue paid …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check an economy spec: refusals (each with a code, what it means and its fix) stop it from going live; warnings are what the person must hear (chance that pays money, revenue paid to stakers, an unfunded prize, a grant without limits, a mint’s powers, a time far off with its date in words, a token a player can hold a payment up in, a box longer than one answer of the oracle’s holds). The program refuses only what it must: much of what a project sets up is taken and warned of, never refused, so each warning goes to the person. Run it after every change, and check before you describe: before telling the person how value moves (a burn, a free token, a swap, a refund, a payment held or not), check one draft with that mechanism once and read what it says (one draft, not every variant). Quote every count of approvals from it. Give the spec inline (`spec`), a file, or an example.

    Annotations the server declares

    • title: Check an economy spec
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_clientHow an app (a game, a site, a bot) uses a live economy: the program’s address and cluster, the npm package and IDL, and the calls a page makes with the player’s own wallet (open a …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How an app (a game, a site, a bot) uses a live economy: the program’s address and cluster, the npm package and IDL, and the calls a page makes with the player’s own wallet (open a box, buy, stake, craft, enter, claim). Use this instead of writing chain code from memory.

    Annotations the server declares

    • title: The program and its calls, for an app
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_costWhat going live costs (each account’s rent, the program’s fees, network fees, the seeds, the transactions it takes) and what each action costs whoever signs it while it runs.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What going live costs (each account’s rent, the program’s fees, network fees, the seeds, the transactions it takes) and what each action costs whoever signs it while it runs.

    Annotations the server declares

    • title: Price going live and each action
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_designFrom what the person wants to the specs that do it, when no single part does it all or their wants pull against each other.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    From what the person wants to the specs that do it, when no single part does it all or their wants pull against each other. Write each want as a requirement naming its route (the key of the lottery, item, grant, farm or contest it is about; its family follows from that): a draw ("pay-in" {currencies: [{token, amount}]}, "burn", "refund-as-paid", "free-entry" {grant, perPerson, spendable}, "one-approval", "one-draw", "one-token", "first-reward-no-sol"); a sale of an item ("pay-in", "fixed-price", "instant", "fair-scarce" {perPerson, list}, "one-approval"); a reward, a grant ("per-person" {claims}, "no-server", "bot-proof", "bounded" {total}, "first-reward-no-sol"; a server's voucher keys as "serverKeys" on any of them); staking, a farm ("emission-cap" {total}, "predictable", "no-lock", "whale-fair"; "perDay" and "days" on any of them); a contest ("no-owner-trust", "equal-stakes" {amount}, "refund-if-no-result"; decider keys as "serverKeys"). Pass the spec as it stands, with each route's skeleton. For each route it builds every combination of known bridges (an entry token each currency buys, crafted in the purchase; a payment held to the draw; a fixed-price listing in each currency; an allowlist; a deciding voucher server; a fixed or shared rate, minted or from a vault, with an end or a halving; a decider key), checks each, tests every requirement on it, and answers the designs best first (what the person asked for, then how it plays, then how clean, then how secure), with what each keeps (✓), keeps in part (~) and gives up (✗), a "Say" sentence for the person and what each needs from them; when none keeps them all, what has to give. Read the requirements back to the person, put the choice to them with your pick, then build the one they choose (its spec is in `designs`) and run xsolana_check on it. A spec saved before they choose is already built, a draft too: save none until they have.

    Annotations the server declares

    • title: From what a person wants to the specs that do it
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_reviewReview an economy the way a cheater reads it, before it goes live (not a validity check: xsolana_check is that).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Review an economy the way a cheater reads it, before it goes live (not a validity check: xsolana_check is that). For every route that pays or gives value it says who can trigger it, what the program enforces, what it trusts off the chain, and the most one cheater gets; then findings with stable ids and a severity; then the trade-off to show the person: for each grant paid on vouchers, whether its server decides, replays or only bounds the result (its "trust"), what a cheater gets at that level, and what the next level costs to build. Fix every high finding, declare "trust" honestly on every voucher grant, and tell the person in plain words which level each signed route uses and what a cheater gets, so they choose the trade-off. Give the spec inline (`spec`), a file, or an example. Answers { ok (false when a finding is high, or the spec does not check: then `refusals`), routes: [{ kind ("grant", "farm", "item", "box", "payment", "recipe", "lottery", "contest", "auction", "schedule", "hold", "decision"), key, name, trigger, enforced: [words], trusts: [words], trust ("decides" | "replays" | "bounds" | null), ceiling (words), feeds: ["farm:<key>", …: what its prize is staked in, crafted into or buys] }], findings: [{ id (R-…), severity ("high" | "medium" | "low" | "info"), route ("grant:<key>", "farm:<key>", … or "economy"), message, fix }] }; the trade-offs are in its text.

    Annotations the server declares

    • title: Review an economy as a cheater would
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_simulateThe quick simulation (expected values from the spec, instant): what each box, ticket and craft gives back against its price, what the game keeps, each pool’s money in and out per d…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The quick simulation (expected values from the spec, instant): what each box, ticket and craft gives back against its price, what the game keeps, each pool’s money in and out per day and whether it runs dry, settles or grows, farm rewards per unit staked, what players, the treasury and the platform get each day; a box’s chances with its odds rules at their most, what a box that gives nothing for a miss misses as its outcomes run out, what a ticket weighs in a lottery weighed by time, and what places get from a pool that starts short. `scenario` overrides the spec’s own ({"perDay": {"box:flip": 1000}, "days": 30, "staked": {"<farm>": 1000}}). Quote its numbers; never your own arithmetic.

    Annotations the server declares

    • title: Simulate where the money goes
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_tokenA token made elsewhere, as the chain has it, for an economy that uses it: give its mint’s address and get its ready `tokens` entry (`source: "existing"`) with its name, ticker, dec…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    A token made elsewhere, as the chain has it, for an economy that uses it: give its mint’s address and get its ready `tokens` entry (`source: "existing"`) with its name, ticker, decimals and token program, and `powers` filled in: what the mint’s own keys can do (mint more, freeze, a transfer fee, a transfer hook, a permanent delegate, a pause…), in words too. Use it instead of asking the person to look the mint up. Reads devnet (or XSOLANA_RPC_URL): the mint and its name record only, never the link the record names.

    Annotations the server declares

    • title: Read a token made elsewhere
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • xsolana_examplesFind an economy to start from.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find an economy to start from. With `query` (the person’s own words, as they said them), returns the closest worked examples (whole specs that check and go live in the tests), the closest of 112 real or trending economies rated against loot (great / some / a-lot / cannot, with what carries it or what is missing), and what loot can’t do exactly in the ask, each with the nearest versions it can. Call it again with the words of any part that looks impossible: the answer is a nearest version to offer, not a dead end. With `name`, returns that example’s whole spec to copy and change. With neither, lists every example.

    Annotations the server declares

    • title: Find a worked economy to start from
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_explainThe economy in plain words for the person: what players do and what it costs and is worth, how the pools fill and drain, what runs by itself, what the authority must sign, what goi…No findings

    Why it is in this group

    • The name "xsolana_explain" says "explain": a word for reading.
    Description, as the server wrote it
    The economy in plain words for the person: what players do and what it costs and is worth, how the pools fill and drain, what runs by itself, what the authority must sign, what going live costs, and what is flagged for the law. Tell them the essentials in a few lines, from this text.

    Annotations the server declares

    • title: Explain an economy in plain words
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_guideRead this first whenever someone wants a web3 economy, game economy, token economy, NFT mechanic or onchain reward system: a shop, loot boxes or packs, gacha, a lottery or raffle, …No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read this first whenever someone wants a web3 economy, game economy, token economy, NFT mechanic or onchain reward system: a shop, loot boxes or packs, gacha, a lottery or raffle, an auction (highest bid wins, the outbid refunded at once), staking or a farm, crafting or merging, seasons and emissions, a contest players back a side in, quests and airdrops, holder-gated drops, using NFTs of any other collection in a game. loot is ONE shared Solana program (on devnet, and on mainnet when the spec says "network": "mainnet"; not independently audited): the economy is a JSON spec, not a new smart contract, so never write Anchor/Rust for what it covers. With no `part`, returns a short index: the loop, and every part and topic with when to fetch it. Then fetch the one you need: `part` gives that part’s fields from the schema, who acts at play time and its nested shapes; a topic (writing, cheating, asks, cannot) gives how to write a spec, designing against bots, asks that look impossible, or what loot cannot do with the nearest versions.

    Annotations the server declares

    • title: What an economy can be made of
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • xsolana_statusA live economy as it is on chain: the project, every pool’s balance, every record the spec names (found or missing).Reads text others writeNo findings

    Why it is in this group

    • The name "xsolana_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    A live economy as it is on chain: the project, every pool’s balance, every record the spec names (found or missing). Reads the economy’s own cluster: devnet through its public RPC (or XSOLANA_RPC_URL), mainnet through XSOLANA_RPC_URL, which must then name a mainnet RPC.

    Annotations the server declares

    • title: Read a live economy from the chain
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://xgames.fun/mcp: tools/list returned 10 tools to an anonymous client, including xsolana_check (write), xsolana_simulate (write), xsolana_cost (write), xsolana_review (write), xsolana_token (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 17, 2026
    • Tools that change things, listed without credentials: 5 to 6

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools11 changed.~11 changedView diff
  2. Tools1 added, 3 changed.+1 added~3 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
    • Tools that change things, listed without credentials: 5 to 6
  4. Tools1 changed.~1 changedView diff
  5. Tools1 changed.~1 changedView diff
  6. Tools1 added.+1 addedView diff
  7. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.29.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http solana-kit https://xgames.fun/mcp
claude mcp add --transport http solana-kit https://xgames.fun/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__solana-kit__xsolana_guide",
      "mcp__solana-kit__xsolana_examples",
      "mcp__solana-kit__xsolana_explain",
      "mcp__solana-kit__xsolana_status"
    ],
    "ask": [
      "mcp__solana-kit__xsolana_check",
      "mcp__solana-kit__xsolana_simulate",
      "mcp__solana-kit__xsolana_cost",
      "mcp__solana-kit__xsolana_review",
      "mcp__solana-kit__xsolana_design",
      "mcp__solana-kit__xsolana_token",
      "mcp__solana-kit__xsolana_client"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as solana-kit. Review it before you use it.

Capability tags behind 2 rules
  • mcp__solana-kit__xsolana_status untrusted-input
  • mcp__solana-kit__xsolana_token untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.XGamesFun/solana-kit/verify?hash=eecfecccee3a826e7574c8da465251eb3625bccf0df87e14177b1634c67df334" | jq -e '.changed == false'

Pinned hash eecfecccee3a, from Nov 21, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.XGamesFun/solana-kit/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.XGamesFun/solana-kit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.XGamesFun/solana-kit.svg)](https://radar.anlyon.com/servers/io.github.XGamesFun/solana-kit)

Source: MCP Registry · repository. Synced Nov 21, 2026, 18:17 UTC.

xsolana MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the xsolana MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the xsolana MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the xsolana MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the xsolana MCP server have?

11 tools: 7 write, 4 read. xsolana_check, xsolana_simulate, xsolana_cost, xsolana_review, xsolana_design, xsolana_token, xsolana_client, xsolana_guide and 3 more.

Does the xsolana MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the xsolana MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the xsolana MCP server changed its tools?

Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.