# xsolana (npm · @xgamesfun/solana)

Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@xgamesfun/solana`
- Version: `0.20.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to XGamesFun/solana-kit).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1789 tokens (~178/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "xsolana_publish" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 11 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

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

xsolana runs locally as an npm package, launched with npx -y @xgamesfun/solana. 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 xgamesfun-solana-kit -- npx -y @xgamesfun/solana
```

### Cursor

```json
{
  "mcpServers": {
    "xgamesfun-solana-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@xgamesfun/solana"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xgamesfun-solana-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@xgamesfun/solana"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add xgamesfun-solana-kit -- npx -y @xgamesfun/solana
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xgamesfun-solana-kit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@xgamesfun/solana"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xgamesfun-solana-kit --command npx --arg -y --arg @xgamesfun/solana
```

### Hermes

```yaml
mcp_servers:
  xgamesfun-solana-kit:
    command: "npx"
    args: ["-y", "@xgamesfun/solana"]
```

### Netclaw

```json
{
  "McpServers": {
    "xgamesfun-solana-kit": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@xgamesfun/solana"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add xgamesfun-solana-kit -t stdio -c npx -a -y @xgamesfun/solana
```

### Other

```json
{
  "mcpServers": {
    "xgamesfun-solana-kit": {
      "command": "npx",
      "args": [
        "-y",
        "@xgamesfun/solana"
      ]
    }
  }
}
```

## 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-10-30 (score 78)

First indexed and scored.

## MCP tools (10)

### `xsolana_guide` (~209 tokens)

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 prediction pool or contest, quests and airdrops, holder-gated drops, using NFTs of any other collection in a game. loot is ONE shared Solana program (devnet until it is audited): the economy is a JSON spec, not a new smart contract, so never write Anchor/Rust for what it covers. Returns every part an economy can have (fields from the schema, who acts at play time, fees), how to write a spec, and what loot cannot do (with the nearest alternative). Pass `part` for one part with its nested shapes.

Input parameters:

- `part` (string): One part, with its nested shapes.

### `xsolana_examples` (~211 tokens)

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.

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` (~174 tokens)

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). Run it after every change. Give the spec inline (`spec`), a file, or an example.

Input parameters:

- `example` (string): A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …).
- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_simulate` (~239 tokens)

The quick simulation (expected values from the spec, instant): what each box, ticket and craft gives back against its price, the house edge, 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. `scenario` overrides the spec’s own ({"perDay": {"box:flip": 1000}, "days": 30, "staked": {"<farm>": 1000}}). Quote its numbers; never your own arithmetic.

Input parameters:

- `example` (string): A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …).
- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `json` (boolean): Also return every row.
- `scenario` (object): What to assume instead of the spec’s scenario.
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_cost` (~134 tokens)

What going live costs (each account’s rent, the program’s fees, network fees, the seeds, the transactions and wallet approvals it takes) and what each action costs whoever signs it while it runs.

Input parameters:

- `example` (string): A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …).
- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_explain` (~158 tokens)

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.

Input parameters:

- `example` (string): A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …).
- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_save` (~108 tokens)

Save a spec into the project (default xsolana.json), only if it checks. A file that is already live keeps its program numbers and its live section. Never put a key in it: the checker refuses one.

Input parameters:

- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `spec` (object, required): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_publish` (~199 tokens)

When the person says to put it live: returns what going live does (every step, in order, and its cost) and the one command they run themselves to approve it in their own wallet (`npx -y @xgamesfun/solana@0.20.1 approve`, pinned to this exact version: give it as it is): it opens a local page where they connect a devnet wallet and approve each transaction. You never sign, never ask for a key, and never run the approval for them.

Input parameters:

- `example` (string): A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …).
- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).
- `spec` (object): An economy spec (version 2) given inline. Takes precedence over file and example.

### `xsolana_status` (~77 tokens)

A live economy as it is on chain: the project, every pool’s balance, every record the spec names (found or missing). Reads devnet (or XSOLANA_RPC_URL).

Input parameters:

- `file` (string): A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists).

### `xsolana_client` (~79 tokens)

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78

## 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 launch Solana game economies on loot, one shared program, no contract. This page covers its npm package (@xgamesfun/solana).

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

xsolana scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 10 tools: xsolana_guide, xsolana_examples, xsolana_check, xsolana_simulate, xsolana_cost, and 5 more. Their descriptions and schemas cost roughly 1,588 tokens of context every time the server is loaded.

### Is the xsolana MCP server still maintained?

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

### What licence is the xsolana MCP server under?

xsolana declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@xgamesfun/solana
- Socket report: https://socket.dev/npm/package/@xgamesfun/solana
- Repository: https://github.com/XGamesFun/solana-kit
- Changelog RSS feed: https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana.xml
- Changelog JSON feed: https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana.json
- HTML version of this page: https://verifymcp.io/servers/xgamesfun-solana-kit/xgamesfun-solana