@floatonnear/mcp 0.10.1 → 0.10.3
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.
- package/SKILL.md +144 -14
- package/dist/agent-key.d.ts +50 -0
- package/dist/agent-key.js +68 -2
- package/dist/create.d.ts +10 -0
- package/dist/create.js +23 -1
- package/dist/explain.d.ts +33 -0
- package/dist/explain.js +55 -0
- package/dist/keyring-path.d.ts +36 -0
- package/dist/keyring-path.js +117 -0
- package/dist/payloads.d.ts +10 -8
- package/dist/payloads.js +92 -23
- package/dist/roles.d.ts +29 -0
- package/dist/roles.js +49 -0
- package/dist/server.js +562 -85
- package/dist/token-meta.d.ts +16 -0
- package/dist/token-meta.js +18 -0
- package/package.json +1 -1
package/dist/token-meta.d.ts
CHANGED
|
@@ -39,4 +39,20 @@ export declare function tokenMeta(rpcUrl: string, token: string, view: Fetcher):
|
|
|
39
39
|
* to remain visible.
|
|
40
40
|
*/
|
|
41
41
|
export declare function label(token: string, meta: TokenMeta | null): string;
|
|
42
|
+
/**
|
|
43
|
+
* The symbol ALONE, for a sentence a person reads.
|
|
44
|
+
*
|
|
45
|
+
* `label()` returns `USDC (17208628f84f5d6ad33f…)`, which is right for a JSON
|
|
46
|
+
* field — the id is what a support conversation needs — and wrong inside
|
|
47
|
+
* prose. Dropped into a `say` it produced "1 usdc.testnet a day", and on
|
|
48
|
+
* mainnet it would have been "1 17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1 a day",
|
|
49
|
+
* because Circle-native USDC's account id is 64 hex characters.
|
|
50
|
+
*
|
|
51
|
+
* Falls back to "tokens" rather than the id. An unresolvable symbol is a
|
|
52
|
+
* cosmetic loss; a 64-character hex string in the middle of a sentence tells
|
|
53
|
+
* the reader the product is broken. `vault_pay` already did exactly this —
|
|
54
|
+
* `meta?.symbol ?? "tokens"` — and this just names the pattern so the next
|
|
55
|
+
* caller does not have to rediscover it.
|
|
56
|
+
*/
|
|
57
|
+
export declare function displaySymbol(meta: TokenMeta | null): string;
|
|
42
58
|
export {};
|
package/dist/token-meta.js
CHANGED
|
@@ -44,3 +44,21 @@ export async function tokenMeta(rpcUrl, token, view) {
|
|
|
44
44
|
export function label(token, meta) {
|
|
45
45
|
return meta ? `${meta.symbol} (${token})` : token;
|
|
46
46
|
}
|
|
47
|
+
/**
|
|
48
|
+
* The symbol ALONE, for a sentence a person reads.
|
|
49
|
+
*
|
|
50
|
+
* `label()` returns `USDC (17208628f84f5d6ad33f…)`, which is right for a JSON
|
|
51
|
+
* field — the id is what a support conversation needs — and wrong inside
|
|
52
|
+
* prose. Dropped into a `say` it produced "1 usdc.testnet a day", and on
|
|
53
|
+
* mainnet it would have been "1 17208628f84f5d6ad33f0da3bbbeb27ffcb398eac501a31bd6ad2011e36133a1 a day",
|
|
54
|
+
* because Circle-native USDC's account id is 64 hex characters.
|
|
55
|
+
*
|
|
56
|
+
* Falls back to "tokens" rather than the id. An unresolvable symbol is a
|
|
57
|
+
* cosmetic loss; a 64-character hex string in the middle of a sentence tells
|
|
58
|
+
* the reader the product is broken. `vault_pay` already did exactly this —
|
|
59
|
+
* `meta?.symbol ?? "tokens"` — and this just names the pattern so the next
|
|
60
|
+
* caller does not have to rediscover it.
|
|
61
|
+
*/
|
|
62
|
+
export function displaySymbol(meta) {
|
|
63
|
+
return meta?.symbol ?? "tokens";
|
|
64
|
+
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@floatonnear/mcp",
|
|
3
|
-
"version": "0.10.
|
|
3
|
+
"version": "0.10.3",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "MCP server for the hierarchical budget vault. The agent key signs request_payment only; owner methods emit unsigned payloads for wallet approval.",
|
|
6
6
|
"license": "MIT",
|