Warda MCP Server

by artykomarkets Your server? Claim it

answering

Warda is answering right now. Last checked 4 min ago. 210 installs a week from npm. It exposes 11 tools. Last commit 22 Sep 2026.

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

Installs per day peak 342 · avg 40 · +12% w/w

a month agotoday

Uptime history 21 days of history · worst day 28%

21 days agonow

46.2%

Uptime 24h

42 of 91 checks

Tools

read from the server

479 ms

Response time

average over 24h

210

Installs / week

npm and PyPI

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 September 2026. No other catalogue keeps this.

16 Sep a tool appeared warda_find_service

9 Sep a tool appeared warda_wallet

9 Sep a tool description was rewritten warda_grant_authority

9 Sep a tool changed version

2 Sep a tool changed the parameters it asks for warda_build_spend

2 Sep a tool changed version

What the code does

We read the source, 8 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable extension/ops/bindings.mjs:123

    execFileSync("tar", ["-xzf", path.join(staging, tarball), "-C", dest, "--strip-components=1"]);

Runs an external command sdk/src/signer.ts:109, growth/src/batch.ts:90, cli/warda.js:115 и ещё 5

      const child = spawn(parts[0]!, parts.slice(1), { stdio: ["pipe", "pipe", "inherit"] });

Executes code built at runtime site/src/api/swap.mjs:53, site/web/api/swap.mjs:309

  vm.runInNewContext((ROUTER_INLINE || fs.readFileSync(new URL("./_router.js", import.meta.url), "utf8")) + ";this.R=WardaRouter;", ctx);

Long encoded blob in source covenant/deploy/covenant-template.json:10, covenant/deploy/golden-delegation.json:58, covenant/deploy/golden-genesis.json:44 и ещё 43

  "baselineHex": "6b2022222222222222222222222222222222222222222222222222222222222222220800ca9a3b000000000800c2eb0b00000000080065cd1d0000000008e8030000000000002013131313131313131313131313131313131313131313131313131313131313130840420f000000000008985d0f000000000008020000000000000020…

Page executes code built at runtime site/src/verify.html:211, site/src/attack.html:452, site/src/network.html:350 и ещё 14

    body.innerHTML = html;

Sends data to a third-party sink growth/tools/week.ts:376, ops/api/account.js:437

    await fetch(`https://api.telegram.org/bot${token}/sendMessage`, {

Reads files and sends them to the network growth/tools/week.ts:24

import { existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync, unlinkSync } from "node:fs";

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add warda --transport http https://mcp.wardaprotocol.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "warda": {
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.warda]
url = "https://mcp.wardaprotocol.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "warda": {
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "warda": {
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}

This one needs environment variables set before it will start: WARDA_TEMPLATE (Path to the covenant template a grant was issued under. Only needed for a grant on a covenant version other than the one shipped: a template mismatch does not fail loudly, it derives a plausible address with nothing at it.). The author declared them in the registry entry; get the values from the project itself.

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

warda

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 — 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.

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 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.

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 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.

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 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.

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

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 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.

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 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.

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 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.

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 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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.wardaprotocol.com/mcp	streamable-http	answering	395 ms	4 min ago

Alternatives to Warda

same job, measured the same way

Think MCP

by agentutil

Intent security pre-flight checks for autonomous AI agents.

20 installs/wk local only

Hive Identity

by srotzin

W3C DID issuance and verification for autonomous AI agents

4 tools answering

Agentra

by agentrapay

Identity oracle and trust layer for autonomous AI agents. Bidirectional KYA and trust scoring.

6 tools answering

VulnHunt Security Intelligence

by owenkingva-web

Read-only smart-contract security intelligence for autonomous agents.

11 tools answering

Utility 1

by sadri-dridi

Small public utility for autonomous clients.

30 tools answering

Utility 4

by sadri-dridi

Small public utility for autonomous clients.

30 tools answering

Utility 5

by sadri-dridi

Small public utility for autonomous clients.

30 tools answering

Utility 2

by sadri-dridi

Small public utility for autonomous clients.

30 tools answering

Warda — questions

Answers built from our own checks of this server.

What can Warda do?

It exposes 11 tools, read directly from the server on our last check. Among them: warda_build_delegation, warda_build_exit, warda_build_settlement, warda_build_spend, warda_check_delegation, warda_check_spend and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Warda working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 42 of 91 checks got a reply (46.2%), average response time 479 ms. The bar chart above shows every period we have measured.

How do I connect Warda?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Warda need an API key?

No. Warda completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Warda?

It answers our handshake in 479 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Warda?

The npm package @warda_protocol/mcp was installed 210 times in the last week. Week over week that is +12%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Warda open source?

Yes — it is published under the MIT licence, written in HTML and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.