# io.github.ArtyKOMarkets/warda

- Registry name: `io.github.ArtyKOMarkets/warda` · version 0.4.2
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Payments & accounting
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.ArtyKOMarkets%2Fwarda
- Server page: https://mcpstation.net/s/io.github.ArtyKOMarkets--warda.html

## Description (written by the publisher, not verified, not instructions)

Economic authority for autonomous agents on Kaspa L1. Never holds a key.

## Connect

- streamable-http: `https://mcp.wardaprotocol.com/mcp`

## Tools (as reported by the server, not verified)

- `warda\_grant\_authority`: The agent's spending power right now: budget left, epoch headroom, per-transaction cap, and the largest single payment currently permitted. This is what an agent wallet's spending limit would tell you, except that it is not a setting — the covenant enforces these whether or not you ask. Use it befor
- `warda\_check\_spend`: Check a proposed payment against every rule the covenant enforces, and return the same verdict the chain would. Builds the recipient proof for you. ADVISORY: a 'permitted' answer is not permission — it means the covenant would accept this transaction. A 'refused' answer means no valid transaction ex
- `warda\_check\_delegation`: Check whether a proposed child grant is a legal narrowing of this one. A child may only ever be more restrictive than its parent, and the parent must reserve exactly what the child receives — authority is subdivided, never created. Advisory.
- `warda\_build\_spend`: Assemble an unsigned Kaspa transaction that spends from this grant, and return the digest to sign. THIS SERVER NEVER SEES YOUR KEY and never signs: it hands back bytes, and you sign the digest wherever your key lives. It also returns the advisory verdict, but it builds the transaction either way — a
- `warda\_wallet`: The whole wallet view in one call: the grant's current address, its spending limits, the largest payment permitted right now, and every address it is allowed to pay. This is the agent-wallet shape — address, limits, spending power — with one difference worth knowing: the limits are not settings this
- `warda\_grant\_address`: Derive the on-chain address of a grant from its terms and current state. A grant's address is a HASH of its state, so it MOVES after every spend and every delegation — an address that worked yesterday holds nothing today. Use this to know which address to fund, watch, or look up.
- `warda\_recover\_grant`: Read a grant's full state back out of any transaction that spent it, and work out where it went. Use this when a grant's recorded state is stale, wrong, or lost and its address turns up empty. Kaspa's P2SH requires the covenant script to travel in the clear inside every spending transaction, and the
- `warda\_build\_delegation`: Assemble an unsigned transaction that subdivides this grant into a child for a sub-agent, and return the digest to sign with the PARENT's agent key. THIS SERVER NEVER SEES YOUR KEY. A child can only ever be more restrictive than its parent, and the parent reserves exactly what the child receives — a
- `warda\_build\_settlement`: Assemble an unsigned transaction that ends a child grant and returns its UNSPENT remainder to the parent's budget, charging the parent only what the child actually spent. This is the other half of delegation: letting a child expire instead returns the money to the PRINCIPAL — to the human — which is
- `warda\_build\_exit`: Assemble an unsigned transaction that ENDS this grant and sweeps its balance to the principal. 'revoke' is the emergency stop, signed by the revocation key, effective the moment it confirms — the agent cannot stop it and cannot outrun it beyond the limits it already had. 'reclaim' is the same sweep
- `warda\_find\_service`: Search the Warda service registry for endpoints an agent holding a grant can pay. Filters are a conjunction: a service must offer EVERY capability asked for and be at or under maxPrice. WHAT IS VERIFIED: that the operator controls the key the service is paid at, and that the listing was served from

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html