run402-mcp 4.14.0 → 4.14.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +18 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -434,6 +434,23 @@ The active project is sticky: `run402 projects use <id>` server-validates `<id>`
434
434
  npx -y run402-mcp # standalone test
435
435
  ```
436
436
 
437
+ ### Buying only? Load 6 tools instead of 198
438
+
439
+ The full server registers **198 tools (~43,000 tokens)** before you do anything. If your agent only wants to *buy* — generate an image for $0.03 and nothing else — that is a fifth to a third of a context window spent on 192 tools it will never call.
440
+
441
+ ```bash
442
+ RUN402_MCP_PROFILE=buyer npx -y run402-mcp
443
+ ```
444
+
445
+ | profile | tools | approx. tokens |
446
+ |---|---:|---:|
447
+ | *(unset — default)* | 198 | ~43,200 |
448
+ | `buyer` | **6** | **~660** |
449
+
450
+ The six: `generate_image` · `init` · `check_balance` · `allowance_status` · `allowance_export` · `request_faucet` — enough to bootstrap a wallet, fund it, check it, and buy. **Local, so it can actually pay:** an x402 payment needs a signing key, so a wallet-less remote server cannot make one.
451
+
452
+ Default is unchanged when the variable is unset. An unknown profile name **exits 1** with the known-profile list rather than silently serving the full surface or nothing.
453
+
437
454
  ### Remote endpoint (no install)
438
455
 
439
456
  A hosted streamable-HTTP MCP server runs at **`https://mcp.run402.com/mcp`** with free discovery tools only: `run402_quickstart`, `x402_price_check` (decode any URL's x402 challenge, unpaid), and `experiment_scoreboard`. It never handles funds — paid capabilities (image generation, deploys, payments) require the local server below, which holds *your* wallet. Registry entry `com.run402/mcp` lists both (`packages[]` npm + `remotes[]`). The remote itself runs as a run402 function — the platform hosting its own MCP server.
@@ -677,6 +694,7 @@ The full MCP surface: every tool is a thin shim over an SDK call.
677
694
  | `RUN402_CONFIG_DIR` | `~/.config/run402` | Local credential storage base directory (named wallets live under `profiles/<name>/`) |
678
695
  | `RUN402_WALLET` | `default` | Active named wallet (profile). Overridden by `--wallet <name>` and per-directory `.run402.json`; `RUN402_PROFILE` is an alias. See `run402 wallets`. |
679
696
  | `RUN402_ALLOWANCE_PATH` | `{config_dir}/allowance.json` | Custom allowance file path |
697
+ | `RUN402_MCP_PROFILE` | *(unset — all 198 tools)* | `run402-mcp` only. `buyer` registers just the 6 tools a buy-only agent needs (~660 tokens instead of ~43,200). Unknown name exits 1. |
680
698
 
681
699
  Local state lives at:
682
700
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "run402-mcp",
3
- "version": "4.14.0",
3
+ "version": "4.14.1",
4
4
  "mcpName": "com.run402/mcp",
5
5
  "description": "MCP server for Run402 — pay-per-call infrastructure for AI agents over x402 USDC micropayments. Generate an image for $0.03 with no signup, or provision Postgres databases with REST API, auth, storage and row-level security.",
6
6
  "type": "module",