# xsolana (remote · xgames.fun)

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

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `xgames.fun`: 75/100 (this document), [markdown](https://verifymcp.io/servers/xgamesfun-solana-kit/xgames.md), [page](https://verifymcp.io/servers/xgamesfun-solana-kit/xgames)
- npm · `@xgamesfun/solana`: 61/100, [markdown](https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana.md), [page](https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana)

## Channel facts

- Endpoint: `https://xgames.fun/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.29.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 53/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3309 tokens (~300/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the xsolana MCP server?

xsolana is a hosted endpoint at https://xgames.fun/mcp, 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.

### Claude

```bash
claude mcp add --transport http xgamesfun-solana-kit 'https://xgames.fun/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xgamesfun-solana-kit": {
      "url": "https://xgames.fun/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xgamesfun-solana-kit": {
      "type": "http",
      "url": "https://xgames.fun/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xgamesfun-solana-kit]
url = "https://xgames.fun/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xgamesfun-solana-kit": {
      "type": "remote",
      "url": "https://xgames.fun/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xgamesfun-solana-kit --url 'https://xgames.fun/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xgamesfun-solana-kit:
    url: "https://xgames.fun/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xgamesfun-solana-kit": {
      "Transport": "http",
      "Url": "https://xgames.fun/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xgamesfun-solana-kit -t streamable-http -u 'https://xgames.fun/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xgamesfun-solana-kit": {
      "type": "http",
      "url": "https://xgames.fun/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “xsolana_client” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_cost” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_design” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_examples” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_explain” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_review” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_status” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_token” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_check” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_guide” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_simulate” rewrote its description, which is the text the model reads
- [functional] Server version: 0.29.2 → 0.29.3
- [functional] Server version: 0.29.0 → 0.29.2
- [cosmetic] “xsolana_simulate” reworded the description of “scenario”
- [cosmetic] “xsolana_simulate” reworded the description of “example”
- [cosmetic] “xsolana_check” reworded the description of “example”
- [cosmetic] “xsolana_cost” reworded the description of “example”
- [cosmetic] “xsolana_design” reworded the description of “example”
- [cosmetic] “xsolana_explain” reworded the description of “example”
- [cosmetic] “xsolana_review” reworded the description of “example”
- [cosmetic] Tool “xsolana_status” changed its title: Read a live economy from the chain
- [cosmetic] Tool “xsolana_token” changed its title: Read a token made elsewhere
- [cosmetic] Tool “xsolana_examples” changed its title: Find a worked economy to start from
- [cosmetic] Tool “xsolana_check” changed its title: Check an economy spec
- [cosmetic] Tool “xsolana_client” changed its title: The program and its calls, for an app
- [cosmetic] Tool “xsolana_cost” changed its title: Price going live and each action
- [cosmetic] Tool “xsolana_design” changed its title: From what a person wants to the specs that do it
- [cosmetic] Tool “xsolana_explain” changed its title: Explain an economy in plain words
- [cosmetic] Tool “xsolana_guide” changed its title: What an economy can be made of
- [cosmetic] Tool “xsolana_review” changed its title: Review an economy as a cheater would
- [cosmetic] Tool “xsolana_simulate” changed its title: Simulate where the money goes

### 2026-11-20 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “xsolana_review” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_guide” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_check” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 255 → 309
- [functional] Server version: 0.28.0 → 0.29.0
- [functional] New tool “xsolana_design”
- [cosmetic] “xsolana_guide” reworded the description of “part”

### 2026-11-18 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “xsolana_status” rewrote its description, which is the text the model reads
- [security] Tool “xsolana_cost” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 224 → 255
- [functional regression] Schema quality: 2021 → 2451
- [functional regression] Schema quality: 2021 → 2242
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.27.0 → 0.28.0
- [functional] Server version: 0.26.1 → 0.27.0
- [functional] Server version: 0.26.0 → 0.26.1
- [functional] New tool “xsolana_token”

### 2026-11-10 (score 70)

First indexed and scored.

## MCP tools (11)

### `xsolana_guide` (~237 tokens)

What an economy can be made of

What an economy on loot can be made of: shops, loot boxes and packs, gacha, lotteries and raffles, auctions (the highest bid wins, the outbid refunded at once), staking and farms, crafting and merging, seasons and emissions, contests players back a side in, quests and airdrops, holder-gated drops, and NFTs of other collections used in a game. loot is one shared Solana program (on devnet, and on mainnet when the spec says "network": "mainnet"; not independently audited): an economy is a JSON spec, not a new smart contract. With no `part`, returns a short index of every part and topic. With a part, returns its fields from the schema, who acts at play time and its nested shapes; with a topic (writing, cheating, asks, cannot), how to write a spec, designing against bots, asks that look impossible, or what loot cannot do and the nearest versions it can.

Input parameters:

- `part` (string): One part, with its fields and nested shapes, or one topic (writing, cheating, asks, cannot).

### `xsolana_examples` (~175 tokens)

Find a worked economy to start from

Worked economies to start from. With `query` (a request in its own words), 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 each or what is missing), and what loot can’t do exactly in the request, each with the nearest versions it can. With `name`, returns that example’s whole spec. With neither, lists every example.

Input parameters:

- `fit` (string): Only ideas with this fit.
- `limit` (integer): How many of each kind (default 6).
- `name` (string): An example’s name, to get its whole spec.
- `query` (string): What the person wants, in a few words.

### `xsolana_check` (~207 tokens)

Check an economy spec

Checks an economy spec. Returns its refusals, each with a code, what it means and its fix, which keep a spec from going live; and its warnings, what the person behind the economy needs to know: 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, so much of what a project sets up is accepted with a warning. Also returns how many wallet approvals each action takes. Takes the spec inline (`spec`) or a worked example by name.

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_simulate` (~260 tokens)

Simulate where the money goes

The quick simulation: expected values from the spec, computed at once. Returns 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, and what players, the treasury and the platform get each day, at the fees of the economy’s own network; 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}}).

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `json` (boolean): Also return every row.
- `scenario` (object): What to assume in place of the spec’s scenario.
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_cost` (~113 tokens)

Price going live and each action

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, at the fees of the economy’s own network. It prices only: nothing is sent.

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_explain` (~106 tokens)

Explain an economy in plain words

The economy in plain words: 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.

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_review` (~365 tokens)

Review an economy as a cheater would

Reviews an economy the way a cheater reads it, before it goes live (a review, not a validity check). 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, 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. Takes the spec inline (`spec`) or a worked example by name. 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.

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_design` (~531 tokens)

From what a person wants to the specs that do it

From what a person wants to the specs that do it, when no single part does it all or the wants pull against each other. Each want is 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"). Takes 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 sentence for the person and what each needs from them; when none keeps them all, what has to give. Each design’s spec is in `designs`.

Input parameters:

- `example` (string): A worked example by name (stud-farm, nft-raffle, …).
- `requirements` (array, required): What the person wants, each a requirement the tools can test.
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.
- `top` (integer): How many designs to answer (3 by default).

### `xsolana_status` (~68 tokens)

Read a live economy from the chain

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 network.

Input parameters:

- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_token` (~191 tokens)

Read a token made elsewhere

A token made elsewhere, as the chain has it: given its mint’s address, returns its ready `tokens` entry (`source: "existing"`) with its name, ticker, decimals and token program, and `powers`: 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. Reads devnet: the mint and its name record only, not the link the record names.

Input parameters:

- `key` (string): What the spec will call it (default: its ticker, in the letters a key takes).
- `mint` (string, required): The token’s mint address.
- `project` (string): The loot project’s address, when the token is one the project is to mint on a mint of its own: its mint authority then reads as the project’s, or as not handed over yet.

### `xsolana_client` (~69 tokens)

The program and its calls, for an app

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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xgamesfun-solana-kit/xgames#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70

## Common questions

### What is the xsolana MCP server?

xsolana is an MCP server listed in the public MCP registry as io.github.XGamesFun/solana-kit. Design, check, simulate and review game economies for Solana: a JSON spec, no contract to write. This page covers its hosted endpoint (https://xgames.fun/mcp).

### Is the xsolana MCP server safe to use?

xsolana scores 75 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 xsolana MCP server expose?

xsolana exposes 11 tools: xsolana_guide, xsolana_examples, xsolana_check, xsolana_simulate, xsolana_cost, and 6 more. Their descriptions and schemas cost roughly 2,322 tokens of context every time the server is loaded.

### Does the xsolana MCP server require authentication?

No. We connected to xsolana without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the xsolana MCP server still maintained?

xsolana is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the xsolana MCP server?

VerifyMCP ran 13 checks on xsolana, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://xgames.fun/mcp
- Repository: https://github.com/XGamesFun/solana-kit
- Website: https://xgames.fun/solana
- Changelog RSS feed: https://verifymcp.io/servers/xgamesfun-solana-kit/xgames.xml
- Changelog JSON feed: https://verifymcp.io/servers/xgamesfun-solana-kit/xgames/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/xgamesfun-solana-kit/xgames.json
- HTML version of this page: https://verifymcp.io/servers/xgamesfun-solana-kit/xgames
