bots.st/warda
warda
Build and verify unsigned grant transactions
2013 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 11
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.wardaprotocol.com/mcp - npm
npx -y @warda_protocol/mcpReleased 24 Sep 2026, version 0.6.1
What it can do
| Tool | What it says it does |
|---|---|
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 —… |
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… |
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… |
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 —… |
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_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… |
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… |
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_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… |
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… |
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… |
In its maker's words
Economic authority for autonomous agents on Kaspa L1. Never holds a key.
- Website
- wardaprotocol.com
- Source
- github.com/ArtyKOMarkets/warda
- Publisher
- ArtyKOMarkets
- Listed from
- the official MCP Registry as
io.github.ArtyKOMarkets/warda - Version
- 0.4.2, updated 1 Sep 2026
- Kinds of work
- Crypto and web3, AI models and agent tools, Security and trust
The domain it lives on
- wardaprotocol.com
- registered 31 Aug 2026 (2 months ago), at GoDaddy.com, LLC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2013 ms | |
| Answered | 2301 ms | |
| Answered | 821 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.