@xgamesfun/solana 0.25.2 → 0.25.3

package/README.md

@@ -106,8 +106,12 @@ codex plugin marketplace add XGamesFun/solana-kit
 codex plugin add xsolana@xgamesfun
 ```
 
+**Chat apps** (claude.ai, ChatGPT, Claude Desktop): add `https://xgames.fun/mcp` as a custom connector (an MCP server
+by URL). It is the hosted server (below, "Over HTTP"): nothing to install, and going live stays your own approval on your
+computer. More at [xgames.fun/solana](https://xgames.fun/solana).
+
 **Any agent with MCP** (Cursor, opencode, Cline…): run the server with
-`npx -y --package=@xgamesfun/solana@0.25.2 xsolana mcp`. Or let `npx -y @xgamesfun/solana@0.25.2 connect` register it, with
+`npx -y --package=@xgamesfun/solana@0.25.3 xsolana mcp`. Or let `npx -y @xgamesfun/solana@0.25.3 connect` register it, with
 the skill, for Claude Code and Codex.
 
 **The skill alone, in any agent that reads skills** (Claude Code, Codex, Copilot, Gemini CLI, Cursor, Windsurf, Cline,
@@ -115,7 +119,7 @@ opencode…): `npx skills add XGamesFun/solana-kit` finds it and installs it for
 server it runs the same tools through `npx`. Each GitHub release also carries `xsolana-economy.zip`, the skill as one
 file for apps that take a skill as an upload (the Claude and ChatGPT desktop apps).
 
-**Over HTTP**: `npx -y --package=@xgamesfun/solana@0.25.2 xsolana mcp --http` serves the tools that read nothing but
+**Over HTTP**: `npx -y --package=@xgamesfun/solana@0.25.3 xsolana mcp --http` serves the tools that read nothing but
 their arguments (guide, examples, check, simulate, cost, explain, review, status, client) at
 `http://127.0.0.1:8787/mcp`, MCP's Streamable HTTP transport. `@xgamesfun/solana/mcp/http` exports the same handler
 (`mcpHttp(request) → response`) for a hosted endpoint: it reads no files, and the agent hands the person the spec and the
@@ -124,7 +128,7 @@ their arguments (guide, examples, check, simulate, cost, explain, review, status
 Then ask for an economy, for example _"a fishing game where each cast costs 0.02 SOL, with a rare golden fish and a
 monthly draw"_.
 
-Going live is always yours: `npx -y @xgamesfun/solana@0.25.2 approve` opens a page on your computer where you connect a
+Going live is always yours: `npx -y @xgamesfun/solana@0.25.3 approve` opens a page on your computer where you connect a
 devnet wallet and approve each transaction. The agent never signs and never asks for a key.
 
 ## Use it from a terminal
@@ -132,13 +136,13 @@ devnet wallet and approve each transaction. The agent never signs and never asks
 Every tool runs from the CLI too, on a spec file (`xsolana.json` by default):
 
 ```bash
-npx -y @xgamesfun/solana@0.25.2 examples shop with loot boxes   # the nearest worked examples
-npx -y @xgamesfun/solana@0.25.2 check xsolana.json                 # refusals and warnings
-npx -y @xgamesfun/solana@0.25.2 simulate xsolana.json              # where the money goes, day by day
-npx -y @xgamesfun/solana@0.25.2 cost xsolana.json                  # what going live and each action cost
-npx -y @xgamesfun/solana@0.25.2 explain xsolana.json               # the economy in plain words
-npx -y @xgamesfun/solana@0.25.2 review xsolana.json                # what a cheater gets on each route (exits 1 on a high finding)
-npx -y @xgamesfun/solana@0.25.2 approve xsolana.json               # go live, approved in your own wallet
+npx -y @xgamesfun/solana@0.25.3 examples shop with loot boxes   # the nearest worked examples
+npx -y @xgamesfun/solana@0.25.3 check xsolana.json                 # refusals and warnings
+npx -y @xgamesfun/solana@0.25.3 simulate xsolana.json              # where the money goes, day by day
+npx -y @xgamesfun/solana@0.25.3 cost xsolana.json                  # what going live and each action cost
+npx -y @xgamesfun/solana@0.25.3 explain xsolana.json               # the economy in plain words
+npx -y @xgamesfun/solana@0.25.3 review xsolana.json                # what a cheater gets on each route (exits 1 on a high finding)
+npx -y @xgamesfun/solana@0.25.3 approve xsolana.json               # go live, approved in your own wallet
 ```
 
 `xsolana help` lists every command. Every command names the exact version, so `npx` runs that release and never whatever
@@ -190,7 +194,7 @@ tiers, boosts and fixed or shared reward rates. The project needs no authority o
 ones), raffles with a Merkle allowlist, and auctions that refund the outbid at once are all routes in the same spec.
 
 **Is there an MCP server or Claude Code plugin for building on Solana?** Yes: the `xsolana` plugin for Claude Code and
-Codex, and `npx -y --package=@xgamesfun/solana@0.25.2 xsolana mcp` for any MCP client. It is listed in the MCP
+Codex, the hosted server at `https://xgames.fun/mcp` for chat apps, and `npx -y --package=@xgamesfun/solana@0.25.3 xsolana mcp` for any MCP client. It is listed in the MCP
 Registry as `io.github.XGamesFun/solana-kit`.
 
 **How is this different from writing my own Anchor program?** Nothing is written, deployed or upgraded per project:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xgamesfun/solana",
-  "version": "0.25.2",
+  "version": "0.25.3",
   "mcpName": "io.github.XGamesFun/solana-kit",
   "description": "Loot boxes, gacha, shops, lotteries, auctions, NFT staking, crafting and rewards on Solana without writing a smart contract: one shared program, its JS client, a CLI, and an MCP server and skill so Claude Code, Codex or any AI agent can design, check, simulate and launch an economy.",
   "license": "Apache-2.0",
@@ -9,7 +9,7 @@
     "type": "git",
     "url": "git+https://github.com/XGamesFun/solana-kit.git"
   },
-  "homepage": "https://github.com/XGamesFun/solana-kit#readme",
+  "homepage": "https://xgames.fun/solana",
   "bugs": {
     "url": "https://github.com/XGamesFun/solana-kit/issues"
   },

package/skills/xsolana-economy/SKILL.md

@@ -9,8 +9,8 @@ An economy is one JSON spec (`xsolana.json` in the project) on **loot**, a Solan
 writes or deploys a contract: the spec is checked, simulated and priced by the `xsolana_*` tools, and the project's
 owner puts it live by approving in their own wallet. It runs on **devnet** until the program is audited.
 
-The tools are the `xsolana_*` MCP tools. Without MCP, the same from a terminal: `npx -y @xgamesfun/solana@0.25.2 <guide|examples|check|simulate|cost|explain|review|publish|status> [xsolana.json]`,
-or `npx -y @xgamesfun/solana@0.25.2 tool <name> '<json>'` for any tool (always with the exact version).
+The tools are the `xsolana_*` MCP tools. Without MCP, the same from a terminal: `npx -y @xgamesfun/solana@0.25.3 <guide|examples|check|simulate|cost|explain|review|publish|status> [xsolana.json]`,
+or `npx -y @xgamesfun/solana@0.25.3 tool <name> '<json>'` for any tool (always with the exact version).
 
 ## Rules (always)
 
@@ -113,7 +113,7 @@ or `npx -y @xgamesfun/solana@0.25.2 tool <name> '<json>'` for any tool (always w
    level would cost. Run it again after every change that touches a route that pays.
 9. **When they say "put it live"**: `xsolana_publish` lists every step and its cost and gives the command. Tell them to
    run it themselves in the project folder, exactly as `xsolana_publish` gives it (it names the exact version:
-   `npx -y @xgamesfun/solana@0.25.2 approve xsolana.json`; never drop the version). It opens a page on their computer where
+   `npx -y @xgamesfun/solana@0.25.3 approve xsolana.json`; never drop the version). It opens a page on their computer where
    they connect a devnet wallet and approve; what lands is written back into `xsolana.json`. You publish nothing.
 10. **After it is live**: `xsolana_status` shows each part on chain; read it before acting on what the person says
     happened. A later change is the same loop: save, publish, and the approval sends only what changed. What only the