boundra-mcp 0.1.0__tar.gz

boundra_mcp-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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 reasonable and customary use in 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 Additional Liability. 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 additional liability.
+
+   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 [yyyy] [name of copyright owner]
+
+   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.

boundra_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,314 @@
+Metadata-Version: 2.4
+Name: boundra-mcp
+Version: 0.1.0
+Summary: Boundra — policy-guarded payment approval gateway for AI agents (MCP server)
+Author: Boundra
+License: Apache-2.0
+Project-URL: Homepage, https://boundra.io
+Project-URL: API, https://api.boundra.io
+Keywords: mcp,agent,payments,x402,policy,guardrails
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: mcp<3,>=2.3
+Requires-Dist: eth-account>=0.13
+Dynamic: license-file
+
+# Boundra · Payment approval gateway for AI agents
+
+<!-- mcp-name: io.github.gobeyondfj-cmd/boundra -->
+
+> **Boundra** (boundra.io) — *Boundaries for agent payments.*
+> The boundary layer for agent payments: before any money moves, answer
+> "should this payment happen at all?"
+
+Our thesis: **the opportunity in agent payments is not "how to pay" (protocols
+solved that) but "whether to pay."**
+
+One natural-language rule → compiled into a policy → every payment the agent
+attempts is genuinely evaluated → allow / ask a human / veto, with a full
+audit trail.
+
+Two run modes:
+
+- **Offline simulation** (`demo.py`): stdlib only, self-contained mock merchant
+  and wallets, zero dependencies, zero network
+- **Real protocol** (`demo/demo_real.py`): standard MCP server + real x402 SDK +
+  Base Sepolia testnet
+
+## Data flow
+
+![Boundra data flow](docs/dataflow.png)
+
+Policies and keys stay with the user; the gateway is read-only; only hash
+commitments go on-chain. Revocation is free — forever, no exceptions.
+
+## See it run in 60 seconds
+
+```bash
+# 1. Hit the hosted evaluation API — a real, public x402 merchant
+curl -X POST https://api.boundra.io/evaluate/basic \
+  -H 'Content-Type: application/json' \
+  -d '{"intent":{"amount":0.01,"recipient":"api.weather.com","purpose":"weather data"}}'
+# → {"decision":"ALLOW",...}  ·  semantic layer: 100 free calls per agent, then $0.003 via x402
+
+# 2. Local end-to-end simulation — a data-procurement agent's day
+.venv/bin/python demo/simulate_agent.py
+# signed policy publish → ALLOW / DENY (limit) / ASK → user-signed approval token
+# → prompt-injection blocked → audit trail, plus a dogfood call to api.boundra.io
+
+# 3. One-line MCP install + 2-minute policy wizard
+uvx --from git+https://github.com/gobeyondfj-cmd/boundra boundra-mcp     # stdio server
+uvx --from git+https://github.com/gobeyondfj-cmd/boundra boundra-init    # wallet → template → sign → anchor
+uvx --from git+https://github.com/gobeyondfj-cmd/boundra boundra-approve # sign an ASK challenge
+```
+
+## The complete flow, step by step
+
+Zero to a signed, enforced policy in ~10 minutes. No accounts, no dashboards —
+your wallet key is your identity.
+
+**0 · Try the hosted API** *(30 seconds, nothing to install)*
+
+```bash
+curl -X POST https://api.boundra.io/evaluate/basic \
+  -H 'Content-Type: application/json' \
+  -d '{"intent":{"amount":0.01,"recipient":"api.weather.com","purpose":"weather data"}}'
+```
+
+**1 · Bind your identity — the wallet is the account**
+
+```bash
+uvx --from git+https://github.com/gobeyondfj-cmd/boundra boundra-init
+```
+
+Creates or imports a Base wallet. No signup, no email — the private key never
+leaves your device, and your address *is* your identity everywhere in the
+system.
+
+**2 · Set your policy**
+
+The wizard offers templates (personal assistant / travel / dev API /
+procurement) or lets you write your own rule in plain English, then compiles
+it and shows you exactly what will be enforced — before anything is signed.
+
+**3 · Sign & publish**
+
+You sign the policy document with your wallet key (EIP-191). It is published
+as a versioned document and a hash commitment is anchored on-chain. From this
+moment the gateway is read-only for every agent — changing the policy without
+your key is impossible.
+
+**4 · Mount the MCP server into your agent**
+
+```json
+{ "mcpServers": { "boundra": { "command": "uvx",
+  "args": ["--from", "git+https://github.com/gobeyondfj-cmd/boundra", "boundra-mcp"] } } }
+```
+
+**5 · Every payment gets a verdict before signing**
+
+Your agent calls `evaluate_payment`; the 5-stage pipeline answers
+**ALLOW** (sign & settle) / **DENY** (aborted pre-signature, zero on-chain
+trace) / **ASK** (a challenge bound to this exact payment).
+
+**6 · When the agent asks, you decide**
+
+```bash
+uvx --from git+https://github.com/gobeyondfj-cmd/boundra boundra-approve
+```
+
+Paste the ASK challenge, sign it on your device — the agent retries with the
+signed approval token. Forged, rebound, or replayed tokens are rejected.
+
+**7 · Watch, update, revoke**
+
+`get_spend_report` / `get_audit_trail` / `get_policy_versions` keep you in
+control day to day. Every policy change is a new signed version
+(`set_policy`); `revoke_policy` is instant default-deny and **free forever**.
+
+## Quick start (from source)
+
+```bash
+cd boundra
+
+# Mode 1: offline simulation (run this first — the full flow in 30 seconds)
+python demo/demo.py
+
+# Mode 2: real x402 + MCP
+python -m venv .venv && .venv/bin/pip install \
+    "x402[evm,httpx]" mcp eth-account fastapi uvicorn
+.venv/bin/python tests/test_mcp_client.py    # MCP protocol-level tests
+.venv/bin/python demo/setup_wallets.py       # generate Base Sepolia test wallets + faucet guide
+.venv/bin/python demo/demo_real.py           # real protocol end-to-end (settles on-chain after funding)
+```
+
+## Architecture: where the gateway stands
+
+```
+Agent framework (Claude / custom)
+   │  MCP protocol (stdio)
+   ▼
+mcp_server.py  ──→  policy.py 5-stage evaluation pipeline
+(policy decision     semantic → whitelist → limit → approval → budget
+ point)
+   ▲
+   │ on_before_payment_creation hook (x402 SDK v2 native interception point)
+x402_buyer.py ──sign (EIP-3009)──→ x402 server ──→ facilitator ──→ Base Sepolia
+```
+
+**Key finding**: x402 SDK v2 natively provides the `on_before_payment_creation`
+hook plus `register_policy` / `set_spend_controls` — the policy layer is not a
+bolt-on; it is the slot the official protocol stack reserves. This validates
+the wedge.
+
+## File map
+
+```
+boundra/
+├── policy.py                 intent compilation (NL→Policy, bilingual CN/EN) + 5-stage pipeline + platform red lines
+├── signed_policy.py          ★ signed policy documents + version chain + revocation (keccak)
+├── approval.py               ★ signed approval tokens (challenge → user signs → gateway verifies)
+├── mandate.py                ★ task Mandates: single-use authorization, burned after use (pipeline layer 4)
+├── templates.py              ★ policy template library (personal assistant / travel / dev API / procurement)
+├── chain_anchor.py           ★ anchor backends: local simulation + real Base Sepolia (web3)
+├── gateway.py                gateway core v3: 4-layer stacking + token verification + Mandate + revocation
+├── rail_adapters.py          ★ rail adapter layer: evaluation core decoupled from settlement rails (x402 first)
+├── mcp_server.py             ★ standard MCP server (11 tools, stdio)
+├── boundra_cli.py            ★ boundra-init (policy wizard) + boundra-approve (challenge signer)
+├── contracts/
+│   └── PolicyAnchor.sol      ★ on-chain commitment contract (owner-write, anyone-read)
+├── demo/
+│   ├── simulate_agent.py     ★ end-to-end user journey simulation (MCP + hosted API dogfood)
+│   ├── demo_policy.py        signed-policy demo (impersonation / unsigned / tampering attacks all blocked)
+│   ├── demo_real.py          real-protocol end-to-end orchestration
+│   ├── x402_resource_server.py  real x402 paywall server (FastAPI middleware)
+│   ├── x402_buyer.py         real x402 buyer, evaluated by the MCP gateway before signing
+│   ├── setup_wallets.py      Base Sepolia test wallet generation
+│   └── demo.py / merchant.py / agent.py   offline simulation (zero dependencies)
+├── tests/
+│   ├── test_product.py       ★ product tests (22 assertions)
+│   └── test_mcp_client.py    MCP protocol-level tests
+├── docs/
+│   ├── dataflow.png          data-flow diagram (English)
+│   └── render_*.py           diagram renderers (architecture / flow / use-case / data flow)
+└── state/audit.jsonl         audit trail (generated at runtime, gitignored)
+```
+
+## Signed policies: the root of trust is the user's key, not the gateway's database (v2)
+
+A policy is a **document signed by the user's wallet**, not a row in the
+gateway's configuration:
+
+```
+user private key signature ──→ PolicyDocument (NL rule + compiled artifact + prev_hash + version)
+                      │  three checks: signer == owner, versions sequential, prev_hash unbroken
+                      ▼
+              PolicyStore (version chain) ──→ LocalAnchor (simulated commitment; production writes to contract)
+                      │
+                      ▼  check_integrity before every evaluation (signature + anchor)
+              5-stage pipeline; audit records cite policy version + hash
+```
+
+- **Read-only for agents**: without the user's private key, `set_policy` always
+  fails — impersonation, unsigned, and tampered submissions are all blocked
+  (seven scenarios in `demo/demo_policy.py`)
+- **Two stacked scopes**: user-level (rules for all agents) × agent-level
+  (per-agent rules); the strictest verdict wins
+- **Every version bump is a signature**: v2 must reference v1's hash; tampering
+  with any historical version → signature invalid + chain broken
+- **Privacy shape**: only hash commitments go on-chain; policy plaintext never
+  leaves the device unless the user chooses to disclose
+
+Run: `.venv/bin/python demo/demo_policy.py`
+
+## MCP server tools
+
+| Tool | Purpose | Caller |
+|------|---------|--------|
+| `evaluate_payment` | Pre-payment evaluation. ALLOW proceeds / DENY aborts / **ASK** returns a challenge the user signs; retry with `approval_token` | Agent |
+| `set_policy` | **Privileged**: submit a new policy version; requires the owner's EIP-191 signature | User only |
+| `revoke_policy` | **Privileged**: revoke a policy chain (default-deny immediately, free forever) | User only |
+| `get_policy_versions` | Policy version history (chain + hashes, comparable with on-chain commitments) | Anyone |
+| `get_policy` | View the legacy fallback policy | Anyone |
+| `get_spend_report` | Today's spend / remaining budget | Agent |
+| `get_audit_trail` | Approval audit records | Agent |
+| `request_policy_change` | Agent asks the user for a policy change (queued, never self-applied) | Agent |
+| `list_templates` / `render_template` | Policy template helpers | Agent |
+
+### Mount into Claude Desktop
+
+One line — uvx resolves dependencies and starts the server:
+
+```json
+{
+  "mcpServers": {
+    "boundra": {
+      "command": "uvx",
+      "args": ["--from", "git+https://github.com/gobeyondfj-cmd/boundra", "boundra-mcp"]
+    }
+  }
+}
+```
+
+On first run, use the **`boundra-init`** wizard (same package): create/import a
+wallet → pick a policy template → sign → publish via MCP, about 2 minutes.
+When your agent hits ASK, run **`boundra-approve`** and paste the challenge to
+produce a signed approval token.
+
+## ⚠️ Known trust-boundary simplifications (must fix for production)
+
+1. ~~`human_approved` self-attested by the agent~~ **solved (v3)**: human
+   approval is now a signed approval token (approval.py) — ASK returns a
+   challenge bound to the exact payment intent; the user's device signs it;
+   the gateway verifies signature + field-by-field intent match + nonce
+   replay protection. The legacy self-attested path remains but is tagged
+   `approve(legacy-deprecated)`.
+2. **MCP-level interception is advisory** — an agent framework can bypass the
+   gateway and talk to the wallet directly. Mitigation: pair with x402's
+   native hook (demonstrated in `demo/demo_real.py`; the hook fires inside the SDK,
+   before signing). Endgame: compile the deterministic parts of policy into a
+   smart-contract wallet module, enforced at the settlement layer.
+3. **Semantic detection is regex-based** — production should swap in LLM
+   evaluation + intent anchoring.
+4. **Anchoring defaults to a local log** — the real contract
+   (`contracts/PolicyAnchor.sol`) and web3 client (`chain_anchor.BaseSepoliaAnchor`)
+   are ready; set `chain_config.json` to switch to the real chain (deploy via
+   Remix with test ETH).
+
+## Economic model: the evaluation API is itself an x402 merchant
+
+Tiered pricing:
+
+| Operation | Price |
+|-----------|-------|
+| Deterministic evaluation (`/evaluate/basic`) | Free |
+| Semantic evaluation (`/evaluate/semantic`) | 100 free calls per agent; then $0.003 USDC/call (real x402 charge) |
+| Policy anchoring / revocation | Free (revocation is free forever — a safety red line) |
+
+Open core: the client, evaluation engine, and demos in this repo are
+Apache-2.0. The hosted evaluation service (tiered pricing, free-quota
+accounting, revenue ledger) runs from the private `boundra-ops` repo.
+
+## Verified / not yet verified
+
+**Verified** (all of `test_product.py` 22 assertions + `test_mcp_client.py` pass):
+4-layer policy stacking (platform red lines × user × agent × Mandate) with
+strictest-wins; signed approval tokens (valid passes, forged rejected,
+intent-rebinding rejected, replay rejected); Mandate single-use; revocation
+defaults to deny and a signed v2 restores; template render+compile; all MCP
+tools over the wire; gateway blocks an injection attack inside the real x402
+402 round-trip before the SDK signs; the full tiered-pricing loop on Base
+Sepolia (2026-10-16): free tier passes, paid tier settles $0.003 USDC for real
+(buyer 20.000 → 19.997, platform address credited 0.003), dogfood hook
+self-evaluates, semantic layer blocks the injection, `/revenue` ledger entry.
+The settlement tx is publicly verifiable: [`0x5ad8ef4b…c474bbe`](https://sepolia.basescan.org/tx/0x5ad8ef4b4d6eef7ba34e718742068f8e8480336c12032a3a85801b101c474bbe)
+(the hosted service code is closed by design — the chain is the receipt).
+
+**Not yet verified**: real on-chain anchoring (contract ready, needs test ETH
+to deploy); real user demand; semantic layer false-positive rate under real
+LLM behavior distributions.