← horizonshield.dev

INDIVIDUAL MCP TOOL

jidec_replay

Re-observe an anchored JIDEC verification path against the live system right now and report drift.

horizonshield.devnone authenticationAvailability not checked

LIVE ENDPOINT

https://jidec.horizonshield.dev/mcp

No auth detected

Connect to this endpoint to inspect the live schema for jidec_replay and invoke it with your own arguments.

Indexed 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 server

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

.mcp.json

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

Settings → Connectors → Add custom connector

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

.vscode/mcp.json

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

Client-specific MCP configuration

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

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

Related tools

  • jidec_cite — Resolve and INDEPENDENTLY verify any JIDEC citation.
  • jidec_list_paths — List the anchored JIDEC verification paths (most recent first), with purpose, verdict and Bitcoin anchoring status.
  • jidec_how_to_verify — Return the step-by-step recipe for verifying a JIDEC record WITHOUT trusting HORIZON SHIELD: which bytes to fetch, which hashes to recompute, which OpenTimestamps proof to check, which algorithm commit to check out, and what must match.
  • nenrin_resume — Return the NENRIN résumé of an agent or MCP endpoint: every recorded measurement that touches its origin (by the gate and by outside witnesses, signed or not), which are Bitcoin-anchored, discrepancies, rings, agreements, and the records not counted with the reason.
  • nenrin_trust_signal — Return the compact NENRIN signal for an endpoint: counts of anchored measurements, witness diversity and freshness, in a shape a trust engine or orderer can read.
  • nenrin_witness — Return one NENRIN witness record by its record SHA-256: pending or anchored, and when anchored, the ledger entry and batch that carry it.
  • nenrin_ledger_head — Return the current head of the JIDEC/NENRIN ledger: entry count n, the head hash, and the end marker bound into the chain (jidec-head-v1) with the recipe to recompute it.
  • nenrin_ledger_entry — Return ledger entry n as the ledger serves it: claim_sha256, the canonical record bytes, work description, OpenTimestamps status and Bitcoin block when anchored.