antd-mcp 0.1.0__tar.gz

antd_mcp-0.1.0/.gitignore

@@ -0,0 +1,100 @@
+# Rust
+target/
+target-dev/
+**/*.rs.bk
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+*.egg
+.venv/
+venv/
+
+# Node.js
+node_modules/
+
+# C# / .NET
+bin/
+obj/
+*.user
+*.suo
+*.csproj.user
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Dart
+.dart_tool/
+pubspec.lock
+
+# PHP
+vendor/
+composer.lock
+composer-setup.php
+composer.phar
+
+# Elixir
+_build/
+deps/
+.elixir_ls/
+mix.lock
+# antd-elixir is a library but commits its lock: CI and dev resolve the same tree
+!antd-elixir/mix.lock
+
+# Zig
+.zig-cache/
+zig-out/
+
+# C++ CMake
+build/
+CMakeCache.txt
+CMakeFiles/
+
+# Ruby
+Gemfile.lock
+.bundle/
+
+# Java
+out/
+.gradle/
+*.class
+
+# Claude
+.claude/
+
+# Lua
+.luarocks/
+
+# ant-dev state
+.ant-dev/
+
+# Logs
+*.log
+
+# Sweep script output dirs (scripts/full-stack-sweep.sh, scripts/integration-sweep.sh)
+.full-stack-sweep-results/
+.integration-results/
+
+# built gems (publish-ruby.yml builds them in CI)
+*.gem
+
+# ffi/scripts/build-native-manylinux.sh output (per-arch libant_ffi.so for packaging)
+ffi/rust/native-out/
+
+# Third-party notices generated by scripts/third_party_notices/generate.py;
+# the release workflow builds them.
+/THIRD-PARTY-NOTICES*.txt
+/RUST-STD-COPYRIGHT*.html
+/antd/*.THIRD-PARTY-NOTICES.txt
+/antd/*.RUST-STD-COPYRIGHT.html

antd_mcp-0.1.0/LICENSE-APACHE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Support. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a
+      fee for, acceptance of support, warranty, indemnity, or other
+      liability obligations and/or rights consistent with this License.
+      However, in accepting such obligations, You may act only on Your
+      own behalf and on Your sole responsibility, not on behalf of any
+      other Contributor, and only if You agree to indemnify, defend, and
+      hold each Contributor harmless for any liability incurred by, or
+      claims asserted against, such Contributor by reason of your accepting
+      any such warranty or support.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Autonomi
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

antd_mcp-0.1.0/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Autonomi
+
+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.

antd_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,311 @@
+Metadata-Version: 2.5
+Name: antd-mcp
+Version: 0.1.0
+Summary: MCP server that lets AI agents store and fetch data on the Autonomi network through the antd daemon
+Project-URL: Homepage, https://autonomi.com
+Project-URL: Repository, https://github.com/WithAutonomi/ant-sdk
+Project-URL: Documentation, https://github.com/WithAutonomi/ant-sdk/tree/main/antd-mcp#readme
+Project-URL: Issues, https://github.com/WithAutonomi/ant-sdk/issues
+Project-URL: Changelog, https://github.com/WithAutonomi/ant-sdk/releases
+Author: Autonomi
+License-Expression: MIT OR Apache-2.0
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+Keywords: ai-agents,antd,autonomi,decentralized,mcp,model-context-protocol,storage
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+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: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Distributed Computing
+Requires-Python: >=3.10
+Requires-Dist: antd[rest]<0.5,>=0.4.0
+Requires-Dist: anyio>=4
+Requires-Dist: mcp<3,>=2
+Provides-Extra: test
+Requires-Dist: pytest-asyncio>=0.23; extra == 'test'
+Requires-Dist: pytest>=7.0; extra == 'test'
+Description-Content-Type: text/markdown
+
+# antd-mcp — MCP Server for Autonomi
+
+An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that exposes the Autonomi network as 31 tools for AI agents (19 storage tools, 10 pointer tools, and the 2 manifest tools when the installed SDK supports them). Works with Claude Desktop, Claude Code, and any MCP-compatible client.
+
+## Installation
+
+```bash
+# Run without installing (recommended for MCP client configs)
+uvx antd-mcp
+
+# Or install as a tool
+pipx install antd-mcp
+
+# Or into an environment
+pip install antd-mcp
+```
+
+Python 3.10+. Pulls in the [`antd`](https://pypi.org/project/antd/) Python SDK (REST transport) automatically. Needs a running [antd](https://github.com/WithAutonomi/ant-sdk/tree/main/antd) daemon: see [Get the antd daemon](#get-the-antd-daemon). antd 0.17.0 or later supports every tool.
+
+From a source checkout: `pip install -e antd-mcp/`.
+
+Add it to Claude Code in one line:
+
+```bash
+claude mcp add antd-autonomi -- uvx antd-mcp
+```
+
+## Get the antd daemon
+
+antd-mcp reaches the Autonomi network through antd, a daemon that runs on the same computer. antd-mcp does not install or start it. Without one, every tool returns a `DAEMON_NOT_RUNNING` error that links here. Some clients also offer to open this page, once per session: those that support MCP URL-mode elicitation on a protocol before 2026-07-28. From 2026-07-28 a server can't prompt mid-call, so those clients, like any others, get the link as `help_url` in the error.
+
+The easiest way to get antd is an installer from the [latest ant-sdk release](https://github.com/WithAutonomi/ant-sdk/releases/latest):
+
+| OS | Download |
+|----|----------|
+| Windows (x64) | `antd-windows-x64-setup.msi` |
+| macOS (Apple silicon) | `antd-macos.pkg` |
+| Linux (x64) | `antd-linux-x64.deb` or `antd-linux-x64.rpm` |
+| Linux (x64 or arm64) | `antd-linux-install.sh` |
+
+The installer starts antd straight away, and again each time you log in. antd listens on `127.0.0.1:8082` and writes the `daemon.port` file, so antd-mcp finds it with no configuration. Ask the agent to try again once antd is running.
+
+You can also download the plain binary from the same release (`antd-windows-amd64.exe`, `antd-darwin-arm64`, `antd-linux-amd64`, `antd-linux-arm64`). Check it against `SHA256SUMS`, then run `antd`.
+
+Reading data needs no wallet. Storing data is paid for from the daemon's wallet; see [Wallet & EVM Configuration](https://github.com/WithAutonomi/ant-sdk/tree/main/antd#wallet--evm-configuration).
+
+To check that the daemon is up, call the `check_health` tool, or run `curl http://127.0.0.1:8082/health`.
+
+## Running
+
+```bash
+# stdio transport (default — for Claude Desktop)
+antd-mcp
+
+# Streamable HTTP transport (for web-based clients; the current MCP HTTP transport)
+antd-mcp --http
+
+# Legacy SSE transport
+antd-mcp --sse
+```
+
+### Environment Variables
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `ANTD_BASE_URL` | auto-discovered | antd daemon URL (overrides port-file discovery) |
+
+The MCP server automatically discovers the antd daemon via the `daemon.port` file written by antd on startup. Set `ANTD_BASE_URL` only if you need to override this (e.g. connecting to a remote daemon). If neither the env var nor port file is available, falls back to `http://127.0.0.1:8082`.
+
+## Claude Desktop Configuration
+
+Add to your Claude Desktop config (`claude_desktop_config.json`):
+
+```json
+{
+  "mcpServers": {
+    "antd-autonomi": {
+      "command": "uvx",
+      "args": ["antd-mcp"]
+    }
+  }
+}
+```
+
+The server will auto-discover the daemon via the port file. Add `"env": {"ANTD_BASE_URL": "http://your-host:port"}` only if you need to override discovery.
+
+## Tool Reference
+
+### Data Operations
+
+| # | Tool | Description |
+|---|------|-------------|
+| 1 | `store_data(text, private?, payment_mode?)` | Store text on the network. With `private=True`, the returned `address` is the caller-held DataMap (not stored on-network — keep it safe). Also returns `sha256`, the plaintext's SHA-256 (hex); requires antd 0.17.0 or later, `null` on older daemons. |
+| 2 | `retrieve_data(address, private?)` | Retrieve text by address. Pass `private=True` if `address` is a caller-held DataMap from a private store. |
+| 3 | `upload_file(path, private?, payment_mode?)` | Upload a local file. With `private=True`, the returned `address` is the caller-held DataMap. Also returns `sha256`, the plaintext's SHA-256 (hex); requires antd 0.17.0 or later, `null` on older daemons. |
+| 4 | `download_file(address, dest_path, private?)` | Download to local path — the **daemon** writes the file (daemon and MCP server must share a filesystem). Pass `private=True` if `address` is a caller-held DataMap from a private upload. |
+| 5 | `stream_download_file(address, dest_path, private?)` | Like `download_file`, but streams the bytes back to the MCP server process and writes `dest_path` on **this** host with constant memory (suits large objects / no shared filesystem). Returns `bytes_written`. |
+| 6 | `get_cost(text?, file_path?, payment_mode?)` | Estimate storage cost — returns `cost`, `file_size`, `chunk_count`, `estimated_gas_cost_wei`, `payment_mode` |
+| 7 | `check_health()` | Check daemon health and network status |
+
+### Wallet Operations
+
+| # | Tool | Description |
+|---|------|-------------|
+| 8 | `wallet_address()` | Get wallet public address |
+| 9 | `wallet_balance()` | Get wallet token and gas balances |
+| 10 | `wallet_approve()` | Approve wallet to spend tokens on payment contracts (one-time) |
+
+### Chunk Operations
+
+| # | Tool | Description |
+|---|------|-------------|
+| 11 | `chunk_put(data)` | Store a raw chunk (base64 input) |
+| 12 | `chunk_get(address)` | Retrieve a chunk (base64 output) |
+
+### External Signer (Two-Phase Upload)
+
+| # | Tool | Description |
+|---|------|-------------|
+| 13 | `prepare_upload(path, visibility?)` | Prepare a file upload for external signing. Pass `visibility="public"` to bundle the DataMap chunk into the same payment batch (the `data_map_address` on finalize is the shareable retrieval handle). |
+| 14 | `prepare_upload_public(path)` | Convenience wrapper for `prepare_upload(path, visibility="public")`. |
+| 15 | `prepare_data_upload(text)` | Prepare a data upload for external signing |
+| 16 | `finalize_upload(upload_id, tx_hashes)` | Finalize a wave-batch upload. Returns `address`, `chunks_stored`, `data_map`, and (for public uploads) `data_map_address`, plus `sha256`, the plaintext's SHA-256 (hex); requires antd 0.17.0 or later, `null` on older daemons. A partial store returns a `PARTIAL_UPLOAD` error (see [Partial uploads](#partial-uploads)). |
+| 17 | `finalize_merkle_upload(upload_id, winner_pool_hash)` | Finalize a merkle-batch upload. Returns the same fields as `finalize_upload` (including `sha256`); same `PARTIAL_UPLOAD` behaviour. |
+| 18 | `prepare_chunk_upload(data_base64)` | Prepare a single raw chunk for external-signer publish. Returns either `already_stored=True` (no payment needed) or a wave-batch payment intent. |
+| 19 | `finalize_chunk_upload(upload_id, tx_hashes)` | Submit a prepared chunk to the network after external payment. Returns `address`. |
+
+### Pointers
+
+A pointer is a small, owner-signed, mutable reference: its address never changes, and its owner can move its target (a chunk, such as a public `store_data` / `upload_file` address, or another pointer). The daemon holds the owner keys (`antd --pointer-keys`), so every write names the pointer by its address (`owner`). See [Pointer payments, counters and errors](#pointer-payments-counters-and-errors) before using the write tools.
+
+| # | Tool | Description |
+|---|------|-------------|
+| 20 | `pointer_keys()` | List the pointer addresses this daemon holds owner keys for, so can write. Free. |
+| 21 | `pointer_get(address, include_owner_key?)` | Read a pointer: `counter` (decimal string), `target`, `kind` / `kind_tag`, `state_id`, `is_final`, `transferred_to`. The owner's ML-DSA-65 public key (~3,900 hex chars) only with `include_owner_key=True`. Free. |
+| 22 | `pointer_resolve(address)` | Follow forwardings and transfers to the target at the end of the chain: `target`, `kind`, `kind_tag`. Free. |
+| 23 | `pointer_finality(address)` | Ask the whole close group where a pointer stands: `status` is `open`, `settling`, `unconfirmed`, `final`, `forked`, or `unknown` (daemon string in `raw_status`). Only `final` means a transfer is beyond dispute. Free. |
+| 24 | `pointer_controller(address)` | Follow transfers to the pointer whose owner now decides: `pointer`, `transfers`, `frozen`. Free. |
+| 25 | `pointer_create(owner, target, kind?)` | Create a pointer (`kind` `"chunk"`, the default, or `"pointer"`). **Pays** from the daemon wallet. `ALREADY_EXISTS` if it exists, refused before paying. |
+| 26 | `pointer_update(owner, target, kind?)` | Point a pointer at a new target; creates it if missing. **Pays** from the daemon wallet. `POINTER_FINAL` once transferred or frozen, usually refused before paying. |
+| 27 | `pointer_transfer(owner, recipient, confirm_irreversible?)` | **Irreversible.** Hand the pointer over to the recipient's pointer for good: it becomes final and its readers are sent on to the recipient. **Pays** from the daemon wallet. Refuses with `CONFIRMATION_REQUIRED`, sending nothing, unless `confirm_irreversible=true`. Returns the close group's `finality`. |
+| 28 | `pointer_prepare(owner, op, target?, kind?, recipient?)` | External signer: the daemon signs `op` (`"create"` / `"update"` with `target`, or `"transfer"` with `recipient`) and quotes it. Returns `upload_id`, `counter` and wave-batch `payments`. Pays nothing itself; other writes to the pointer get `CONFLICT` until it is finalized or expires (one hour). |
+| 29 | `pointer_finalize(upload_id, tx_hashes)` | External signer: store the prepared write after `payForQuotes()`. Returns `counter`, and `finality` for a transfer. |
+
+### Manifests
+
+A manifest (a `.ant` file, or an `ant://manifest/` link to one) bundles files that are already on the network, each with an optional relative path. The `link` is what you share. Both tools are **free**: nothing is uploaded and nothing is paid, so neither asks for confirmation. They are annotated read-only. Upload the files first (`store_data`, `upload_file`) and pass the `address` (public) or `data_map` (private, embedded in the manifest) they returned.
+
+| # | Tool | Description |
+|---|------|-------------|
+| 30 | `build_manifest(entries, name?, torrent_info_hashes?, embed_roots?)` | Each entry is `{path?, size?, sha256?, data_map? \| address?}`: give exactly one of `data_map` or `address`. `sha256` is the file's plaintext SHA-256 (hex) to record; requires antd 0.17.0 or later; it is passed through as given and the daemon rejects a malformed one with `BAD_REQUEST`. Returns `manifest_base64` (the `.ant` bytes), `link` (null when the manifest exceeds 1,500 bytes; share the file instead) and `entries` (each with `sha256`, the hash the manifest records or `null`; requires antd 0.17.0 or later). `embed_roots` defaults to true. A bad entry returns `BAD_REQUEST` with a message naming `entries[i]`. |
+| 31 | `decode_manifest(manifest_base64? \| link?, resolve?)` | Give exactly one of the base64 `.ant` bytes or a `link` (manifest link, file link or bare address). Returns `source` (`manifest` or `file_link`), `name`, the torrent hashes and `entries` (each with `sha256`, the hash the manifest records or `null`; requires antd 0.17.0 or later). With `resolve=true` it also reads each entry's root from the network to fill in `exact_size`; one entry's failure is in its `error`, not a failed call. |
+
+Unset sizes and unset `sha256` values are `null`, never 0 or an empty string. These tools need an antd daemon with the manifest API (antd 0.16.0 or later) and an [`antd`](https://pypi.org/project/antd/) Python SDK that has `build_manifest`. With an older SDK the server still starts and serves its other tools; it just does not register the manifest tools.
+
+### Payment Modes
+
+The `store_data`, `upload_file`, and `get_cost` tools accept an optional `payment_mode` parameter:
+
+| Mode | Behavior |
+|------|----------|
+| `"auto"` (default) | Uses merkle batch payments for 64+ chunks, single payments otherwise. Recommended for most use cases. |
+| `"merkle"` | Forces merkle batch payments regardless of chunk count (minimum 2 chunks). Saves gas on larger uploads. |
+| `"single"` | Forces per-chunk payments. Useful for small data or debugging. |
+
+## Response Format
+
+All tools return JSON with a `network` field indicating the connected network:
+
+```json
+{
+  "address": "abc123...",
+  "cost": "1000000",
+  "network": "local"
+}
+```
+
+Errors return structured error objects:
+
+```json
+{
+  "error": "NOT_FOUND",
+  "message": "Resource not found",
+  "status_code": 404,
+  "network": "local"
+}
+```
+
+When no daemon answers, the error is `DAEMON_NOT_RUNNING`. Its `message` says which address was tried and where that address came from (`ANTD_BASE_URL`, the `daemon.port` file, or the default). It also carries a `hint` and a `help_url` pointing to [Get the antd daemon](#get-the-antd-daemon). The address is shown as scheme, host and port only, so credentials in `ANTD_BASE_URL` never appear in errors or logs. That request never reached a daemon. It says nothing about a payment already sent, such as the on-chain payment an external signer makes before `finalize_upload`: keep the `upload_id` and payment details, and reconcile before paying again. Never pay again on this error alone.
+
+The `sha256` fields on upload and manifest results need both an antd daemon 0.17.0 or later and an [`antd`](https://pypi.org/project/antd/) Python SDK 0.4.0 or later. With an older daemon or SDK they are `null`.
+
+### Partial uploads
+
+`finalize_upload` / `finalize_merkle_upload` can fail *after* the payment went through: some chunks store, others miss quorum after the daemon's own retries. The error object then carries the counts and a `retryable` flag so the agent can decide what to do:
+
+```json
+{
+  "error": "PARTIAL_UPLOAD",
+  "message": "Partial upload: 300/312 chunks stored, 12 failed after retries: ...",
+  "status_code": 502,
+  "chunks_stored": 300,
+  "chunks_failed": 12,
+  "total_chunks": 312,
+  "retryable": true,
+  "retention_known": true,
+  "network": "local"
+}
+```
+
+The payment and the stored chunks persist either way.
+
+- **`retryable: true`** — the daemon kept the paid attempt under the same `upload_id` (antd ≥ 0.14.0). Call the **same** finalize tool again with the **same arguments**; it stores the remainder against the same payment — no re-prepare, no second payment. Bound the retries: stop after a few attempts, or when `chunks_failed` stops shrinking. The retained attempt expires with the daemon's pending-upload TTL (one hour).
+- **`retention_known: true`, `retryable: false`** — the daemon confirmed it kept nothing (e.g. a merkle finalize with deliberately unpaid batches). Run the prepare step again for the same content; already-stored chunks are skipped, so only the remainder is paid for.
+- **`retention_known: false`** — retention is unknown. The daemon may still hold the paid attempt: it records the resume handle before it returns the error. Stop automatic recovery, keep the `upload_id` and the payment details you passed, and reconcile before preparing or paying again. Never pay again on this signal alone. Daemons older than 0.14.0 never send `retryable`, so their partial uploads read as unknown.
+
+`retryable: true` always comes with `retention_known: true`.
+
+These fields come from the antd SDK, which reads the daemon's response strictly. A count that is not a non-negative JSON integer (at most 2^64−1) reads as `0`. `retryable` is `true` only when the daemon sent the JSON literal `true`, and `retention_known` is `true` only when `retryable` was a JSON bool. A malformed partial-upload response therefore never shows up as `UNEXPECTED`. It arrives as `PARTIAL_UPLOAD` with the unreadable fields at `0` / `false` (an unreadable `retryable` means retention unknown). If the body is unreadable, or its `code` is not exactly `"PARTIAL_UPLOAD"`, it arrives as a plain `NETWORK_ERROR` without the partial-upload fields.
+
+Full contract: `docs/external-signer-flow.md` §6 in the ant-sdk repo.
+
+### Pointer payments, counters and errors
+
+The pointer tools need an antd daemon with the pointer API and an [`antd`](https://pypi.org/project/antd/) Python SDK 0.3.0 or later. With an older SDK the server still starts and serves the other 19 tools; it just does not register the pointer tools.
+
+**Every write pays, and no tool retries.** `pointer_create`, `pointer_update` and `pointer_transfer` each pay from the daemon wallet, about the price of one chunk, with the same posture as `store_data` / `upload_file` / `chunk_put`: no confirmation step and no automatic retry. Every repeat pays again, so check the pointer (`pointer_get`) before repeating a failed write. The reads are free.
+
+**Transfers are irreversible.** A transfer makes the pointer final forever: nobody, its owner included, can update or transfer it again, and its readers are sent on to the recipient's pointer. On top of the paid-tool posture, `pointer_transfer` refuses to run unless `confirm_irreversible` is `true`. Without it the tool sends and pays nothing and returns:
+
+```json
+{
+  "error": "CONFIRMATION_REQUIRED",
+  "message": "pointer_transfer would hand the pointer <owner> over to <recipient> forever: ... Nothing was sent or paid. Confirm with the user, then call again with confirm_irreversible=true.",
+  "network": "local"
+}
+```
+
+The tool is also annotated `destructiveHint: true`, `idempotentHint: false` for clients that prompt on those hints.
+
+**Counters are decimal strings**, never JSON numbers. A final pointer (transferred or frozen) sits at counter `"18446744073709551615"` (2^64−1), which JSON clients that read numbers as doubles, and LLMs, round. Compare counters as strings of digits or as big integers. An unset counter (finality other than `open`) is `null`.
+
+**Errors.** Four pointer-era codes carry a `hint` saying what to do next:
+
+| `error` | HTTP | Meaning |
+|---------|------|---------|
+| `POINTER_FINAL` | 409 | The pointer is transferred or frozen; nothing can change it. Usually refused before paying, but a write already paid for when the network refused it keeps that payment. Do not retry. |
+| `POINTER_FORKED` | 409 | The owner signed two different final states and no majority holds either. Do not retry. |
+| `CONFLICT` | 409 | A prepared write to the pointer awaits payment (refused before paying), or an update lost to a newer state while in flight (possibly after paying). The `hint` says which; read the pointer before paying for another write. |
+| `CLOSE_GROUP_SHORTFALL` | 503 | Too few of the close group answered or stored. Carries `retryable`. |
+
+`CLOSE_GROUP_SHORTFALL` with `retryable: true` comes only from `pointer_finalize`. It means **retry the finalize, the payment was kept**: call `pointer_finalize` again with the same `upload_id` and the daemon stores the paid state against the same payment, with no second payment. Bound the retries; the kept attempt expires after one hour.
+
+```json
+{
+  "error": "CLOSE_GROUP_SHORTFALL",
+  "message": "Close group shortfall: ... (paid attempt retained: call finalize again with the same upload_id ...)",
+  "status_code": 503,
+  "retryable": true,
+  "hint": "Retry the finalize, the payment was kept: call pointer_finalize again with the same upload_id ...",
+  "network": "local"
+}
+```
+
+With `retryable: false`, a read is free to retry later, but do not repeat a paid write automatically: it may already have been paid for. A create of an existing pointer stays `ALREADY_EXISTS`.
+
+## Project Structure
+
+```
+antd-mcp/
+├── pyproject.toml
+└── src/antd_mcp/
+    ├── __init__.py
+    ├── server.py      # 29 MCP tool definitions
+    ├── discover.py    # Daemon port-file discovery
+    └── errors.py      # Error formatting
+```