@floatonnear/mcp 0.1.0 → 0.1.1

package/dist/server.js

@@ -77,7 +77,17 @@ const limitShape = z
     decimals: z.number().int().min(0).max(38).default(6),
 }))
     .min(1);
-const server = new McpServer({ name: "near-vault", version: "0.1.0" });
+// The name a client displays in its server list, so this string -- not the
+// package name, not the config key -- is the product's label in the one place
+// the product is visible. It was "near-vault": the repo's directory name,
+// leaking outward as the user-facing identity while the config key create-float
+// writes has always been `float`.
+//
+// The version stays a literal rather than being read from package.json at
+// 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.1.1" });
 // ----------------------------------------------------------------- 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.", {

package/package.json

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