MCP server exposing a Warda grant's whole life to agent frameworks: authority, spends, delegation, settlement, revocation and recovery. Builds unsigned transactions and explains verdicts; never holds a key, never enforces — the covenant does that on-chain
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
warda_grant_authorityThe agent's spending power right now: budget left, epoch headroom, per-transaction cap,The agent's spending power right now: budget left, epoch headroom, per-transaction cap,
No input schema was published for this tool.
warda_check_spendCheck a proposed payment against every rule the covenant enforces, and return the sameCheck a proposed payment against every rule the covenant enforces, and return the same
No input schema was published for this tool.
warda_check_delegationCheck whether a proposed child grant is a legal narrowing of this one. A child may onlyCheck whether a proposed child grant is a legal narrowing of this one. A child may only
No input schema was published for this tool.
warda_build_spendAssemble an unsigned Kaspa transaction that spends from this grant, and return the digestAssemble an unsigned Kaspa transaction that spends from this grant, and return the digest
No input schema was published for this tool.
warda_walletThe whole wallet view in one call: the grant's current address, its spending limits,The whole wallet view in one call: the grant's current address, its spending limits,
No input schema was published for this tool.
warda_grant_addressDerive the on-chain address of a grant from its terms and current state. A grant'sDerive the on-chain address of a grant from its terms and current state. A grant's
No input schema was published for this tool.
warda_recover_grantRead a grant's full state back out of any transaction that spent it, and work outRead a grant's full state back out of any transaction that spent it, and work out
No input schema was published for this tool.
warda_build_delegationAssemble an unsigned transaction that subdivides this grant into a child for aAssemble an unsigned transaction that subdivides this grant into a child for a
No input schema was published for this tool.
warda_build_settlementAssemble an unsigned transaction that ends a child grant and returns its UNSPENTAssemble an unsigned transaction that ends a child grant and returns its UNSPENT
No input schema was published for this tool.
warda_build_exitAssemble an unsigned transaction that ENDS this grant and sweeps its balance to theAssemble an unsigned transaction that ENDS this grant and sweeps its balance to the
No input schema was published for this tool.
warda_find_serviceSearch the Warda service registry for endpoints an agent holding a grant can pay.Search the Warda service registry for endpoints an agent holding a grant can pay.
No input schema was published for this tool.
11 of 11 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server exposing a Warda grant's whole life to agent frameworks: authority, spends, delegation, settlement, revocation and recovery. Builds unsigned transactions and explains verdicts; never holds a key, never enforces — the covenant does that on-chain
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
57 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+45 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.