# io.github.ArtyKOMarkets/warda (remote · mcp.wardaprotocol.com)

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

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mcp.wardaprotocol.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/artykomarkets-warda/mcp.md), [page](https://verifymcp.io/servers/artykomarkets-warda/mcp)
- npm · `@warda_protocol/mcp`: 78/100, [markdown](https://verifymcp.io/servers/artykomarkets-warda/warda-protocol-mcp.md), [page](https://verifymcp.io/servers/artykomarkets-warda/warda-protocol-mcp)

## Channel facts

- Endpoint: `https://mcp.wardaprotocol.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2408 tokens (~218/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.ArtyKOMarkets/warda MCP server?

io.github.ArtyKOMarkets/warda is a hosted endpoint at https://mcp.wardaprotocol.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http artykomarkets-warda 'https://mcp.wardaprotocol.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "artykomarkets-warda": {
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "artykomarkets-warda": {
      "type": "http",
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.artykomarkets-warda]
url = "https://mcp.wardaprotocol.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "artykomarkets-warda": {
      "type": "remote",
      "url": "https://mcp.wardaprotocol.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add artykomarkets-warda --url 'https://mcp.wardaprotocol.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  artykomarkets-warda:
    url: "https://mcp.wardaprotocol.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "artykomarkets-warda": {
      "Transport": "http",
      "Url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add artykomarkets-warda -t streamable-http -u 'https://mcp.wardaprotocol.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "artykomarkets-warda": {
      "type": "http",
      "url": "https://mcp.wardaprotocol.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 74, +1)

- [functional] Server version: 0.6.0 → 0.6.1

### 2026-09-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 70, 0)

- [functional regression] Schema quality: 2098 → 2408
- [functional] Server version: 0.5.1 → 0.6.0
- [functional] New tool “warda_find_service”

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +1)

- [functional] Server version: 0.5.0 → 0.5.1

## MCP tools (11)

### `warda_grant_authority` (~140 tokens)

What may this agent spend?

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.

Input parameters:

- `daaScore` (string, required): Current DAA score of the chain.
- `grant` (object, required): The grant, as issued by the principal.

### `warda_check_spend` (~138 tokens)

Would this payment be allowed?

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.

Input parameters:

- `amountKas` (string, required): Amount to pay, in KAS.
- `daaScore` (string, required)
- `grant` (object, required): The grant, as issued by the principal.
- `recipient` (string, required): Payee public key, 32 bytes of hex.

### `warda_check_delegation` (~121 tokens)

Would this delegation be allowed?

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.

Input parameters:

- `childAgentKey` (string, required)
- `childBudgetKas` (string, required)
- `childEpochLimitKas` (string, required)
- `childMaxPerSpendKas` (string, required)
- `daaScore` (string, required)
- `parent` (object, required): The grant, as issued by the principal.

### `warda_build_spend` (~290 tokens)

Build a payment for me to sign

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.

Input parameters:

- `amountKas` (string, required): Amount to pay, in KAS.
- `computeBudget` (number): Defaults to 16. Charged as mass, so over-provisioning costs money and under-provisioning is rejected outright.
- `daaScore` (string, required): Current DAA score of the chain.
- `feeSompi` (string): Defaults to 3000000. A covenant spend carries the whole redeem script in its signature script — about 7KB — so its mass is dominated by size and an ordinary transfer's fee is rejected as non-standard.
- `grant` (object, required): The grant, as issued by the principal.
- `recipient` (string, required): Payee public key, 32 bytes of hex. Must be on the allowlist.
- `utxo` (object, required): The grant's CURRENT UTXO. Its address moves after every spend, so a stale one will not be found.

### `warda_wallet` (~211 tokens)

Show me this agent's 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.

Input parameters:

- `daaScore` (string, required): Current DAA score of the chain.
- `grant` (object, required): The grant, as issued by the principal.
- `prefix` (string): Address prefix: kaspa, kaspatest, kaspasim or kaspadev. Defaults to kaspatest.

### `warda_grant_address` (~118 tokens)

Where does this grant live right now?

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.

Input parameters:

- `grant` (object, required): The grant, as issued by the principal.
- `prefix` (string): Address prefix: kaspa, kaspatest, kaspasim or kaspadev. Defaults to kaspatest.

### `warda_recover_grant` (~179 tokens)

Find a grant again from a transaction that spent it

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.

Input parameters:

- `prefix` (string): Address prefix: kaspa, kaspatest, kaspasim or kaspadev. Defaults to kaspatest.
- `redeemScriptHex` (string): The covenant script alone, if you have only that.
- `transaction`: A wire-format transaction that spent the grant.

### `warda_build_delegation` (~369 tokens)

Build a delegation for me to sign

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.

Input parameters:

- `childAgentKey` (string, required): The sub-agent's x-only public key, 32 bytes of hex.
- `childBudgetKas` (string, required)
- `childDelegationDepth` (number, required): Strictly less than the parent's, or the tree could not terminate.
- `childEpochLimitKas` (string, required)
- `childExpiresAt` (string): A short window is the only attenuation that ends BY ITSELF, with nobody online to revoke.
- `childMaxPerSpendKas` (string, required)
- `childNotBefore` (string): Inherited from the parent when omitted.
- `childRecipients` (array): A subset of the parent's allowlist. Omit to inherit all of it.
- `computeBudget` (number)
- `feeSompi` (string)
- `parent` (object, required): The grant, as issued by the principal.
- `parentRecipients` (array): The parent's FULL member list. Required only when childRecipients narrows it.
- `prefix` (string): Address prefix: kaspa, kaspatest, kaspasim or kaspadev. Defaults to kaspatest.
- `utxo` (object, required): The grant's CURRENT UTXO. Its address moves after every spend, so a stale one will not be found.

### `warda_build_settlement` (~297 tokens)

Build a settlement, collapsing a child back into its parent

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.

Input parameters:

- `child` (required)
- `childUtxo` (required)
- `computeBudget` (number)
- `feeSompi` (string): Defaults to 2000000 — two covenant inputs, so roughly twice a spend's mass.
- `parent` (object, required): The grant, as issued by the principal.
- `parentUtxo` (object, required): The grant's CURRENT UTXO. Its address moves after every spend, so a stale one will not be found.
- `prefix` (string): Address prefix: kaspa, kaspatest, kaspasim or kaspadev. Defaults to kaspatest.
- `prevRoot` (string, required): The parent's reserve root before this child was pushed.

### `warda_build_exit` (~235 tokens)

Build a revocation or a reclaim

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.

Input parameters:

- `computeBudget` (number)
- `feeSompi` (string)
- `grant` (object, required): The grant, as issued by the principal.
- `kind` (string, required)
- `lockTime` (string): Reclaim needs at least expiresAt, and still below the current DAA score. Revoke takes 0.
- `utxo` (object, required): The grant's CURRENT UTXO. Its address moves after every spend, so a stale one will not be found.

### `warda_find_service` (~310 tokens)

What can this agent buy, and for how much?

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.

Input parameters:

- `capability` (array): Capabilities the service must offer, ALL of them. e.g. ['weather.current']
- `maxPrice` (string): Most you will pay per unit, as a decimal string in the asset's own units, e.g. '0.05'.
- `network` (string): e.g. 'kaspa:testnet-10'. Omit for any.
- `q` (string): Plain substring over name and description. Crude on purpose.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/artykomarkets-warda/mcp#diagnostics

## Score history

- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 65
- 2026-09-02: 64
- 2026-09-01: 64

## Common questions

### What is the io.github.ArtyKOMarkets/warda MCP server?

io.github.ArtyKOMarkets/warda is an MCP server listed in the public MCP registry as io.github.ArtyKOMarkets/warda. Economic authority for autonomous agents on Kaspa L1. Never holds a key. This page covers its hosted endpoint (https://mcp.wardaprotocol.com/mcp).

### Is the io.github.ArtyKOMarkets/warda MCP server safe to use?

io.github.ArtyKOMarkets/warda scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.ArtyKOMarkets/warda MCP server expose?

io.github.ArtyKOMarkets/warda exposes 11 tools: warda_grant_authority, warda_check_spend, warda_check_delegation, warda_build_spend, warda_wallet, and 6 more. Their descriptions and schemas cost roughly 2,408 tokens of context every time the server is loaded.

### Does the io.github.ArtyKOMarkets/warda MCP server require authentication?

No. We connected to io.github.ArtyKOMarkets/warda without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.ArtyKOMarkets/warda MCP server still maintained?

io.github.ArtyKOMarkets/warda is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.wardaprotocol.com/mcp
- Repository: https://github.com/ArtyKOMarkets/warda
- Website: https://wardaprotocol.com/
- Changelog RSS feed: https://verifymcp.io/servers/artykomarkets-warda/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/artykomarkets-warda/mcp.json
- HTML version of this page: https://verifymcp.io/servers/artykomarkets-warda/mcp