← kaspaseal.dev

INDIVIDUAL MCP TOOL

hash_data

Compute sha256 over the JCS-canonical bytes of any JSON value — the same payload_hash anchor_action would produce — without anchoring.

kaspaseal.devnone authenticationAvailability not checked

Input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent endpoint

kaspaseal.dev

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.kaspaseal-dev]
url = "https://mcp.kaspaseal.dev/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "kaspaseal-dev": {
      "type": "http",
      "url": "https://mcp.kaspaseal.dev/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: kaspaseal-dev
Remote MCP URL: https://mcp.kaspaseal.dev/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": {
    "kaspaseal-dev": {
      "url": "https://mcp.kaspaseal.dev/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "kaspaseal-dev": {
      "type": "http",
      "url": "https://mcp.kaspaseal.dev/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "kaspaseal-dev",
  "transport": "streamable-http",
  "url": "https://mcp.kaspaseal.dev/mcp"
}
MCP Inspector

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

Related tools

  • verify_proof — Re-compute sha256(JCS(data)), Schnorr-verify the signature, and re-derive the bech32 address from the public key — all locally, no chain query.
  • verify_proof_onchain — Chain-backed verification over the hosted operator node: looks up the bundle's txid (mempool / confirmation), and — when confirmed — checks the on-chain KAP1 payload commits to the bundle's payload_hash / parent_txid / action_type, then walks the parent chain.