Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xsolana

REMOTE · XGAMES.FUN · 2 COMPONENTS

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

+3 this week 75 Trust /100

Last scanned (49 minutes ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security80
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability53
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1
    • 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 security
    • Server version: 0.29.2 → 0.29.3 functional
    • Server version: 0.29.0 → 0.29.2 functional
    • “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 cosmetic
  • 20 Nov 26 0
    • 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 security
    • Schema quality: 255 → 309 ▼ functional
    • Server version: 0.28.0 → 0.29.0 functional
    • New tool “xsolana_design” functional
    • “xsolana_guide” reworded the description of “part” cosmetic
  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 11 Nov 26 0
    • 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 security
    • Schema quality: 224 → 255 ▼ functional
    • Schema quality: 2021 → 2451 ▼ functional
    • Schema quality: 2021 → 2242 ▼ functional
    • 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” functional
  • 10 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://xgames.fun/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xgames.fun CN=YR1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 RSA 2048 SHA256-RSA 50502b854d5e5f2dd7cb36d1ba8b4ad19c7
SANs: xgames.fun
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of xgames.fun. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
fun. DS published 47728 13 Verified
xgames.fun. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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
Header Value
strict-transport-security max-age=63072000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://xgames.fun/mcp Verified 200
http (plaintext) http://xgames.fun/mcp HTTPS enforced 308 https://xgames.fun/mcp
MCP tools · 11 exposed · ~2,322 tokens

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 →

Tool Tokens
xsolana_check ~207

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.

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_client ~69

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

xsolana_cost ~113

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.

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_design ~531

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

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
requirementsarrayyesWhat the person wants, each a requirement the tools can test.
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.
topinteger–How many designs to answer (3 by default).

No output schema declared.

No examples provided.

xsolana_examples ~175

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.

NameTypeReqDescription
fitstring–Only ideas with this fit.
limitinteger–How many of each kind (default 6).
namestring–An example’s name, to get its whole spec.
querystring–What the person wants, in a few words.

No output schema declared.

No examples provided.

xsolana_explain ~106

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.

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_guide ~237

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.

NameTypeReqDescription
partstring–One part, with its fields and nested shapes, or one topic (writing, cheating, asks, cannot).

No output schema declared.

No examples provided.

xsolana_review ~365

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.

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_simulate ~260

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

NameTypeReqDescription
examplestring–A worked example by name (stud-farm, nft-raffle, …).
jsonboolean–Also return every row.
scenarioobject–What to assume in place of the spec’s scenario.
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_status ~68

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.

NameTypeReqDescription
specobject–An economy spec (version 2) given inline. Takes precedence over file and example.

No output schema declared.

No examples provided.

xsolana_token ~191

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.

NameTypeReqDescription
keystring–What the spec will call it (default: its ticker, in the letters a key takes).
mintstringyesThe token’s mint address.
projectstring–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.

No output schema declared.

No examples provided.

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.

remote · xgames.fun

# add to Claude Code
claude mcp add --transport http xgamesfun-solana-kit 'https://xgames.fun/mcp'
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.