Skip to main content

Agent Spend Mandate & Budget Ledger Verifier MCP

A local evidence verifier that binds supplied transactions to exact mandate IDs, compares merchant, category and currency, enforces validity windows and amount caps, detects duplicate transaction identities and computes deterministic budget usage.

What it creates

  • result.json
  • transaction-binding.csv
  • budget-usage.csv
  • issues.jsonl
  • SPEND_MANDATE_REVIEW.md
  • evidence-receipt.json

Requirements

  • Windows 11
  • Python 3.11–3.14
  • An MCP-compatible client
  • MCP_LICENSE_KEY from the MCP Marketplace purchase
  • Internet access for initial and periodic license verification

License verification sends only the license key and public product slug. Buyer evidence paths, contents and generated reports remain local.

Install from a purchased source checkout

python -m venv .venv
.\.venv\Scripts\python.exe -m pip install .

MCP client configuration

{
  "mcpServers": {
    "spend-mandate": {
      "command": "spend-mandate-mcp",
      "env": {"MCP_LICENSE_KEY": "PASTE_THE_KEY_FROM_YOUR_PURCHASE"}
    }
  }
}

Run the client from the folder containing buyer-authorized evidence. All supplied paths must be relative to that folder.

Tool

build_spend_mandate_packet

  • mandates: Spend-mandate JSONL
  • transactions: Transaction JSONL
  • policy: Spend-ledger policy JSON
  • output_directory: new output directory

The tool returns structured JSON. ERROR means the request could not be processed.

CLI

The diagnostic command is unlicensed:

spend-mandate --json doctor

Protected commands verify the marketplace license before reading buyer files:

spend-mandate --json analyze --mandates examples/sample-input/mandates.jsonl --transactions examples/sample-input/transactions.jsonl --policy examples/sample-input/policy.json --out packet
spend-mandate --json show packet/result.json
spend-mandate --json verify packet/evidence-receipt.json

Product boundary

It does not verify signatures or identity, issue mandates, grant approvals, access cards or wallets, execute payments, refund transactions, handle disputes, enforce policy or attest legal compliance. All accepted evidence stays local. Apart from license verification, the package performs no network activity and has no telemetry.

Release files for agent-spend-mandate-budget-ledger-verifier-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-spend-mandate-budget-ledger-verifier-mcp 0.2.0
File Size Uploaded
agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0.tar.gz 14.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for agent-spend-mandate-budget-ledger-verifier-mcp 0.2.0
File Interpreter ABI Platform
agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 31.2 kB

Release files / agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0.tar.gz

Download URL agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0.tar.gz
Size 14.9 kB
Tags Source
SHA-256 checksum
How to use checksums
45d17cdd9a2eed1a6a3dee00ece370965b89e8fd3590f4a855f5c8545c9ad132
BLAKE2b-256 checksum
How to use checksums
411d61c002aeb1f23c79c8dd88f50d015d5f8bb972b46e2f3e3bd5738026cbc5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.

Transparency log

Release files / agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0-py3-none-any.whl

Download URL agent_spend_mandate_budget_ledger_verifier_mcp-0.2.0-py3-none-any.whl
Size 16.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d024ea51bb7f3857bf0d1f4d6aa5e0440c595d2063b5c636a2cf143a1ebf529d
BLAKE2b-256 checksum
How to use checksums
d9fc14447fede4ee96c195da478bdb9a8ea337b46b47e2b6fdf6b2b043e1de7a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page