MCP server for interacting with the Scryfall MTG API
xsolana is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user xsolana-mcp '--' npx -y @xgamesfun/solana mcp
# 2 — ask your agent for something these tools do
# xsolana_guide, xsolana_examples, xsolana_check and 7 more
xsolana costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts xsolana as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user xsolana-mcp '--' npx -y @xgamesfun/solana mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | string | no | One part, with its nested shapes. |
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 … real or trending economies rated against loot (great / some / a-lot / cannot, with what carries it or…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What the person wants, in a few words. |
| name | string | no | An example’s name, to get its whole spec. |
| fit | string | no | Only ideas with this fit. |
| limit | integer | no | How many of each kind (default 6). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| spec | object | no | An economy spec (version 2) given inline. Takes precedence over file and example. |
| file | string | no | A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists). |
| example | string | no | A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …). |
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…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scenario | object | no | What to assume instead of the spec’s scenario. |
| json | boolean | no | Also return every row. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| spec | object | no | An economy spec (version 2) given inline. Takes precedence over file and example. |
| file | string | no | A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists). |
| example | string | no | A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| spec | object | no | An economy spec (version 2) given inline. Takes precedence over file and example. |
| file | string | no | A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists). |
| example | string | no | A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| spec | yes | — | |
| file | no | — |
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 (…, pinned to this exact version: give it as it is): it opens a local page where they connect a devnet wallet and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| spec | object | no | An economy spec (version 2) given inline. Takes precedence over file and example. |
| file | string | no | A JSON file holding the spec, relative to the project folder (default: xsolana.json when it exists). |
| example | string | no | A worked example by name, from xsolana_examples (coin-flip-arena, stud-farm, …). |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file | no | — |
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.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install xsolana or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.20.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish xsolana can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.