Developer Tools

wardaprotocol.com

Manages and validates Kaspa blockchain grants by reporting authority, checking proposed payments, and assembling unsigned spending transactions.

1 endpoint9 known toolsFirst detected September 2, 2026Last detected September 6, 2026

ENDPOINT 1

https://mcp.wardaprotocol.com/mcp

No auth detected

MCP server metadata

Name: warda
Version: 0.4.1

Capabilities

tools.listChanged

Known tools 9

warda_grant_authority

Report a grant's remaining authority: budget left, epoch headroom, per-transaction cap, and the largest single payment permitted right now.

Potential side effects

warda_check_spend

Check a proposed payment against every rule the covenant enforces, and return the same verdict the chain would.

Potential side effects

warda_check_delegation

Check whether a proposed child grant is a legal narrowing of this one.

Inferred read-only

warda_build_spend

Assemble an unsigned Kaspa transaction that spends from this grant, and return the digest to sign.

Inferred read-only

warda_grant_address

Derive the on-chain address of a grant from its terms and current state.

Inferred read-only

warda_recover_grant

Read a grant's full state back out of any transaction that spent it, and work out where it went.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

warda_build_exit

Assemble an unsigned transaction that ENDS this grant and sweeps its balance to the principal.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: warda
Remote MCP URL: https://mcp.wardaprotocol.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "warda",
  "transport": "streamable-http",
  "url": "https://mcp.wardaprotocol.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.