@buildaureon/mcp 0.1.9 → 0.1.10

package/docs/auth.md

@@ -1,6 +1,6 @@
 # Authentication Guide
 
-How **`@buildaureon/mcp`** `v0.1.9` authenticates to the live AUREON API — aligned with `@buildaureon/sdk`, safe for humans and for agents that call the **54** stdio tools.
+How **`@buildaureon/mcp`** `v0.1.10` authenticates to the live AUREON API — aligned with `@buildaureon/sdk`, safe for humans and for agents that call the **54** tools over hosted HTTP or local stdio.
 
 Related docs: [Setup](./setup.md) · [Tools](./tools.md) · [Agent guide](./agent-guide.md) · [Architecture](./architecture.md) · [Security](./security.md) · [Package README](../README.md)
 
@@ -8,7 +8,7 @@ Related docs: [Setup](./setup.md) · [Tools](./tools.md) · [Agent guide](./agen
 
 ## Who this is for
 
-- **Agent operators** wiring Cursor or Claude Desktop with an issued developer key
+- **Agent operators** wiring Cursor or Claude Desktop to the hosted URL or to stdio with an issued developer key
 - **Integrators** comparing MCP auth to the typed SDK client
 - **Security reviewers** checking that private keys never enter the MCP process
 - **Agents** reading this file as context before calling `aureon_me`, restore, or vault prepare tools
@@ -19,13 +19,22 @@ If you have not configured the host yet, start with [./setup.md](./setup.md), th
 
 ## Goals of MCP auth
 
-1. Reach the official API `https://api.aureonlabs.network` (currently testnet 46630). Opt in to chain 4663 with `AUREON_NETWORK=mainnet`.
+1. Reach the official API `https://api.aureonlabs.network` on mainnet. Stay on testnet with `AUREON_NETWORK=testnet`. Public Living Capital is still the testnet console.
 2. Bind control-plane actions to a wallet identity (issued key or Bearer session).
 3. Keep signing and broadcasting of on-chain vault steps **outside** MCP.
 4. Prefer a long-lived issued key for always-on agents over interactive wallet handshakes.
 
 The operator utility at [app.aureonlabs.network](https://app.aureonlabs.network) remains wallet-Bearer oriented for humans. MCP and the SDK share the issued-key path for automation.
 
+### Hosted URL vs stdio
+
+| How you connect | Where the issued key lives |
+| --- | --- |
+| `https://mcp.aureonlabs.network/mcp` | Optional. URL-only for open tools. Your wallet tools need `X-Aureon-Api-Key`. |
+| `npx -y @buildaureon/mcp` | In the host `env` as `AUREON_API_KEY` (your Developers key). |
+
+Private keys stay out of both. Hosted without a header is not your wallet. Hosted with `X-Aureon-Api-Key` is your issued key. Stdio identity is the key you set in env.
+
 ---
 
 ## Credential types
@@ -51,7 +60,7 @@ Plain language:
 | --- | --- |
 | `AUREON_API_KEY` | Preferred. Issued developer key. |
 | `AUREON_AUTH_TOKEN` | Optional Bearer. Use when you intentionally want a session without (or in addition to) a key — see conflict rules below. |
-| `AUREON_NETWORK` | Optional. Omit for official API / testnet 46630. Set `mainnet` for chain 4663. |
+| `AUREON_NETWORK` | Optional. Omit for official API / mainnet. Set `testnet` to stay on testnet. |
 | `AUREON_API_URL` | Optional override of `https://api.aureonlabs.network`. |
 
 Startup rule: at least one of `AUREON_API_KEY` or `AUREON_AUTH_TOKEN` must be set or the MCP process exits with a clear error.
@@ -77,7 +86,7 @@ Minimal env (official API):
 
 ```bash
 AUREON_API_KEY=aureon_....
-# AUREON_NETWORK=mainnet   # chain 4663 on the same official host
+# AUREON_NETWORK=testnet   # stay on testnet on the same official host
 ```
 
 With only the issued key, agents can sync portfolio, create objectives, fetch restore plans, restore, refresh watchdog, and manage developer keys — without an interactive signature each session.
@@ -115,7 +124,7 @@ Agent → aureon_verify_wallet(address, message, signature, inviteCode?)
 Later tools use getAccessToken() from the in-process session provider.
 ```
 
-Early access may require an `inviteCode` on first verify for a new wallet.
+`inviteCode` is only for the optional wallet Bearer handshake when the API asks for it. It is not required to use hosted MCP or stdio with an issued key.
 
 You may also seed `AUREON_AUTH_TOKEN` in the host env if you already obtained a Bearer elsewhere. That token is loaded into the same in-process session provider at startup.
 
@@ -219,9 +228,9 @@ Never paste a private key into MCP tool arguments or host env “for convenience
 | `401` Unauthorized | Key revoked/paused, Bearer expired, or typo | Rotate key or re-verify wallet |
 | Wrong wallet on `aureon_me` | Bearer winning over key | `aureon_logout`; remove env Bearer; restart |
 | `aureon_verify_wallet` fails | Bad signature, stale nonce, or missing invite | New nonce; re-sign; supply `inviteCode` if required |
-| `aureon_dev_login` fails on live API | Expected | Use an issued key. Public host is still 46630. |
+| `aureon_dev_login` fails on live API | Expected | Use an issued key. Public Living Capital is still the testnet console. |
 | Prepare tools succeed but funds do not move | Unsigned steps not broadcast | Sign outside MCP with a real wallet |
-| Agent invents a local API URL | Misconfigured override | Omit `AUREON_API_URL` for the official API, or set `AUREON_NETWORK=mainnet` |
+| Agent invents a local API URL | Misconfigured override | Omit `AUREON_API_URL` for the official API, or set `AUREON_NETWORK=testnet` |
 
 Map structured SDK errors in tool output to the same categories; do not retry blindly on `401` without rotating credentials.
 
@@ -235,7 +244,7 @@ Map structured SDK errors in tool output to the same categories; do not retry bl
 4. **Call `aureon_me` once** after connect to confirm identity before write tools.
 5. **On identity mismatch**, clear Bearer before creating objectives or restoring.
 6. **Treat Developers keys like passwords** — rotate on leak; use labeled keys per host.
-7. **Keep MCP local stdio** — do not expose the process on a public port.
+7. **Do not expose your stdio process** — use `https://mcp.aureonlabs.network/mcp` for the official host; do not publish your own child process.
 8. **Read** [./agent-guide.md](./agent-guide.md) before multi-step restore or market-event rehearsals.
 9. **Respect locked objective fields** — recreate rather than fighting update errors (see tools doc).
 10. **Assume tool output may be logged** by the host; minimize secret material in responses.
@@ -246,16 +255,17 @@ Map structured SDK errors in tool output to the same categories; do not retry bl
 
 ```text
 MCP host (Cursor / Claude)
-    │  stdio
+    │  Streamable HTTP  https://mcp.aureonlabs.network/mcp
+    │  or stdio  npx @buildaureon/mcp
     ▼
-@buildaureon/mcp  (54 tools, no private key)
+adapter  (54 tools, no private key)
     │
     ▼
 @buildaureon/sdk  (HTTP, retries, types)
     │  HTTP(S) + API key and/or Bearer
     ▼
-default https://api.aureonlabs.network (46630)
-opt-in  AUREON_NETWORK=mainnet (chain 4663, same host)
+default https://api.aureonlabs.network (mainnet)
+opt-in  AUREON_NETWORK=testnet (same host)
     │
     ├── control plane (objectives, portfolio, restore, …)
     └── prepare vault steps → human/agent signs elsewhere
@@ -320,11 +330,11 @@ Do not reuse the compromised secret “temporarily.” Treat rotation as mandato
 
 - Issued key → API key header / client option
 - Bearer → access token via the session provider
-- Base URL → `https://api.aureonlabs.network` by default (currently 46630). `AUREON_NETWORK=mainnet` selects chain 4663.
+- Base URL → `https://api.aureonlabs.network` by default (mainnet). `AUREON_NETWORK=testnet` stays on testnet.
 
 If a typed SDK script works with your issued key but MCP fails, compare env names (`AUREON_API_KEY` vs hard-coded client options) and confirm the host actually injects env into the stdio child process.
 
-Package version for this guide: **`@buildaureon/mcp` `v0.1.9`**.
+Package version for this guide: **`@buildaureon/mcp` `v0.1.10`**.
 
 ---
 

package/docs/security.md

@@ -10,16 +10,16 @@ This document is for operators configuring agent hosts and for AI agents that mu
 
 | Boundary | Assumption | Failure mode if broken |
 | --- | --- | --- |
-| MCP process | Local stdio child of a trusted host | Remote callers could invoke any registered tool |
+| MCP process | Local stdio child of a trusted host, **or** the official hosted HTTP process | A leaked URL-plus-gate, or a published homemade stdio port, lets callers invoke every registered tool |
 | Issued API key | Equivalent to “act as this developer / wallet scope” on the control plane | Attacker creates objectives, restores, prepares vault steps, manages keys |
 | Private key | Never enters MCP env or process | Full fund theft if combined with broadcast capability |
 | Host LLM / agent | Can call any enabled tool | Prompt injection or confused deputy may trigger writes |
 | Operator utility | Separate wallet-Bearer UI | Unrelated to MCP, but same API identity if same wallet |
-| HTTP(S) to API | Default official host TLS is `https://api.aureonlabs.network` (currently 46630) | MITM if URL pointed at attacker |
+| HTTP(S) to API | Default official host TLS is `https://api.aureonlabs.network` (mainnet by omit) | MITM if URL pointed at attacker |
 
 ```mermaid
 flowchart LR
-  Host[MCP_host_and_LLM] -->|tool_calls_stdio| MCP[local_MCP_adapter]
+  Host[MCP_host_and_LLM] -->|stdio_or_hosted_HTTP| MCP[MCP_adapter]
   MCP -->|API_key_and_optional_Bearer| API[official_api_aureonlabs_network]
   MCP -.->|never_holds| PK[private_keys]
   Human[Human_operator] -->|reviews_and_signs| Chain[Robinhood_Chain]
@@ -207,8 +207,8 @@ Use this before enabling `@buildaureon/mcp` on a machine that can affect real ca
 - [ ] Issued API key created specifically for this host
 - [ ] Key stored only in host secret/env config (not in git)
 - [ ] Private keys absent from MCP env and agent-accessible storage
-- [ ] Default API is `https://api.aureonlabs.network` (currently 46630) unless `AUREON_NETWORK=mainnet` (chain 4663)
-- [ ] Host is local stdio — not published as an open network service
+- [ ] Default API is `https://api.aureonlabs.network` on mainnet unless `AUREON_NETWORK=testnet`
+- [ ] You use official hosted `https://mcp.aureonlabs.network/mcp` **or** local stdio — you did not publish your own stdio port
 - [ ] Write tools understood by operators (`create`, `restore`, `prepare`, key CRUD)
 - [ ] Prepare → human sign → broadcast workflow documented for the team
 - [ ] Pause/revoke path tested once (know which tool/UI to use under stress)
@@ -261,7 +261,7 @@ Do not paste live secrets into tickets.
 | Cloud / browser agent with remote tool runner | Broader persistence and sharing surfaces | Short-lived keys; revoke often; avoid high-value wallets |
 | Shared demo machine | Key reuse across people | Unique keys; revoke after demo; no private keys nearby |
 
-In all cases: MCP remains a **local adapter pattern** conceptually. If a product remotes the stdio server, you have changed the threat model — re-validate network ACLs and auth before use.
+The official hosted URL is `https://mcp.aureonlabs.network/mcp`. Connect is URL-only. A server key is used only for open tools. Your wallet tools need `X-Aureon-Api-Key`. Do not treat a homemade public stdio port as equivalent. Keep private keys out of every host.
 
 ---
 
@@ -332,4 +332,4 @@ Follow AUREON’s published support / security channels on the product site; inc
 
 ## 15. Summary
 
-Treat `@buildaureon/mcp` as a **local, non-custodial stdio adapter** over `@buildaureon/sdk`. Default API is `https://api.aureonlabs.network` (currently testnet 46630). Protect issued keys like passwords, keep private keys out of the MCP process, require human (or hardened external) signing for deposit/withdraw broadcast, rotate and revoke quickly, and assume the LLM is not a security boundary — configuration hygiene and least privilege are.
+Treat AUREON MCP as a **non-custodial adapter** over `@buildaureon/sdk`: official hosted HTTP at `https://mcp.aureonlabs.network/mcp`, or local stdio via `@buildaureon/mcp`. Default API is `https://api.aureonlabs.network` on mainnet. Public Living Capital is still the testnet console. Protect issued keys like passwords, keep private keys out of the MCP process, require human (or hardened external) signing for deposit/withdraw broadcast, rotate and revoke quickly, and assume the LLM is not a security boundary — configuration hygiene and least privilege are.

package/docs/setup.md

@@ -1,8 +1,17 @@
 # Setup Guide
 
-Complete installation and host configuration for **`@buildaureon/mcp`** `v0.1.9` against the live AUREON API.
+Complete installation and host configuration for **`@buildaureon/mcp`** `v0.1.10` against the live AUREON API.
 
-This package is a **stdio** [Model Context Protocol](https://modelcontextprotocol.io) server. It wraps [`@buildaureon/sdk`](https://github.com/buildaureon/aureon-sdk) and exposes **54 tools** so Cursor, Claude Desktop, and other MCP hosts can call the Financial Compass control plane.
+This package is the official [Model Context Protocol](https://modelcontextprotocol.io) adapter for AUREON. It wraps [`@buildaureon/sdk`](https://github.com/buildaureon/aureon-sdk) and exposes **54 tools** so Cursor, Claude Desktop, and other MCP hosts can call the Financial Compass control plane.
+
+There are two supported transports:
+
+| Transport | Endpoint / command | Auth in the host |
+| --- | --- | --- |
+| **Hosted HTTP** | `https://mcp.aureonlabs.network/mcp` | None required to connect. Optional `X-Aureon-Api-Key` for your wallet tools. |
+| **Local stdio** | `npx -y @buildaureon/mcp` | Your issued `AUREON_API_KEY` in the host `env` block |
+
+Both surfaces are the same 54 tools. Neither signs or broadcasts. Confirm hosted health at [https://mcp.aureonlabs.network/healthz](https://mcp.aureonlabs.network/healthz).
 
 Related docs: [Authentication](./auth.md) · [Tools](./tools.md) · [Agent guide](./agent-guide.md) · [Architecture](./architecture.md) · [Security](./security.md) · [Package README](../README.md)
 
@@ -10,10 +19,11 @@ Related docs: [Authentication](./auth.md) · [Tools](./tools.md) · [Agent guide
 
 ## What this guide covers
 
+- Hosted URL vs local stdio — which to pick
 - What you need before connecting an agent
-- Environment variables the MCP process reads
-- How to create an issued developer API key
-- Cursor and Claude Desktop config (published package first)
+- Environment variables the **stdio** process reads
+- How to create an issued developer API key (required for stdio; not pasted into Cursor for hosted)
+- Cursor and Claude Desktop config (hosted URL first, then published package)
 - Running via `npx` without a permanent install
 - Building from a source clone (optional)
 - Smoke prompts to verify the wire is live
@@ -28,9 +38,9 @@ If you only want auth semantics (key vs Bearer vs private key), skip ahead to [.
 | Requirement | Notes |
 | --- | --- |
 | **Node.js 20+** | ESM runtime. Check with `node -v`. |
-| **Issued developer API key** | Issue the key at [app.aureonlabs.network](https://app.aureonlabs.network) → **Developers**. Plaintext is shown once. |
-| **Network access** | Default is the official API `https://api.aureonlabs.network` (currently chain 46630). Optional `AUREON_NETWORK=mainnet` selects chain 4663 on the same host. |
-| **MCP host** | Cursor, Claude Desktop, or any client that can launch a stdio MCP server. |
+| **Issued developer API key** | Required for **stdio**. Issue it at [app.aureonlabs.network](https://app.aureonlabs.network) → **Developers**. Not pasted into Cursor when you use the hosted URL. |
+| **Network access** | Default is the official API `https://api.aureonlabs.network` on mainnet. Optional `AUREON_NETWORK=testnet` stays on testnet on the same host. Public Living Capital is still the testnet console. |
+| **MCP host** | Cursor, Claude Desktop, or any client that can attach to Streamable HTTP **or** spawn a stdio MCP server. |
 
 You do **not** need a wallet Bearer token for day-to-day control-plane tools when you use an issued key.
 
@@ -45,11 +55,11 @@ The MCP server never custodies funds and never signs chain transactions.
 | Item | Value |
 | --- | --- |
 | npm package | `@buildaureon/mcp` |
-| Version | `0.1.9` |
+| Version | `0.1.10` |
 | Depends on | `@buildaureon/sdk` |
-| Transport | stdio MCP (JSON-RPC over stdin/stdout) |
+| Transports | Hosted Streamable HTTP at `https://mcp.aureonlabs.network/mcp`, or local stdio (`npx -y @buildaureon/mcp`) |
 | Tool count | 54 |
-| Default API | `https://api.aureonlabs.network` (testnet 46630). `AUREON_NETWORK=mainnet` selects chain 4663. |
+| Default API | `https://api.aureonlabs.network` on mainnet. `AUREON_NETWORK=testnet` stays on testnet. |
 | Console | [app.aureonlabs.network](https://app.aureonlabs.network) |
 
 Primary launch command (recommended for hosts):
@@ -68,12 +78,12 @@ The process reads these at startup. Put them in your MCP host `env` block (Curso
 | --- | --- | --- | --- |
 | `AUREON_API_KEY` | **Preferred** | — | Issued developer key (`aureon_…`). Product access **and** wallet identity for control-plane tools. |
 | `AUREON_AUTH_TOKEN` | Optional | — | Wallet Bearer session. Wins over key identity when both are present on a request. |
-| `AUREON_NETWORK` | Optional | `testnet` | Omit for official API / 46630. Set `mainnet` for chain 4663. |
+| `AUREON_NETWORK` | Optional | `mainnet` | Omit for official API / mainnet. Set `testnet` to stay on testnet. |
 | `AUREON_API_URL` | Optional | `https://api.aureonlabs.network` | Override the official host only if you must. |
 
 At least one of `AUREON_API_KEY` or `AUREON_AUTH_TOKEN` must be set or the server refuses to start.
 
-**Recommendation:** set only `AUREON_API_KEY`. The process uses the official API. Add `AUREON_NETWORK=mainnet` only if you want chain 4663 on that host.
+**Recommendation:** set only `AUREON_API_KEY`. The process uses the official API on mainnet. Add `AUREON_NETWORK=testnet` only to stay on testnet on that host.
 
 Never put a wallet private key in MCP env. Prepare tools return unsigned calldata; the host wallet signs elsewhere.
 
@@ -82,7 +92,7 @@ Never put a wallet private key in MCP env. Prepare tools return unsigned calldat
 ## Create an issued developer API key
 
 1. Open [https://app.aureonlabs.network](https://app.aureonlabs.network).
-2. Complete invite / early-access flow if prompted, then connect your wallet.
+2. Connect your wallet.
 3. Open **Developers**.
 4. Create a key with a clear label (for example `cursor-mcp` or `claude-desktop`).
 5. Copy the secret immediately — plaintext is shown once.
@@ -95,7 +105,44 @@ That key binds control-plane calls to your wallet. You do not need a separate Be
 
 ## Cursor configuration
 
-### Option A — published package (recommended)
+### Option A — official hosted URL (recommended first use)
+
+No Node process. A user key is not required to connect. Merge [`../examples/cursor.hosted.mcp.json`](../examples/cursor.hosted.mcp.json):
+
+```json
+{
+  "mcpServers": {
+    "aureon": {
+      "url": "https://mcp.aureonlabs.network/mcp"
+    }
+  }
+}
+```
+
+Restart Cursor. Confirm **aureon** appears under MCP / tools. Ask: *“Use aureon_ping.”*
+
+Open tools without a key: `aureon_ping`, `aureon_list_market_presets`, `aureon_validate_receipt`.
+
+For **your** wallet (`aureon_me`, portfolio, objectives, restore, vault prepare), add the header. Template: [`../examples/cursor.hosted.user.mcp.json`](../examples/cursor.hosted.user.mcp.json).
+
+```json
+{
+  "mcpServers": {
+    "aureon": {
+      "url": "https://mcp.aureonlabs.network/mcp",
+      "headers": {
+        "X-Aureon-Api-Key": "aureon_...."
+      }
+    }
+  }
+}
+```
+
+Health check: [https://mcp.aureonlabs.network/healthz](https://mcp.aureonlabs.network/healthz) must report `ok: true` and `tools: 54`.
+
+Use Option B when you want the key in host env instead of an HTTP header.
+
+### Option B — published stdio package (your issued key)
 
 Create or edit `.cursor/mcp.json` in the project, or merge into your user MCP config:
 
@@ -117,9 +164,9 @@ Restart Cursor (or reload MCP servers). Confirm **aureon** appears under MCP / t
 
 Ask a smoke prompt such as: *“Use aureon_ping, then aureon_me.”*
 
-Issue the key at [app.aureonlabs.network](https://app.aureonlabs.network) → **Developers**. The official API is used when `AUREON_API_URL` is omitted. Add `"AUREON_NETWORK": "mainnet"` only to select chain 4663.
+Issue the key at [app.aureonlabs.network](https://app.aureonlabs.network) → **Developers**. Public Living Capital is still the testnet console. The official API is used when `AUREON_API_URL` is omitted (mainnet). Add `"AUREON_NETWORK": "testnet"` only to stay on testnet.
 
-### Option B — from a local build
+### Option C — from a local build
 
 Use this only when you are iterating on a clone of the package. Replace the working directory with your own clone path.
 
@@ -140,13 +187,25 @@ Use this only when you are iterating on a clone of the package. Replace the work
 
 Build first (`pnpm build` or `npm run build` inside the MCP package) so `dist/index.js` exists.
 
-Prefer Option A for everyday agent use. Local `cwd` configs are for contributors and package development.
+Prefer Option A for everyday agent use. Option B when you need your own key. Option C (`cwd`) is for contributors and package development.
 
 ---
 
 ## Claude Desktop configuration
 
-Merge the same shape into Claude Desktop’s MCP config file (location depends on your OS; Claude’s docs describe where `claude_desktop_config.json` lives).
+If the host supports a remote MCP URL, use the same hosted endpoint as Cursor:
+
+```json
+{
+  "mcpServers": {
+    "aureon": {
+      "url": "https://mcp.aureonlabs.network/mcp"
+    }
+  }
+}
+```
+
+Otherwise merge the stdio shape into Claude Desktop’s MCP config file (location depends on your OS; Claude’s docs describe where `claude_desktop_config.json` lives).
 
 ```json
 {
@@ -164,9 +223,9 @@ Merge the same shape into Claude Desktop’s MCP config file (location depends o
 
 Restart Claude Desktop after saving. In a new chat, ask the model to list AUREON tools or call `aureon_ping`.
 
-For a from-source Claude entry, use `node` + `dist/index.js` with `"cwd": "/path/to/your/clone/mcp"` the same way as Cursor Option B.
+For a from-source Claude entry, use `node` + `dist/index.js` with `"cwd": "/path/to/your/clone/mcp"` the same way as Cursor Option C.
 
-Example templates also ship in the package under `examples/cursor.mcp.json` and `examples/claude-desktop.json`.
+Example templates: [`examples/cursor.hosted.mcp.json`](../examples/cursor.hosted.mcp.json), [`examples/cursor.mcp.json`](../examples/cursor.mcp.json), [`examples/claude-desktop.json`](../examples/claude-desktop.json).
 
 ---
 
@@ -177,7 +236,7 @@ From a terminal, with the key in the environment:
 ```bash
 export AUREON_API_KEY=aureon_....
 # omit AUREON_API_URL for official API https://api.aureonlabs.network
-# export AUREON_NETWORK=mainnet   # chain 4663 on the same official host
+# export AUREON_NETWORK=testnet   # stay on testnet on the same official host
 
 npx -y @buildaureon/mcp
 ```
@@ -187,7 +246,7 @@ On Windows PowerShell:
 ```powershell
 $env:AUREON_API_KEY = "aureon_...."
 # omit AUREON_API_URL for official API https://api.aureonlabs.network
-# $env:AUREON_NETWORK = "mainnet"   # chain 4663 on the same official host
+# $env:AUREON_NETWORK = "testnet"   # stay on testnet on the same official host
 npx -y @buildaureon/mcp
 ```
 
@@ -259,7 +318,7 @@ For write workflows (create objective, restore, prepare vault), see [./agent-gui
 
 ## Verify the tool surface
 
-A healthy install exposes auth, read, objective, portfolio, execution, market, vault prepare, and developer key tools — **47** in total.
+A healthy install exposes auth, read, objective, portfolio, execution, market, vault prepare, and developer key tools — **54** in total.
 
 You do not need every tool on day one. Start with:
 
@@ -281,7 +340,7 @@ Vault **prepare** tools return unsigned steps only. Signing and broadcasting sta
 | Startup error about missing credentials | Neither key nor Bearer set | Set `AUREON_API_KEY` in the host `env` block |
 | `401` / unauthorized on tools | Bad, paused, or revoked key | Create a new issued key; update config |
 | `npx` hangs or fails | Network / registry issue | Retry; ensure Node 20+; try `npm view @buildaureon/mcp version` |
-| Tools listed but every call fails | Wrong URL / mixed network | Omit `AUREON_API_URL` for the official API, or set `AUREON_NETWORK=mainnet` for chain 4663 |
+| Tools listed but every call fails | Wrong URL / mixed network | Omit `AUREON_API_URL` for the official API, or set `AUREON_NETWORK=testnet` to stay on testnet |
 | `aureon_me` shows unexpected wallet | Bearer also set and winning | Clear `AUREON_AUTH_TOKEN` / logout; prefer key-only — see [./auth.md](./auth.md) |
 | Local `node dist/index.js` fails | Missing build | Run `pnpm build` so `dist/index.js` exists |
 | Deposit / withdraw “not signed” | Expected | MCP returns unsigned steps; sign outside MCP |
@@ -295,7 +354,7 @@ Still stuck? Confirm HTTPS reachability to the API, then re-check that the key s
 
 ### Do I need to install the package globally?
 
-No. Prefer `npx -y @buildaureon/mcp` in the host config so the published `v0.1.9` (or newer) is fetched on demand.
+No. Prefer `npx -y @buildaureon/mcp` in the host config so the published `v0.1.10` (or newer) is fetched on demand.
 
 ### Is a Bearer token required?
 
@@ -307,11 +366,11 @@ No. Keep private keys out of MCP. Use them only in a separate signing host when
 
 ### Does MCP talk to a local backend?
 
-Default (omit `AUREON_API_URL`) is the official API `https://api.aureonlabs.network` (currently chain 46630). Set `AUREON_NETWORK=mainnet` to select chain 4663 on that same host.
+Default (omit `AUREON_API_URL`) is the official API `https://api.aureonlabs.network` on mainnet. Set `AUREON_NETWORK=testnet` to stay on testnet on that same host.
 
 ### How is this different from `@buildaureon/sdk`?
 
-The SDK is for typed TypeScript programs. MCP is the same surface as **named tools** for AI hosts over stdio. Both authenticate the same way against the live API.
+The SDK is for typed TypeScript programs. MCP is the same surface as **named tools** for AI hosts. Hosted HTTP and local stdio expose the same 54 tools. Both call the live API. Stdio authenticates with your issued key in host env. Hosted is URL-only for open tools; add `X-Aureon-Api-Key` for your wallet.
 
 ### Where do I rotate a leaked key?
 
@@ -327,9 +386,9 @@ Node.js **20 or newer**. Older runtimes are unsupported.
 
 - [ ] Node 20+ installed (`node -v`)
 - [ ] Issued key created on the Developers page
-- [ ] Host config uses `npx -y @buildaureon/mcp` (or local `node dist/index.js` with a placeholder cwd)
-- [ ] `AUREON_API_KEY` set in host `env` (no private key)
-- [ ] `AUREON_API_URL` omitted (official API). Optional `AUREON_NETWORK=mainnet` for chain 4663
+- [ ] Host config uses `https://mcp.aureonlabs.network/mcp` **or** `npx -y @buildaureon/mcp`
+- [ ] If stdio: `AUREON_API_KEY` set in host `env` (no private key)
+- [ ] If stdio: `AUREON_API_URL` omitted (official API / mainnet). Optional `AUREON_NETWORK=testnet` to stay on testnet
 - [ ] Host restarted; aureon server shows connected
 - [ ] `aureon_ping` succeeds
 - [ ] `aureon_me` returns the expected wallet

package/docs/tools.md

@@ -8,7 +8,9 @@ For request/response shapes, error codes, and HTTP contracts, see the **@buildau
 
 **Tool count:** 54.
 
-**API:** default official API `https://api.aureonlabs.network` (testnet 46630). Optional `AUREON_NETWORK=mainnet` selects chain 4663 on the same host.
+**API:** default official API `https://api.aureonlabs.network` on mainnet. Optional `AUREON_NETWORK=testnet` stays on testnet on the same host.
+
+**Hosted URL:** `aureon_ping`, `aureon_list_market_presets`, and `aureon_validate_receipt` work without a user key. Every other tool needs `X-Aureon-Api-Key` (your issued Developers key) or stdio `AUREON_API_KEY`.
 
 ---
 
@@ -20,19 +22,19 @@ These conventions apply to every tool below.
 | --- | --- |
 | Issued API key | Set `AUREON_API_KEY` to an issued Developers key. That key is product access **and** wallet identity for control-plane calls. |
 | Optional Bearer | You may also supply a wallet Bearer (`AUREON_AUTH_TOKEN` or `aureon_verify_wallet`). If both key and Bearer are present, Bearer wins. |
-| Default network | Official API / testnet 46630. Optional `AUREON_NETWORK=mainnet` for chain 4663. |
+| Default network | Official API / mainnet. Optional `AUREON_NETWORK=testnet` to stay on testnet. |
 | Private key outside MCP | Deposit and withdraw **prepare** tools return unsigned steps. Signing and broadcast happen in the host wallet — never inside the MCP process. |
 | Default automation | `aureon_create_objective` defaults `automationMode` to `"auto"`. |
 | Locked at create | `targetSymbol` and `automationMode` are immutable after create. Recreate the objective to change them. |
 | Unsigned prepare | `aureon_prepare_vault_deposit` and `aureon_prepare_vault_withdraw` never broadcast. |
 | Settlement honesty | Restore / execution receipts may show `settlement: "vault"` (on-chain) or `"staged"` (ledger-local). Label them honestly. |
 
-The catalog includes `aureon_dev_login` for preview APIs only. On hosted APIs it fails by design — agents should use an issued key (or optional Bearer) instead. The public host is still testnet 46630, not 4663.
+The catalog includes `aureon_dev_login` for preview APIs only. On hosted APIs it fails by design — agents should use an issued key (or optional Bearer) instead. Public Living Capital is still the testnet console.
 
 ### Auth bootstrap (agents)
 
 1. Create an issued key in the operator utility **Developers** console.
-2. Configure the MCP host with `AUREON_API_KEY`. Omit `AUREON_API_URL` to use the official API. Set `AUREON_NETWORK=mainnet` only for chain 4663.
+2. Configure the MCP host with `AUREON_API_KEY`. Omit `AUREON_API_URL` to use the official API (mainnet). Set `AUREON_NETWORK=testnet` only to stay on testnet.
 3. Call tools. Day-to-day agent work does **not** require a wallet handshake.
 
 Optional wallet path: `aureon_get_auth_nonce` → host signs → `aureon_verify_wallet`. Prefer issued keys for always-on agents.
@@ -85,7 +87,7 @@ Successful calls return structured JSON (formatted for agents). Failures return
 
 **When to use:** Optional wallet handshake only. Issued API keys usually skip this path.
 
-**Caveats:** The message must be signed by the matching wallet. Early-access wallets may still need an invite on verify.
+**Caveats:** The message must be signed by the matching wallet. `inviteCode` is only if the API asks for it on this optional Bearer path. Hosted MCP and issued-key stdio do not use this tool.
 
 ### `aureon_verify_wallet`
 
@@ -748,7 +750,7 @@ Successful calls return structured JSON (formatted for agents). Failures return
 - [Agent guide](./agent-guide.md) — read → decide → act playbooks
 - [Auth](./auth.md) — issued key, optional Bearer, private-key boundary
 - [Setup](./setup.md) — host configuration for Cursor / Claude Desktop
-- [Security](./security.md) — stdio trust boundary and key hygiene
+- [Security](./security.md) — hosted HTTP and stdio trust boundary and key hygiene
 - **@buildaureon/sdk documentation** — typed client methods, data contracts, error model
 
 ---

package/examples/cursor.hosted.mcp.json

@@ -0,0 +1,7 @@
+{
+  "mcpServers": {
+    "aureon": {
+      "url": "https://mcp.aureonlabs.network/mcp"
+    }
+  }
+}

package/examples/cursor.hosted.user.mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "aureon": {
+      "url": "https://mcp.aureonlabs.network/mcp",
+      "headers": {
+        "X-Aureon-Api-Key": "<your-issued-developer-api-key>"
+      }
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@buildaureon/mcp",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "MCP server for AUREON Financial Compass: Financial Compass capital context for AI agents",
   "type": "module",
   "main": "./dist/index.js",
@@ -44,7 +44,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
     "zod": "^3.25.67",
-    "@buildaureon/sdk": "0.1.9"
+    "@buildaureon/sdk": "0.1.10"
   },
   "devDependencies": {
     "@types/node": "^22.13.10",