Warda MCP Server

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 — authority is subdivided, never created. Narrowing the child's allowlist needs the parent's full member list, because the witness is a path through the parent's tree and a root alone cannot produce one.

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 after the window has closed, signed by the principal key; the covenant enforces the timing with a CLTV, so a reclaim built early simply will not run. THIS SERVER NEVER SEES A KEY. This is the tool a monitor calls when a grant is behaving badly and something has to act.

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 no use to an agent mid-task. Returns TWO digests: the parent's half is signed by the parent's agent key, the child's by the revocation key. THIS SERVER NEVER SEES EITHER. prevRoot is the parent's reserve root from before this child was pushed; warda_build_delegation returns it as parentReserveRootBefore. It cannot be derived from anything on chain — a hash chain pops by preimage.

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 local rule that is too strict must not be able to block a payment the chain would accept. If the verdict says refused, broadcasting will cost a fee and fail.

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.

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 exists, so broadcasting one would only waste a fee.

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 the same host as the endpoint it names. WHAT IS NOT: that the price is real, that the service works, or that it is worth paying — those are the operator's claims about themselves and arrive labelled as such. There is no ranking; do not read the order as one. NETWORK: unlike every other tool on this server, this one makes one outbound request, to the registry and to nothing else. It will not fetch a URL you give it. NOT REQUIRED: discovery is never in the payment path. A listing is a signed manifest at /.well-known/warda-service.json on the operator's own domain — if you already know an endpoint, read that directly and pay it without asking anyone.

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.

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 before planning a purchase. NOT a chain balance: this server never reads the chain. It reports what the grant you passed says, so a stale descriptor gives a confident wrong number.

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 grant's state is spliced into that script — so every spend publishes the grant it spent. Pass the transaction as wire JSON, or just the redeem script hex if that is all you have.

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 server or your code applies. They are in the script that unlocks the coin, so a payment outside them is not refused, it is a transaction that does not exist. NO CHAIN READ: this server never connects to a node. Every figure comes from the grant descriptor you passed, so an on-chain balance is deliberately absent — reporting one from a stale record is the failure this whole protocol keeps meeting.