exfer-mcp 0.1.0__tar.gz

exfer_mcp-0.1.0/.gitignore

@@ -0,0 +1,31 @@
+# Python build artifacts
+__pycache__/
+*.py[cod]
+*$py.class
+build/
+dist/
+*.egg-info/
+
+# venvs
+.venv/
+venv/
+env/
+
+# tooling caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# editor
+.vscode/
+.idea/
+*.swp
+
+# uv lock — opt-in
+uv.lock
+
+# assistant runtime state
+.claude/
+.gstack/

exfer_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+## 0.1.0
+
+Initial release. Seven tools wrapping the `exfer-walletd` v1.9 Read +
+Spend surface (via `exfer-walletd>=0.8.0`):
+
+- `exfer_generate_address`
+- `exfer_get_balance`
+- `exfer_simulate_transfer`
+- `exfer_transfer`
+- `exfer_wait_for_tx`
+- `exfer_payment_uri_encode`
+- `exfer_payment_uri_decode`
+
+stdio transport. Auth via `WALLETD_URL` + `WALLETD_AUTH_TOKEN` env
+vars; optional TLS pinning via `WALLETD_FINGERPRINT`. Errors from
+walletd (insufficient balance, wait-timeout, indexer-not-configured)
+surface as MCP `isError=true` content with one-line plain-English
+summaries so the agent can react instead of crashing the conversation.

exfer_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Exfer community contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

exfer_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.4
+Name: exfer-mcp
+Version: 0.1.0
+Summary: Model Context Protocol server for the Exfer blockchain — gives an AI agent direct, typed access to an exfer-walletd hot wallet
+Project-URL: Homepage, https://github.com/exfer-stack/exfer-mcp
+Project-URL: Repository, https://github.com/exfer-stack/exfer-mcp
+Project-URL: Bug Tracker, https://github.com/exfer-stack/exfer-mcp/issues
+Project-URL: exfer-walletd (Rust daemon), https://github.com/exfer-stack/exfer-walletd
+Project-URL: exfer-walletd (Python SDK), https://github.com/exfer-stack/exfer-py
+Author: exfer-stack
+License: MIT
+License-File: LICENSE
+Keywords: agent,crypto,exfer,mcp,wallet
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: <3.14,>=3.10
+Requires-Dist: exfer-walletd<1.0,>=0.8.0
+Requires-Dist: mcp<2.0,>=1.0
+Provides-Extra: dev
+Requires-Dist: mypy<2.0,>=1.10; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: respx>=0.21; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# exfer-mcp
+
+Model Context Protocol server for the [Exfer](https://github.com/ahuman-exfer/exfer) blockchain. Gives an AI agent (Claude Desktop, Claude Code, any MCP-aware host) typed, direct access to an [`exfer-walletd`](https://github.com/exfer-stack/exfer-walletd) hot wallet.
+
+> ⚠️ **This is a hot wallet.** Anything that can talk to this MCP server can spend funds — there are no per-period caps, no human-approval gates, no rate limits beyond walletd's own. Until walletd ships the v1.10 allowance ledger, run `exfer-mcp` only against accounts you would be okay losing in full.
+
+## What it exposes
+
+Seven v0.1 tools — enough for the "Hello World agent flow" of generating an address, simulating a transfer, sending it, and waiting for confirmation:
+
+| Tool | What it does |
+|---|---|
+| `exfer_generate_address` | Create a new managed wallet address |
+| `exfer_get_balance` | Confirmed balance of a managed address |
+| `exfer_simulate_transfer` | Dry-run a payment — exact fee + inputs, no broadcast |
+| `exfer_transfer` | Build, sign, broadcast a payment |
+| `exfer_wait_for_tx` | Block until a tx reaches a confirmation depth |
+| `exfer_payment_uri_encode` | Build a BIP21-style `exfer:` URI |
+| `exfer_payment_uri_decode` | Parse a BIP21-style `exfer:` URI |
+
+HTLC swap tools, attestation / reputation lookups, and `htlc_list` are out of v0.1 scope — tracked for v0.2.
+
+## Install
+
+### Recommended — `uvx` (zero global install)
+
+`uvx` runs the server in an isolated, on-demand environment. No `pip install`, no virtual-env management, no PATH wrestling. The host (Claude Desktop / Claude Code / Cursor / …) spawns it on demand and uv handles the rest.
+
+Install `uv` once:
+
+```bash
+# macOS / Linux
+curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+```
+
+Then wire `uvx exfer-mcp` into your MCP host config — examples below. The first time the host launches the server, uv fetches the package from PyPI; subsequent runs are cached.
+
+### Fallback — `pip install`
+
+For developer / CI use, or environments where adding `uv` is awkward:
+
+```bash
+pip install exfer-mcp        # installs the `exfer-mcp` console script
+```
+
+Requires Python ≥ 3.10. Pulls `exfer-walletd ≥ 0.8.0` (the JSON-RPC client) and `mcp ≥ 1.0` (the MCP server framework).
+
+## Configure (Claude Desktop)
+
+Edit `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS (or the equivalent path on your OS), then restart Claude Desktop:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "http://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<paste your walletd token here>"
+      }
+    }
+  }
+}
+```
+
+The token is whatever `exfer-walletd` was started with — by default it's written to `~/.exfer-walletd/token` on first run (`chmod 0600`).
+
+If walletd is running with `--tls` and a self-signed cert, pin its fingerprint:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "https://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<token>",
+        "WALLETD_FINGERPRINT": "sha256:<paste from cert.fingerprint>"
+      }
+    }
+  }
+}
+```
+
+For a publicly-fronted walletd (e.g. behind a reverse proxy with a CA-signed cert), drop the `WALLETD_FINGERPRINT` field — the SDK falls back to the system CA chain.
+
+### Pin a specific version
+
+```json
+"args": ["exfer-mcp@0.1.0"]
+```
+
+## Configure (Claude Code)
+
+One-shot via `claude mcp add`:
+
+```bash
+claude mcp add exfer \
+  -e WALLETD_URL=http://127.0.0.1:7448 \
+  -e WALLETD_AUTH_TOKEN=<token> \
+  -- uvx exfer-mcp
+```
+
+Or by editing the project / global Claude Code MCP config directly:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "http://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<token>"
+      }
+    }
+  }
+}
+```
+
+## Configure (other MCP hosts)
+
+Cursor, Cline, Continue.dev, and most other MCP-aware hosts accept the same `command` / `args` / `env` shape. Use the `uvx exfer-mcp` invocation above.
+
+## Environment
+
+| Variable | Required | Default | Meaning |
+|---|---|---|---|
+| `WALLETD_URL` | ✓ | — | walletd base URL |
+| `WALLETD_AUTH_TOKEN` | ✓ | — | walletd bearer token |
+| `WALLETD_FINGERPRINT` | only for `https://` with a self-signed cert | — | SHA-256 of walletd's TLS cert (`sha256:<hex>`) |
+| `EXFER_MCP_DEFAULT_FEE_RATE` | | walletd default | fee_rate (exfers/byte) for spends when the agent didn't specify |
+| `EXFER_MCP_HTTPX_TIMEOUT` | | 30 | per-RPC timeout in seconds |
+
+## Recommended agent flow
+
+When the user asks the agent to send a payment, the expected sequence is:
+
+1. `exfer_simulate_transfer` → compute exact fee
+2. Show the user the fee and ask for confirmation
+3. `exfer_transfer` → broadcast
+4. `exfer_wait_for_tx` → confirm
+
+The simulate-first pattern means the agent always knows the cost before committing. The user is the one who decides whether the cost is acceptable.
+
+## Safety
+
+- `WALLETD_AUTH_TOKEN` is **all-or-nothing access to the wallet**. Treat it like a payment-card number.
+- `exfer-mcp` does no per-call confirmation by itself — that's the host's job. If you need spend caps, configure them on the walletd side (planned for v1.10) or run a walletd that only holds a small float you would be comfortable losing.
+- The MCP transport is stdio. The agent does not see the wire token; only this process does.
+- Errors from walletd surface as MCP `isError=true` content the agent reads and reacts to, including specific cases like `InsufficientBalanceError` (over-spend) and `WaitTimeoutError` (confirmation depth not reached in time).
+
+## Coming soon
+
+- **`.mcpb` desktop bundle** — Anthropic's one-click `.mcpb` install format for Claude Desktop, with the env vars surfaced as a form at install time.
+- **v0.2 tools** — HTLC trio (`exfer_htlc_lock` / `exfer_htlc_claim` / `exfer_htlc_reclaim`), `exfer_htlc_status`, attestation queries (`exfer_get_attestation_edges`).
+- **MCP directory** — submission to Anthropic's curated MCP directory + community directories.
+
+## Development
+
+```bash
+git clone https://github.com/exfer-stack/exfer-mcp
+cd exfer-mcp
+uv venv && source .venv/bin/activate
+uv pip install -e '.[dev]'
+pytest                          # unit tests
+mypy && ruff check               # lint
+python -m scripts.e2e_smoke      # end-to-end smoke (needs a live walletd)
+```
+
+See [`scripts/e2e_smoke.py`](scripts/e2e_smoke.py) for a runnable example that exercises the full Exfer stack — walletd, indexer, MCP — against a real deployment.
+
+## License
+
+MIT

exfer_mcp-0.1.0/README.md

@@ -0,0 +1,180 @@
+# exfer-mcp
+
+Model Context Protocol server for the [Exfer](https://github.com/ahuman-exfer/exfer) blockchain. Gives an AI agent (Claude Desktop, Claude Code, any MCP-aware host) typed, direct access to an [`exfer-walletd`](https://github.com/exfer-stack/exfer-walletd) hot wallet.
+
+> ⚠️ **This is a hot wallet.** Anything that can talk to this MCP server can spend funds — there are no per-period caps, no human-approval gates, no rate limits beyond walletd's own. Until walletd ships the v1.10 allowance ledger, run `exfer-mcp` only against accounts you would be okay losing in full.
+
+## What it exposes
+
+Seven v0.1 tools — enough for the "Hello World agent flow" of generating an address, simulating a transfer, sending it, and waiting for confirmation:
+
+| Tool | What it does |
+|---|---|
+| `exfer_generate_address` | Create a new managed wallet address |
+| `exfer_get_balance` | Confirmed balance of a managed address |
+| `exfer_simulate_transfer` | Dry-run a payment — exact fee + inputs, no broadcast |
+| `exfer_transfer` | Build, sign, broadcast a payment |
+| `exfer_wait_for_tx` | Block until a tx reaches a confirmation depth |
+| `exfer_payment_uri_encode` | Build a BIP21-style `exfer:` URI |
+| `exfer_payment_uri_decode` | Parse a BIP21-style `exfer:` URI |
+
+HTLC swap tools, attestation / reputation lookups, and `htlc_list` are out of v0.1 scope — tracked for v0.2.
+
+## Install
+
+### Recommended — `uvx` (zero global install)
+
+`uvx` runs the server in an isolated, on-demand environment. No `pip install`, no virtual-env management, no PATH wrestling. The host (Claude Desktop / Claude Code / Cursor / …) spawns it on demand and uv handles the rest.
+
+Install `uv` once:
+
+```bash
+# macOS / Linux
+curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
+```
+
+Then wire `uvx exfer-mcp` into your MCP host config — examples below. The first time the host launches the server, uv fetches the package from PyPI; subsequent runs are cached.
+
+### Fallback — `pip install`
+
+For developer / CI use, or environments where adding `uv` is awkward:
+
+```bash
+pip install exfer-mcp        # installs the `exfer-mcp` console script
+```
+
+Requires Python ≥ 3.10. Pulls `exfer-walletd ≥ 0.8.0` (the JSON-RPC client) and `mcp ≥ 1.0` (the MCP server framework).
+
+## Configure (Claude Desktop)
+
+Edit `~/Library/Application Support/Claude/claude_desktop_config.json` on macOS (or the equivalent path on your OS), then restart Claude Desktop:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "http://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<paste your walletd token here>"
+      }
+    }
+  }
+}
+```
+
+The token is whatever `exfer-walletd` was started with — by default it's written to `~/.exfer-walletd/token` on first run (`chmod 0600`).
+
+If walletd is running with `--tls` and a self-signed cert, pin its fingerprint:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "https://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<token>",
+        "WALLETD_FINGERPRINT": "sha256:<paste from cert.fingerprint>"
+      }
+    }
+  }
+}
+```
+
+For a publicly-fronted walletd (e.g. behind a reverse proxy with a CA-signed cert), drop the `WALLETD_FINGERPRINT` field — the SDK falls back to the system CA chain.
+
+### Pin a specific version
+
+```json
+"args": ["exfer-mcp@0.1.0"]
+```
+
+## Configure (Claude Code)
+
+One-shot via `claude mcp add`:
+
+```bash
+claude mcp add exfer \
+  -e WALLETD_URL=http://127.0.0.1:7448 \
+  -e WALLETD_AUTH_TOKEN=<token> \
+  -- uvx exfer-mcp
+```
+
+Or by editing the project / global Claude Code MCP config directly:
+
+```json
+{
+  "mcpServers": {
+    "exfer": {
+      "command": "uvx",
+      "args": ["exfer-mcp"],
+      "env": {
+        "WALLETD_URL": "http://127.0.0.1:7448",
+        "WALLETD_AUTH_TOKEN": "<token>"
+      }
+    }
+  }
+}
+```
+
+## Configure (other MCP hosts)
+
+Cursor, Cline, Continue.dev, and most other MCP-aware hosts accept the same `command` / `args` / `env` shape. Use the `uvx exfer-mcp` invocation above.
+
+## Environment
+
+| Variable | Required | Default | Meaning |
+|---|---|---|---|
+| `WALLETD_URL` | ✓ | — | walletd base URL |
+| `WALLETD_AUTH_TOKEN` | ✓ | — | walletd bearer token |
+| `WALLETD_FINGERPRINT` | only for `https://` with a self-signed cert | — | SHA-256 of walletd's TLS cert (`sha256:<hex>`) |
+| `EXFER_MCP_DEFAULT_FEE_RATE` | | walletd default | fee_rate (exfers/byte) for spends when the agent didn't specify |
+| `EXFER_MCP_HTTPX_TIMEOUT` | | 30 | per-RPC timeout in seconds |
+
+## Recommended agent flow
+
+When the user asks the agent to send a payment, the expected sequence is:
+
+1. `exfer_simulate_transfer` → compute exact fee
+2. Show the user the fee and ask for confirmation
+3. `exfer_transfer` → broadcast
+4. `exfer_wait_for_tx` → confirm
+
+The simulate-first pattern means the agent always knows the cost before committing. The user is the one who decides whether the cost is acceptable.
+
+## Safety
+
+- `WALLETD_AUTH_TOKEN` is **all-or-nothing access to the wallet**. Treat it like a payment-card number.
+- `exfer-mcp` does no per-call confirmation by itself — that's the host's job. If you need spend caps, configure them on the walletd side (planned for v1.10) or run a walletd that only holds a small float you would be comfortable losing.
+- The MCP transport is stdio. The agent does not see the wire token; only this process does.
+- Errors from walletd surface as MCP `isError=true` content the agent reads and reacts to, including specific cases like `InsufficientBalanceError` (over-spend) and `WaitTimeoutError` (confirmation depth not reached in time).
+
+## Coming soon
+
+- **`.mcpb` desktop bundle** — Anthropic's one-click `.mcpb` install format for Claude Desktop, with the env vars surfaced as a form at install time.
+- **v0.2 tools** — HTLC trio (`exfer_htlc_lock` / `exfer_htlc_claim` / `exfer_htlc_reclaim`), `exfer_htlc_status`, attestation queries (`exfer_get_attestation_edges`).
+- **MCP directory** — submission to Anthropic's curated MCP directory + community directories.
+
+## Development
+
+```bash
+git clone https://github.com/exfer-stack/exfer-mcp
+cd exfer-mcp
+uv venv && source .venv/bin/activate
+uv pip install -e '.[dev]'
+pytest                          # unit tests
+mypy && ruff check               # lint
+python -m scripts.e2e_smoke      # end-to-end smoke (needs a live walletd)
+```
+
+See [`scripts/e2e_smoke.py`](scripts/e2e_smoke.py) for a runnable example that exercises the full Exfer stack — walletd, indexer, MCP — against a real deployment.
+
+## License
+
+MIT

exfer_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,113 @@
+[build-system]
+requires      = ["hatchling>=1.21"]
+build-backend = "hatchling.build"
+
+[project]
+name            = "exfer-mcp"
+dynamic         = ["version"]
+description     = "Model Context Protocol server for the Exfer blockchain — gives an AI agent direct, typed access to an exfer-walletd hot wallet"
+readme          = "README.md"
+license         = { text = "MIT" }
+requires-python = ">=3.10,<3.14"
+authors         = [{ name = "exfer-stack" }]
+keywords        = ["exfer", "mcp", "agent", "wallet", "crypto"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Typing :: Typed",
+]
+# Pinned to >=0.8 because the v0.1 tool surface uses simulate_transfer +
+# wait_for_tx + payment_uri_* — all walletd v1.9 methods that landed in
+# exfer-walletd 0.8.0. Drop the lower bound only when the MCP tool
+# surface stops using them.
+dependencies = [
+    "exfer-walletd>=0.8.0,<1.0",
+    "mcp>=1.0,<2.0",
+]
+
+[project.scripts]
+# The single entrypoint a Claude Desktop / Claude Code config refers
+# to. The stdio transport is launched here.
+exfer-mcp = "exfer_mcp.server:main"
+
+[project.urls]
+Homepage      = "https://github.com/exfer-stack/exfer-mcp"
+Repository    = "https://github.com/exfer-stack/exfer-mcp"
+"Bug Tracker" = "https://github.com/exfer-stack/exfer-mcp/issues"
+"exfer-walletd (Rust daemon)" = "https://github.com/exfer-stack/exfer-walletd"
+"exfer-walletd (Python SDK)"  = "https://github.com/exfer-stack/exfer-py"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0",
+    "pytest-asyncio>=0.23",
+    "respx>=0.21",
+    "mypy>=1.10,<2.0",
+    "ruff>=0.5",
+]
+
+[tool.hatch.version]
+path = "src/exfer_mcp/_version.py"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/exfer_mcp"]
+
+[tool.hatch.build.targets.sdist]
+include = [
+    "src/exfer_mcp",
+    "tests",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md",
+    "pyproject.toml",
+]
+
+[tool.ruff]
+line-length    = 100
+target-version = "py310"
+src            = ["src", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "SIM", "RUF"]
+ignore = [
+    "E501",
+]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/**" = ["B011"]
+
+[tool.mypy]
+python_version          = "3.10"
+strict                  = true
+warn_unreachable        = true
+disallow_any_unimported = true
+files                   = ["src/exfer_mcp"]
+
+[[tool.mypy.overrides]]
+module                 = ["respx"]
+ignore_missing_imports = true
+
+# The `mcp` SDK's `Server.list_tools()` / `Server.call_tool()` decorators
+# are not typed in the upstream package. We can't make them strict without
+# stubs; silence the two specific codes they emit so we don't slacken
+# strict-mode elsewhere.
+[[tool.mypy.overrides]]
+module                = ["exfer_mcp.server"]
+disable_error_code    = ["no-untyped-call", "misc", "untyped-decorator"]
+
+[tool.pytest.ini_options]
+testpaths    = ["tests"]
+pythonpath   = ["src"]
+asyncio_mode = "auto"
+
+[tool.uv.sources]
+# Local-checkout override while the matching `exfer-walletd` 0.8.0
+# isn't on PyPI yet. When the wheel ships, drop this section and the
+# normal PyPI resolver will take over.
+exfer-walletd = { path = "../exfer-py", editable = true }

exfer_mcp-0.1.0/src/exfer_mcp/__init__.py

@@ -0,0 +1,24 @@
+"""Model Context Protocol server for the Exfer blockchain.
+
+Wraps an ``exfer-walletd`` daemon as a set of MCP tools so an AI agent
+(Claude Desktop, Claude Code, any MCP-aware host) can transact on the
+Exfer chain directly — generate addresses, simulate transfers, send
+payments, wait for confirmation, build payment URIs.
+
+The transport is stdio; the agent host spawns this process as a
+subprocess and speaks JSON-RPC over its stdin / stdout. See the README
+for the exact host-config stanza.
+
+.. warning::
+
+   This is a hot wallet. Anything that can talk to this MCP server can
+   spend funds from the wired ``WALLETD_AUTH_TOKEN``. Run only against
+   accounts you would be okay losing in full until walletd ships
+   per-period allowance caps (tracked at exfer-walletd v1.10).
+"""
+
+from __future__ import annotations
+
+from ._version import __version__
+
+__all__ = ["__version__"]

exfer_mcp-0.1.0/src/exfer_mcp/_version.py

@@ -0,0 +1 @@
+__version__ = "0.1.0"