@floatonnear/mcp 0.2.0 → 0.3.0

package/dist/payloads.d.ts

@@ -109,8 +109,33 @@ export declare function toCliCommand(p: OwnerPayload, network?: string): string;
  * A threshold is a gate INSIDE the caps: it can only make the vault more
  * conservative, never less, so there is no value of it that moves more money
  * than the budget tree already allowed. `null` removes it.
+ *
+ * ---- `amount` IS HUMAN UNITS, and it used to be base units.
+ *
+ * Breaking change, 2026-10-31, made the same day the tool was published and
+ * before anyone used it. The parameter was `amountBase` and took raw base
+ * units, which made it the ONLY tool in this module on that convention:
+ *
+ *   vault_pay.amount                   human   "12.50"
+ *   planSetNodeCaps dailyCap/perTxCap  human   (the zod schema says so)
+ *   planSetApprovalThreshold           BASE    <- the odd one out
+ *
+ * And it is the one that configures a safety gate, so it FAILED OPEN. An owner
+ * thinking in human units who passed a figure at or above the per-tx cap in
+ * base units got a threshold ABOVE every cap in the tree: the gate never fires,
+ * nothing is ever held, and the transaction succeeds — so the owner believes the
+ * control is on. Measured against the live mainnet vault (per-tx cap 510000
+ * base = 0.51 USDC): "1000000" meaning "a million" yields a 1.0 USDC threshold,
+ * above every cap.
+ *
+ * The other direction fails closed and is merely annoying ("1" meaning 1 USDC
+ * became 0.000001, so everything got held), which is why only one direction is
+ * dangerous and why this is worth a breaking change rather than a doc fix.
+ *
+ * `toBaseUnits` throws rather than truncating excess precision — correct here:
+ * silently rounding 0.1234567 would set a threshold the owner did not choose.
  */
-export declare function planSetApprovalThreshold(vault: string, nodeId: number, amountBase: string | null): OwnerPayload;
+export declare function planSetApprovalThreshold(vault: string, nodeId: number, amount: string | null, decimals: number): OwnerPayload;
 /**
  * Execute a held payment.
  *

package/dist/payloads.js

@@ -296,18 +296,47 @@ export function toCliCommand(p, network = "testnet") {
  * A threshold is a gate INSIDE the caps: it can only make the vault more
  * conservative, never less, so there is no value of it that moves more money
  * than the budget tree already allowed. `null` removes it.
+ *
+ * ---- `amount` IS HUMAN UNITS, and it used to be base units.
+ *
+ * Breaking change, 2026-10-31, made the same day the tool was published and
+ * before anyone used it. The parameter was `amountBase` and took raw base
+ * units, which made it the ONLY tool in this module on that convention:
+ *
+ *   vault_pay.amount                   human   "12.50"
+ *   planSetNodeCaps dailyCap/perTxCap  human   (the zod schema says so)
+ *   planSetApprovalThreshold           BASE    <- the odd one out
+ *
+ * And it is the one that configures a safety gate, so it FAILED OPEN. An owner
+ * thinking in human units who passed a figure at or above the per-tx cap in
+ * base units got a threshold ABOVE every cap in the tree: the gate never fires,
+ * nothing is ever held, and the transaction succeeds — so the owner believes the
+ * control is on. Measured against the live mainnet vault (per-tx cap 510000
+ * base = 0.51 USDC): "1000000" meaning "a million" yields a 1.0 USDC threshold,
+ * above every cap.
+ *
+ * The other direction fails closed and is merely annoying ("1" meaning 1 USDC
+ * became 0.000001, so everything got held), which is why only one direction is
+ * dangerous and why this is worth a breaking change rather than a doc fix.
+ *
+ * `toBaseUnits` throws rather than truncating excess precision — correct here:
+ * silently rounding 0.1234567 would set a threshold the owner did not choose.
  */
-export function planSetApprovalThreshold(vault, nodeId, amountBase) {
+export function planSetApprovalThreshold(vault, nodeId, amount, decimals) {
+    const base = amount === null ? null : toBaseUnits(amount, decimals).toString();
     return {
         receiverId: vault,
         methodName: "set_approval_threshold",
-        args: { node_id: nodeId, amount: amountBase },
+        args: { node_id: nodeId, amount: base },
         gasTgas: DEFAULT_GAS_TGAS,
         depositYocto: ONE_YOCTO,
-        summary: amountBase
-            ? `Payments above ${amountBase} (base units) from node ${nodeId} will need your approval`
+        // Human units in the summary too. The old line read "Payments above
+        // 1000000 (base units)", which is unreadable in precisely the moment the
+        // owner is checking the plan before signing it.
+        summary: amount
+            ? `Payments above ${amount} from node ${nodeId} will need your approval`
             : `Remove the approval threshold on node ${nodeId} — payments up to the caps run unattended`,
-        warnings: amountBase
+        warnings: amount
             ? []
             : ["After this, nothing at this node waits for a human: only the caps apply."],
     };

package/dist/server.js

@@ -87,7 +87,7 @@ const limitShape = z
 // startup: a wrong relative path would break the server outright instead of
 // merely reporting a stale version. server.smoke.test.ts asserts the two agree,
 // so a bump cannot land with only one of them moved.
-const server = new McpServer({ name: "float", version: "0.2.0" });
+const server = new McpServer({ name: "float", version: "0.3.0" });
 // ----------------------------------------------------------------- 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.", {
@@ -211,7 +211,15 @@ server.tool("vault_plan_set_cooldown", "Build an UNSIGNED payload to set the min
 server.tool("vault_pending_approval", "Look up a payment that is HELD awaiting the owner's approval. Returns null if there is no ticket for that id — already approved, already rejected, or never held.", { requestId: z.string().min(1) }, async ({ requestId }) => json((await viewFunction(cfg.rpcUrl, requireVault(), "get_pending_approval", {
     request_id: requestId,
 })) ?? null));
-server.tool("vault_plan_set_approval_threshold", "Build an UNSIGNED payload requiring the owner's approval for payments above an amount at this node. A threshold sits INSIDE the caps and can only make the vault more conservative. Pass amountBase null to remove it. Not signed by this server.", { nodeId: z.number().int().min(0), amountBase: z.string().min(1).nullable() }, async ({ nodeId, amountBase }) => renderPlan(planSetApprovalThreshold(requireVault(), nodeId, amountBase)));
+server.tool("vault_plan_set_approval_threshold", 'Build an UNSIGNED payload requiring the owner\'s approval for payments above an amount at this node. A threshold sits INSIDE the caps and can only make the vault more conservative. `amount` is HUMAN units, the same convention as vault_pay — "0.25" is a quarter of a USDC. Pass amount null to remove the threshold. Not signed by this server.', {
+    nodeId: z.number().int().min(0),
+    // HUMAN units, matching vault_pay and vault_plan_set_caps. This took BASE
+    // units until 2026-10-31 and was the only tool here that did — on the one
+    // control that configures a safety gate, where the mistake fails OPEN. See
+    // planSetApprovalThreshold in payloads.ts for the measurement.
+    amount: z.string().min(1).nullable().describe('human units, e.g. "0.25" — NOT base units'),
+    decimals: z.number().int().min(0).max(38).default(6),
+}, async ({ nodeId, amount, decimals }) => renderPlan(planSetApprovalThreshold(requireVault(), nodeId, amount, decimals)));
 server.tool("vault_plan_approve_payment", "Build an UNSIGNED payload to APPROVE a held payment, which sends it. Every limit is re-checked at approval, so it can still be refused. Not signed by this server.", { requestId: z.string().min(1) }, async ({ requestId }) => renderPlan(planApprovePayment(requireVault(), requestId)));
 server.tool("vault_plan_reject_payment", "Build an UNSIGNED payload to REJECT a held payment. Nothing moves and the ticket is discarded. Not signed by this server.", { requestId: z.string().min(1) }, async ({ requestId }) => renderPlan(planRejectPayment(requireVault(), requestId)));
 server.tool("vault_plan_pause", "Build an UNSIGNED payload to pause or resume the whole vault. Pausing halts every agent payment. Not signed by this server.", { paused: z.boolean() }, async ({ paused }) => renderPlan(planSetPaused(requireVault(), paused)));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@floatonnear/mcp",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "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",