@floatonnear/mcp 0.6.0 → 0.6.1

package/dist/rpc.d.ts

@@ -17,6 +17,34 @@
  * https://docs.near.org/api/rpc/providers
  */
 export declare const DEFAULT_RPC_URL = "https://test.rpc.fastnear.com";
+/**
+ * The RPC to use for a given NETWORK.
+ *
+ * WHY THIS EXISTS. `vault_create` takes a `network` argument, resolved the
+ * right factory for it, and then asked `cfg.rpcUrl` — a single value
+ * defaulting to testnet. So a user asking for a mainnet vault got:
+ *
+ *   account usefloat.near does not exist while viewing
+ *
+ * about an account that demonstrably does exist. The factory was right and
+ * the chain was wrong, which reads as "the factory is broken" rather than
+ * "you asked the wrong network". Shipped in 0.6.0 and found by driving the
+ * published package instead of reading its diff.
+ */
+export declare const RPC_BY_NETWORK: Record<string, string>;
+/**
+ * Pick an RPC for `net`, honouring an operator override ONLY where it applies.
+ *
+ * An explicit NEAR_VAULT_RPC_URL is configured for ONE network — whichever the
+ * operator set NEAR_VAULT_NETWORK to. Applying it to the other network is the
+ * same bug in a new place: it would send a mainnet question to a testnet
+ * endpoint and report the answer as fact. So the override wins only when the
+ * requested network is the one it was configured for.
+ */
+export declare function rpcForNetwork(net: string, opts?: {
+    configuredNetwork?: string;
+    override?: string;
+}): string;
 export declare function encodeArgs(args: unknown): string;
 interface RawViewResponse {
     result?: number[];

package/dist/rpc.js

@@ -18,6 +18,38 @@ import { randomUUID } from "node:crypto";
  * https://docs.near.org/api/rpc/providers
  */
 export const DEFAULT_RPC_URL = "https://test.rpc.fastnear.com";
+/**
+ * The RPC to use for a given NETWORK.
+ *
+ * WHY THIS EXISTS. `vault_create` takes a `network` argument, resolved the
+ * right factory for it, and then asked `cfg.rpcUrl` — a single value
+ * defaulting to testnet. So a user asking for a mainnet vault got:
+ *
+ *   account usefloat.near does not exist while viewing
+ *
+ * about an account that demonstrably does exist. The factory was right and
+ * the chain was wrong, which reads as "the factory is broken" rather than
+ * "you asked the wrong network". Shipped in 0.6.0 and found by driving the
+ * published package instead of reading its diff.
+ */
+export const RPC_BY_NETWORK = {
+    testnet: "https://test.rpc.fastnear.com",
+    mainnet: "https://free.rpc.fastnear.com",
+};
+/**
+ * Pick an RPC for `net`, honouring an operator override ONLY where it applies.
+ *
+ * An explicit NEAR_VAULT_RPC_URL is configured for ONE network — whichever the
+ * operator set NEAR_VAULT_NETWORK to. Applying it to the other network is the
+ * same bug in a new place: it would send a mainnet question to a testnet
+ * endpoint and report the answer as fact. So the override wins only when the
+ * requested network is the one it was configured for.
+ */
+export function rpcForNetwork(net, opts = {}) {
+    if (opts.override && net === opts.configuredNetwork)
+        return opts.override;
+    return RPC_BY_NETWORK[net] ?? DEFAULT_RPC_URL;
+}
 export function encodeArgs(args) {
     // Explicit utf8: a memo is free text, goes on-chain, and a latin-1
     // truncation here would corrupt it silently.

package/dist/server.js

@@ -49,7 +49,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import { z } from "zod";
 import { fromBaseUnits, toBaseUnits } from "./amounts.js";
 import { DEFAULT_GAS_TGAS, planAddNode, planAddRole, planBindVirtualAgent, planUnbindVirtualAgent, planFreezeNode, planPurgeSettled, planSetCooldown, planSetNodeCaps, planSetPaused, planSetRecipients, toCliCommand, planSetApprovalThreshold, planApprovePayment, planRejectPayment, planWithdraw, } from "./payloads.js";
-import { accountExists, DEFAULT_RPC_URL, newRequestId, requireAgentKey, viewAccessKeys, viewAccount, viewFunction, } from "./rpc.js";
+import { accountExists, rpcForNetwork, DEFAULT_RPC_URL, newRequestId, requireAgentKey, viewAccessKeys, viewAccount, viewFunction, } from "./rpc.js";
 import { AGENT_NODE_ID, generateAgentKey } from "./agent-key.js";
 import { resolveKeySource } from "./key-file.js";
 import { dirname } from "node:path";
@@ -233,7 +233,7 @@ WORTH KNOWING
   An implicit account (a 64-character hex id) cannot own a vault at all. Tell the user to use a
   named account rather than retrying.
   Amounts are whole tokens in these tools (1.5 means 1.5 USDC), never base units.`;
-const server = new McpServer({ name: "float", version: "0.6.0" }, { instructions: INSTRUCTIONS });
+const server = new McpServer({ name: "float", version: "0.6.1" }, { instructions: INSTRUCTIONS });
 // ----------------------------------------------------------------- reads
 server.tool("vault_tree", "Read the whole budget tree: every node, its caps, parent, bound agent account, cooldown and freeze state. No key required.", {}, async () => json(await viewFunction(cfg.rpcUrl, requireVault(), "get_tree", {})));
 server.tool("vault_budget", "Read one node's budget for a UTC day: cap, executed, in-flight (pending) and available, in human units. Omit `day` for today. No key required.", {
@@ -352,7 +352,14 @@ server.tool("vault_create", "For a user who has NO vault yet. Works out where th
             `NEAR_VAULT_FACTORY. There is deliberately no built-in mainnet default: ` +
             `guessing it wrong would send a real deposit somewhere unverified.`);
     }
-    const rpc = cfg.rpcUrl;
+    // THE RPC MUST FOLLOW THE NETWORK, not the process's default. 0.6.0
+    // resolved the right factory for `net` and then asked the testnet RPC
+    // about it, so a mainnet request answered "usefloat.near does not exist"
+    // about an account that does.
+    const rpc = rpcForNetwork(net, {
+        configuredNetwork: cfg.network,
+        override: process.env.NEAR_VAULT_RPC_URL,
+    });
     // Only ask the factory to derive an id when there IS an owner. With none,
     // the address is decided by whichever wallet signs, and inventing one here
     // would print a plausible address next to a real deposit figure.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@floatonnear/mcp",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "type": "module",
   "description": "MCP server for the hierarchical budget vault. The agent key signs request_payment only; owner methods emit unsigned payloads for wallet approval.",
   "license": "MIT",