@oobe-protocol-labs/sap-mcp-server 0.9.1 → 0.9.3

package/README.md

@@ -15,7 +15,7 @@ User-facing setup docs live in [`USER_DOCS/`](USER_DOCS/00_START_HERE.md). Opera
 
 | Area | Current behavior |
 | --- | --- |
-| Package version | `0.2.1` |
+| Package version | `0.9.21` |
 | MCP transport | stdio locally, Streamable HTTP remotely |
 | Remote access | Bearerless public mode for hosted agents; API key or JWT for private modes |
 | Config directory | `~/.config/mcp-sap` only |
@@ -60,6 +60,12 @@ Create or select a profile:
 npx sap-mcp-config wizard
 ```
 
+Repair hosted SAP MCP runtime entries without recreating the profile:
+
+```bash
+npx sap-mcp-config repair
+```
+
 After connecting hosted SAP MCP in an agent runtime, start the agent context
 with one short message:
 
@@ -128,7 +134,7 @@ For paid/write hosted tools, add the local non-custodial payment bridge as well:
 ```toml
 [mcp_servers.sap_payments]
 command = "npx"
-args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"]
+args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"]
 startup_timeout_sec = 300
 tool_timeout_sec = 300
 
@@ -146,7 +152,7 @@ Codex supports Streamable HTTP MCP servers with URL-based entries in `config.tom
 ```toml
 [mcp_servers.sap]
 command = "npx"
-args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"]
+args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"]
 
 [mcp_servers.sap.env]
 SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE = "false"

package/USER_DOCS/00_START_HERE.md

@@ -44,16 +44,57 @@ https://mcp.sap.oobeprotocol.ai/docs/#/user/06_DESKTOP_GUI_WIZARD
 
 ### CLI Wizard
 
-Run the wizard:
+Run the wizard for a full hosted setup:
 
 ```bash
 npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard
 ```
 
-1. Accept the default **hosted-api** mode for hosted SAP MCP.
-2. Create or import the dedicated local SAP MCP wallet profile.
+At the first menu, choose **Full hosted SAP MCP setup** for new profiles or
+**Repair hosted runtime + sap_payments bridge only** when the profile already
+exists and only paid/write hosted calls are failing.
+
+Repair without walking through the full wizard:
+
+```bash
+npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair
+```
+
+1. Full setup creates or imports the dedicated local SAP MCP wallet profile.
+2. Repair keeps the active profile and only fixes OOBE `sap`/`sap_payments` runtime entries.
 3. Let the wizard configure hosted `sap` plus local `sap_payments` for supported runtimes.
-4. Use `sap_payments_call_paid_tool` when a hosted tool requires x402 payment.
+4. Use `sap_payments_call_paid_tool` when a hosted SAP MCP tool requires x402 payment.
+5. Use `sap_payments_call_external_x402` when an external HTTP x402 agent endpoint is discovered through SAP registry metadata.
+6. Use `sap_protocol_invariants` before registry writes when treasury, fee, or hosted/local routing is unclear.
+7. Use `sap_payments_register_agent` when hosted `sap_register_agent` returns `hosted_local_signer_required`.
+8. Use `sap_payments_update_agent` when hosted `sap_update_agent` returns `hosted_local_signer_required`; this is the preferred path for public agent image/profile metadata updates.
+9. For registrations, check `success`, `agentRegistered`, `agentPda`, `protocolFee`, and `protocolComplete`. Local registration does not pay a hosted x402 fee. `success: true` means the agent account exists and the source-level protocol fee invariant was verified. If `success: false` with `agentRegistered: true`, the account may exist but SAP registration is not protocol-complete.
+10. Use `sap_payments_finalize_transaction` when a paid hosted builder returns an unsigned transaction to preview, sign locally, and optionally submit already-signed bytes through the hosted OOBE relay.
+11. Use `sap_agent_runtime_status` when asking an agent whether SAP MCP is connected or ready for paid/write work. It returns the hosted/local bridge routing truth without reading local files.
+12. Use `sap_pricing_catalog` or `https://mcp.sap.oobeprotocol.ai/pricing.json` to inspect generated hosted pricing tiers. The x402 challenge returned by a paid tool remains the final payment source of truth.
+
+Agent identity, profile images, Metaplex bridging, SNS linking, capabilities,
+pricing, and update fields are documented in:
+
+```txt
+https://mcp.sap.oobeprotocol.ai/docs/#/16_SAP_AGENT_IDENTITY_PIPELINE
+```
+
+Agents can discover the same recovery path without guessing. The hosted SAP MCP
+server exposes these free maintenance tools:
+
+| Tool | Purpose |
+| --- | --- |
+| `sap_agent_start` | Load the canonical startup playbook. |
+| `sap_agent_runtime_status` | Free runtime truth table for hosted connection, local `sap_payments` readiness expectations, write routing, forbidden actions, and next tool calls. |
+| `sap_pricing_catalog` | Free machine-readable pricing catalog generated from the hosted pricing registry. Also available at `/pricing.json`. |
+| `sap_protocol_invariants` | Return the canonical SAP program id, protocol treasury, registration fee, hosted/local routing rules, and forbidden actions. |
+| `sap_agent_identity_plan` | Free planner for SAP registration, image/profile updates, Metaplex identity, SNS linking, and verification. |
+| `sap_skills_upgrade_plan` | Return latest-release skill upgrade commands and target directories. |
+| `sap_runtime_repair_plan` | Return the pinned repair command and expected `sap_payments` bridge tools after restart. |
+
+If an agent says the local `sap_payments` bridge is missing, ask it to call
+`sap_runtime_repair_plan` before asking you to edit JSON, TOML, or YAML by hand.
 
 Show the active profile:
 
@@ -73,6 +114,12 @@ Hosted documentation:
 https://mcp.sap.oobeprotocol.ai/docs
 ```
 
+Hosted pricing catalog:
+
+```txt
+https://mcp.sap.oobeprotocol.ai/pricing.json
+```
+
 Client config docs:
 
 ```txt

package/USER_DOCS/01_HOSTED_REMOTE_MCP.md

@@ -29,7 +29,7 @@ Public `server.json` shape:
   "name": "sap-mcp-server",
   "title": "SAP MCP Server | OOBE Protocol",
   "description": "Hosted Solana-native MCP gateway for Synapse Agent Protocol tools, x402/pay.sh monetization, SNS identity, and agent operations.",
-  "version": "0.2.1",
+  "version": "0.9.21",
   "status": "online",
   "protocol": {
     "primary": "mcp",

package/USER_DOCS/03_PAYMENTS_X402_PAYSH.md

@@ -61,6 +61,10 @@ Most agent runtimes can connect to hosted SAP MCP directly, but not every runtim
 ```txt
 sap_payments_readiness
 sap_payments_call_paid_tool
+sap_payments_call_external_x402
+sap_payments_register_agent
+sap_payments_update_agent
+sap_payments_finalize_transaction
 ```
 
 `sap_payments_readiness` is free. It verifies the hosted endpoint, local bridge,
@@ -96,16 +100,41 @@ Install or repair runtime bridge config from the wizard:
 npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard
 ```
 
+Repair only hosted `sap` plus local `sap_payments` runtime entries:
+
+```bash
+npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair
+```
+
+The repair command keeps the active SAP MCP profile and only updates OOBE SAP
+MCP blocks, so unrelated MCP servers from other projects stay intact.
+
 The wizard can also write a local reference bundle under:
 
 ```txt
 ~/.config/mcp-sap/addons/x402-paid-call
 ```
 
-Local stdio SAP MCP also exposes the `sap_payments_call_paid_tool` challenge bridge and the legacy `sap_x402_paid_call` alias when the current process has a user-controlled wallet profile. The OOBE hosted server does not advertise these local signing helpers in non-custodial mode because payment signing must happen on the user's machine, not on `mcp.sap.oobeprotocol.ai`.
+Local stdio SAP MCP also exposes the `sap_payments_call_paid_tool` challenge bridge, `sap_payments_register_agent` for local SAP agent registration, `sap_payments_update_agent` for local SAP agent profile/image metadata updates, `sap_payments_finalize_transaction` for local transaction preview/sign/submit, and the legacy `sap_x402_paid_call` alias when the current process has a user-controlled wallet profile. The OOBE hosted server does not advertise these local signing helpers in non-custodial mode because payment and transaction signing must happen on the user's machine, not on `mcp.sap.oobeprotocol.ai`.
+
+When you call a non-OOBE external x402 HTTP endpoint discovered through SAP
+registry metadata, use `sap_payments_call_external_x402` instead of the hosted
+MCP paid-tool helper. It signs the external provider's 402 challenge locally,
+retries the same HTTP request, and returns the provider response plus the x402
+receipt. It is for generic HTTP x402 endpoints, not hosted SAP MCP tool names.
 
 Basic wallet reads do not require x402. Call `sol_get_balance`, `spl-token_getBalance`, and `spl-token_getTokenAccounts` directly on hosted SAP MCP. They should not be routed through the local payment bridge and should not depend on the facilitator.
 
+If hosted SAP MCP returns `hosted_local_signer_required`, no x402 payment was
+charged. The requested tool requires a user-owned Solana signature or is not
+available as a hosted unsigned builder. Do not retry the same hosted direct
+write. Use a local SAP MCP profile, an external signer, or a hosted unsigned
+builder followed by `sap_payments_finalize_transaction` when a builder exists.
+For `sap_register_agent`, call local `sap_payments_register_agent`. For
+`sap_update_agent`, call local `sap_payments_update_agent`; upload images or
+metadata JSON to IPFS, Arweave, Kommodo, or HTTPS first, then set `agentUri` or
+`metadataUri`.
+
 Security boundaries:
 
 - keypair bytes stay local and are never included in MCP client config;
@@ -161,7 +190,7 @@ endpoints:
           unit: requests
           scale: 1
           tiers:
-            - price_usd: 0.008
+            - price_usd: 0.001
 ```
 
 pay.sh metered rules to keep:
@@ -233,7 +262,7 @@ endpoints:
           unit: requests
           scale: 1
           tiers:
-            - price_usd: 0.008
+            - price_usd: 0.001
 
   - method: POST
     path: 'mcp/pro'

package/USER_DOCS/04_CLIENT_CONFIGS.md

@@ -45,7 +45,7 @@ url = "https://mcp.sap.oobeprotocol.ai/mcp"
 
 [mcp_servers.sap_payments]
 command = "npx.cmd"
-args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"]
+args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"]
 startup_timeout_sec = 300
 tool_timeout_sec = 300
 
@@ -65,7 +65,7 @@ the complete local stdio SAP MCP process instead of using the hosted endpoint, u
 ```toml
 [mcp_servers.sap]
 command = "npx.cmd"
-args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"]
+args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"]
 
 [mcp_servers.sap.env]
 SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE = "false"
@@ -92,8 +92,8 @@ Hermes profile YAML uses `mcp_servers` with a flat server block:
 ```yaml
 mcp_servers:
   sap:
-    url: https://mcp.sap.oobeprotocol.ai/mcp
-    transport: streamable-http
+    url: "https://mcp.sap.oobeprotocol.ai/mcp"
+    transport: "streamable-http"
 ```
 
 Do not nest `mcpServers.sap` inside a Hermes `mcp_servers.sap` block.
@@ -182,19 +182,26 @@ bridge shown above. It exposes only:
 ```txt
 sap_payments_readiness
 sap_payments_call_paid_tool
+sap_payments_call_external_x402
+sap_payments_register_agent
+sap_payments_update_agent
+sap_payments_finalize_transaction
 sap_payments_prepare_challenge
 sap_payments_sign_challenge
 sap_payments_verify_receipt
 sap_x402_paid_call
-sap_profile_current
-sap_x402_estimate_cost
 ```
 
+Use `sap_payments_finalize_transaction` when a hosted builder returns
+`transactionBase64`, `transaction`, or another unsigned Solana transaction. Do
+not create temporary signing scripts, read keypair JSON, or ask the hosted
+server to sign user-owned transactions.
+
 For Claude Code, use the official MCP CLI pattern:
 
 ```bash
 claude mcp add --transport http sap https://mcp.sap.oobeprotocol.ai/mcp
-claude mcp add --transport stdio sap_payments -- npx --yes --package @oobe-protocol-labs/sap-mcp-server@0.9.1 sap-mcp-server
+claude mcp add --transport stdio sap_payments -- npx --yes --package @oobe-protocol-labs/sap-mcp-server@0.9.21 sap-mcp-server
 ```
 
 Set `SAP_MCP_PAYMENTS_BRIDGE_ONLY=true` and `SAP_ALLOWED_TOOLS=all` in the

package/USER_DOCS/05_SKILLS_AND_TOOLS.md

@@ -13,17 +13,28 @@ The agent should then:
 
 1. call `sap_agent_start`;
 2. call `sap_skills_bundle` with `includeContents: true`;
-3. use exact tool names from `tools/list`;
-4. call `sap_payments_readiness` if the local `sap_payments` bridge is visible;
-5. use `sap_payments_call_paid_tool` for paid hosted tools that return x402 payment requirements.
+3. use the `sap-agent-intent-router` prompt when prompts are available and the user wants a paid call, registry write, escrow flow, identity update, or error recovery;
+4. call `sap_skills_upgrade_plan` if skills are missing or stale;
+5. use exact tool names from `tools/list`;
+6. call `sap_payments_readiness` if the local `sap_payments` bridge is visible;
+7. use `sap_payments_call_paid_tool` for paid hosted SAP MCP tools that return x402 payment requirements;
+8. use `sap_payments_call_external_x402` for external HTTP x402 agent endpoints discovered through SAP registry metadata;
+9. use `sap_payments_register_agent` for local non-custodial SAP agent registration when hosted `sap_register_agent` is blocked;
+10. use `sap_payments_update_agent` for local non-custodial SAP agent profile/image/metadata updates when hosted `sap_update_agent` is blocked;
+11. if a paid hosted builder returns `transactionBase64`, call `sap_payments_finalize_transaction` for local preview/sign/submit.
 
 If `sap_payments` is missing, run the wizard repair flow and restart the agent
 runtime:
 
 ```bash
-npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard
+npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair
 ```
 
+Agents should call the free `sap_runtime_repair_plan` tool before asking users
+to edit MCP config by hand. It returns the pinned latest-release repair command,
+what the repair changes, and which `sap_payments` tools should be visible after
+the runtime restarts.
+
 ## 2. Install Skills
 
 List bundled skills:
@@ -58,6 +69,27 @@ Install bundled skills into a local agent skill directory:
 }
 ```
 
+Plan a skills upgrade from hosted or local SAP MCP:
+
+```json
+{
+  "jsonrpc": "2.0",
+  "id": 3,
+  "method": "tools/call",
+  "params": {
+    "name": "sap_skills_upgrade_plan",
+    "arguments": {
+      "agent": "codex"
+    }
+  }
+}
+```
+
+`sap_skills_upgrade_plan` is free. In hosted mode it does not claim to write
+files on the user's machine; it returns exact commands and target directories.
+In local stdio mode, use `sap_skills_install` with `confirm: true` when the user
+wants the files written.
+
 ## 3. Tool Selection
 
 Use profile and context first:
@@ -69,23 +101,51 @@ Use profile and context first:
 
 Use global discovery:
 
-- `sap_list_all_agents`
-- `sap_discover_agents`
+- `sap_discover_agents` for targeted paid hosted search by `query`, `wallet`,
+  `agentPda`, `protocol`, `capability`, `capabilities`, or
+  `hasX402Endpoint`
+- `sap_list_all_agents` for global directory reads; use small `limit` values
+  and continue with `pagination.nextCursor`
 - `sap_fetch_protocol_index`
 - `sap_fetch_capability_index`
 
+When a capability-filtered search returns zero rows, retry with `query` or
+`wallet` before concluding an agent is absent. The canonical source is the
+on-chain AgentAccount directory; secondary protocol/capability indexes can lag.
+
 Use SNS:
 
-- `sap_sns_check_domain`
+- `sap_sns_check_domain` for a free single-domain availability check
 - `sap_sns_batch_check_domains`
 - `sap_sns_resolve_domain`
-- `sap_sns_register_agent_domain`
+- `sap_sns_register_agent_domain` only from a local SAP MCP profile with a
+  local wallet or external signer
+
+Hosted accountless SAP MCP cannot directly sign SNS registrations. If a hosted
+direct write returns `hosted_local_signer_required`, no x402 payment was charged;
+for `sap_register_agent`, call local `sap_payments_register_agent` with the
+same fields and `confirm: true`. For `sap_update_agent`, call local
+`sap_payments_update_agent` with the intended replacement fields and
+`confirm: true`; upload images or metadata JSON to a public URI first and set
+`agentUri` or `metadataUri`. For other writes, run the local profile flow or use
+hosted unsigned builders plus `sap_payments_finalize_transaction` where a builder
+exists.
 
 Use transactions:
 
 - `sap_preview_transaction`
 - `sap_sign_transaction`
 - `sap_submit_signed_transaction`
+- `sap_payments_finalize_transaction` for hosted builder transactions that must be previewed and signed locally; with `submit: true`, it submits already-signed bytes through the hosted OOBE relay and returns confirmation status plus retry guidance
+- `sap_payments_register_agent` for SAP agent registration through the local signer bridge
+- `sap_payments_update_agent` for SAP agent profile, image metadata, capabilities, protocols, pricing, and x402 endpoint updates through the local signer bridge
+
+If a local registry update returns Anchor 3012, `AccountNotInitialized`, or a
+`pricing_menu` message, the local payment/signing bridge is not the problem.
+That error is an on-chain SAP registry lifecycle issue for a required PDA. Do
+not retry paid hosted writes or run repair loops; call `sap_agent_next_action`
+and `sap_protocol_invariants`, then use the current SDK/server initializer path
+before retrying.
 
 ## 4. Agent Safety
 

package/USER_DOCS/06_DESKTOP_GUI_WIZARD.md

@@ -106,7 +106,7 @@ url = "https://mcp.sap.oobeprotocol.ai/mcp"
 
 [mcp_servers.sap_payments]
 command = "npx"
-args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"]
+args = ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"]
 startup_timeout_sec = 300
 tool_timeout_sec = 300
 
@@ -119,7 +119,7 @@ SAP_LOG_LEVEL = "info"
 
 On Windows, the command is `npx.cmd`.
 
-The hosted `sap` server lists and executes remote SAP MCP tools. The local `sap_payments` bridge signs x402 payment proofs with the active local SAP MCP profile and retries paid hosted calls without exposing keypair bytes.
+The hosted `sap` server lists and executes remote SAP MCP tools. The local `sap_payments` bridge signs x402 payment proofs with the active local SAP MCP profile, retries paid hosted calls, registers SAP agents locally with `sap_payments_register_agent` when hosted direct registration is blocked, updates SAP agent profile metadata locally with `sap_payments_update_agent` when hosted direct update is blocked, and finalizes unsigned hosted transactions with `sap_payments_finalize_transaction` without exposing keypair bytes.
 
 ## 6. Runtime Configs Written By The GUI
 
@@ -138,7 +138,7 @@ Claude Desktop uses a root `mcpServers` JSON object:
     },
     "sap_payments": {
       "command": "npx",
-      "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"],
+      "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"],
       "env": {
         "SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE": "false",
         "SAP_MCP_PAYMENTS_BRIDGE_ONLY": "true",
@@ -170,7 +170,7 @@ Hermes global `mcp.json` uses flat server entries:
   },
   "sap_payments": {
     "command": "npx",
-    "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"],
+    "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"],
     "env": {
       "SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE": "false",
       "SAP_MCP_PAYMENTS_BRIDGE_ONLY": "true",
@@ -186,20 +186,20 @@ Hermes profile YAML uses top-level `mcp_servers`:
 ```yaml
 mcp_servers:
   sap:
-    url: https://mcp.sap.oobeprotocol.ai/mcp
-    transport: streamable-http
+    url: "https://mcp.sap.oobeprotocol.ai/mcp"
+    transport: "streamable-http"
   sap_payments:
-    command: npx
+    command: "npx"
     args:
-      - --yes
-      - --package
-      - @oobe-protocol-labs/sap-mcp-server@0.9.1
-      - sap-mcp-server
+      - "--yes"
+      - "--package"
+      - "@oobe-protocol-labs/sap-mcp-server@0.9.21"
+      - "sap-mcp-server"
     env:
       SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE: "false"
       SAP_MCP_PAYMENTS_BRIDGE_ONLY: "true"
-      SAP_ALLOWED_TOOLS: all
-      SAP_LOG_LEVEL: info
+      SAP_ALLOWED_TOOLS: "all"
+      SAP_LOG_LEVEL: "info"
 ```
 
 ### 6.3 OpenClaw
@@ -215,7 +215,7 @@ OpenClaw MCP JSON uses the same root `mcpServers` structure as generic MCP clien
     },
     "sap_payments": {
       "command": "npx",
-      "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.1", "sap-mcp-server"],
+      "args": ["--yes", "--package", "@oobe-protocol-labs/sap-mcp-server@0.9.21", "sap-mcp-server"],
       "env": {
         "SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE": "false",
         "SAP_MCP_PAYMENTS_BRIDGE_ONLY": "true",
@@ -260,6 +260,12 @@ The same setup can always be done from terminal:
 npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard
 ```
 
+Repair only the hosted runtime/payment bridge entries:
+
+```bash
+npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config repair
+```
+
 Show active profile:
 
 ```bash

package/USER_DOCS/07_SMITHERY_AND_MARKETPLACES.md

@@ -102,6 +102,13 @@ Then paid hosted calls should be routed through:
 sap_payments_call_paid_tool
 ```
 
+If a paid hosted builder returns an unsigned transaction payload, finalize it
+locally with:
+
+```txt
+sap_payments_finalize_transaction
+```
+
 ## 6. Native x402 Client Flow
 
 If the user already has an x402-capable client, the flow is:

package/config.example.json

@@ -53,10 +53,11 @@
     "maxTimeoutSeconds": 120,
     "payShCheckoutUrl": "https://pay.sh/checkout/YOUR_CHECKOUT_ID",
     "prices": {
-      "readPremiumUsd": 0.008,
-      "builderUsd": 0.05,
-      "valueFixedUsd": 0.2,
-      "valueBps": 50,
+      "readPremiumUsd": 0.001,
+      "builderUsd": 0.008,
+      "valueFixedUsd": 0.09,
+      "heavyValueUsd": 0.05,
+      "valueBps": 0,
       "minUsd": 0.001,
       "maxUsd": 100
     }

package/config.schema.json

@@ -319,22 +319,27 @@
             "readPremiumUsd": {
               "type": "number",
               "exclusiveMinimum": 0,
-              "default": 0.008
+              "default": 0.001
             },
             "builderUsd": {
               "type": "number",
               "exclusiveMinimum": 0,
-              "default": 0.05
+              "default": 0.008
             },
             "valueFixedUsd": {
               "type": "number",
               "minimum": 0,
-              "default": 0.2
+              "default": 0.09
+            },
+            "heavyValueUsd": {
+              "type": "number",
+              "minimum": 0,
+              "default": 0.15
             },
             "valueBps": {
               "type": "number",
               "minimum": 0,
-              "default": 50
+              "default": 0
             },
             "minUsd": {
               "type": "number",

package/config.secure-example.json

@@ -56,10 +56,11 @@
     "maxTimeoutSeconds": 120,
     "payShCheckoutUrl": "https://pay.sh/checkout/YOUR_CHECKOUT_ID",
     "prices": {
-      "readPremiumUsd": 0.008,
-      "builderUsd": 0.05,
-      "valueFixedUsd": 0.2,
-      "valueBps": 50,
+      "readPremiumUsd": 0.001,
+      "builderUsd": 0.008,
+      "valueFixedUsd": 0.09,
+      "heavyValueUsd": 0.05,
+      "valueBps": 0,
       "minUsd": 0.001,
       "maxUsd": 100
     }

package/dist/adapters/index.d.ts

@@ -1,5 +1,11 @@
 /**
- * Adapters - Export all adapter modules
+ * @name adapters/index
+ * @description Barrel export for all SAP MCP adapter modules (MCP and Solana).
+ *
+ * Re-exports the MCP response helpers and Solana connection utilities so that
+ * the rest of the server can import them from a single entry point.
+ *
+ * @module adapters/index
  */
 export * from './mcp/index.js';
 export * from './solana/index.js';

package/dist/adapters/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/adapters/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,cAAc,gBAAgB,CAAC;AAC/B,cAAc,mBAAmB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/adapters/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,cAAc,gBAAgB,CAAC;AAC/B,cAAc,mBAAmB,CAAC"}

package/dist/adapters/index.js

@@ -1,5 +1,11 @@
 /**
- * Adapters - Export all adapter modules
+ * @name adapters/index
+ * @description Barrel export for all SAP MCP adapter modules (MCP and Solana).
+ *
+ * Re-exports the MCP response helpers and Solana connection utilities so that
+ * the rest of the server can import them from a single entry point.
+ *
+ * @module adapters/index
  */
 export * from './mcp/index.js';
 export * from './solana/index.js';

package/dist/adapters/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/adapters/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,cAAc,gBAAgB,CAAC;AAC/B,cAAc,mBAAmB,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/adapters/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,cAAc,gBAAgB,CAAC;AAC/B,cAAc,mBAAmB,CAAC"}

package/dist/adapters/mcp/errors.d.ts

@@ -1,5 +1,17 @@
 /**
- * MCP error helper
+ * @name adapters/mcp/errors
+ * @description Custom error class for MCP protocol-level failures.
+ *
+ * @module adapters/mcp/errors
+ */
+/**
+ * @name McpError
+ * @description Error thrown when an MCP protocol operation fails.
+ *
+ * Extends the native `Error` class with a fixed `name` property so that
+ * consumers can distinguish MCP errors from other runtime errors.
+ *
+ * @usedBy `adapters/mcp/index.ts`, MCP tool handlers
  */
 export declare class McpError extends Error {
     constructor(message: string);

package/dist/adapters/mcp/errors.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"errors.d.ts","sourceRoot":"","sources":["../../../src/adapters/mcp/errors.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,qBAAa,QAAS,SAAQ,KAAK;gBACrB,OAAO,EAAE,MAAM;CAI5B"}
+{"version":3,"file":"errors.d.ts","sourceRoot":"","sources":["../../../src/adapters/mcp/errors.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;;;;GAQG;AACH,qBAAa,QAAS,SAAQ,KAAK;gBACrB,OAAO,EAAE,MAAM;CAI5B"}

package/dist/adapters/mcp/errors.js

@@ -1,5 +1,17 @@
 /**
- * MCP error helper
+ * @name adapters/mcp/errors
+ * @description Custom error class for MCP protocol-level failures.
+ *
+ * @module adapters/mcp/errors
+ */
+/**
+ * @name McpError
+ * @description Error thrown when an MCP protocol operation fails.
+ *
+ * Extends the native `Error` class with a fixed `name` property so that
+ * consumers can distinguish MCP errors from other runtime errors.
+ *
+ * @usedBy `adapters/mcp/index.ts`, MCP tool handlers
  */
 export class McpError extends Error {
     constructor(message) {

package/dist/adapters/mcp/errors.js.map

@@ -1 +1 @@
-{"version":3,"file":"errors.js","sourceRoot":"","sources":["../../../src/adapters/mcp/errors.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,MAAM,OAAO,QAAS,SAAQ,KAAK;IACjC,YAAY,OAAe;QACzB,KAAK,CAAC,OAAO,CAAC,CAAC;QACf,IAAI,CAAC,IAAI,GAAG,UAAU,CAAC;IACzB,CAAC;CACF"}
+{"version":3,"file":"errors.js","sourceRoot":"","sources":["../../../src/adapters/mcp/errors.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH;;;;;;;;GAQG;AACH,MAAM,OAAO,QAAS,SAAQ,KAAK;IACjC,YAAY,OAAe;QACzB,KAAK,CAAC,OAAO,CAAC,CAAC;QACf,IAAI,CAAC,IAAI,GAAG,UAAU,CAAC;IACzB,CAAC;CACF"}

package/dist/adapters/mcp/index.d.ts

@@ -1,5 +1,11 @@
 /**
- * MCP adapter barrel export
+ * @name adapters/mcp/index
+ * @description Barrel export for the MCP adapter subsystem.
+ *
+ * Re-exports tool response helpers, resource response helpers,
+ * prompt response helpers, and the MCP error class.
+ *
+ * @module adapters/mcp/index
  */
 export { createTextResponse, createJsonResponse, createErrorResponse } from './tool-response.js';
 export { createResourceResponse } from './resource-response.js';

package/dist/adapters/mcp/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/adapters/mcp/index.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,kBAAkB,EAAE,kBAAkB,EAAE,mBAAmB,EAAE,MAAM,oBAAoB,CAAC;AACjG,OAAO,EAAE,sBAAsB,EAAE,MAAM,wBAAwB,CAAC;AAChE,OAAO,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/adapters/mcp/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,EAAE,kBAAkB,EAAE,kBAAkB,EAAE,mBAAmB,EAAE,MAAM,oBAAoB,CAAC;AACjG,OAAO,EAAE,sBAAsB,EAAE,MAAM,wBAAwB,CAAC;AAChE,OAAO,EAAE,oBAAoB,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,EAAE,QAAQ,EAAE,MAAM,aAAa,CAAC"}