mcpbeat Sign in

JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP Server

answering

JIDEC: Bitcoin-anchored public verification ledger (NENRIN) is answering right now. Last checked 16 min ago. It exposes 9 tools. Last commit 25 Oct 2026.

Read agents' Bitcoin-anchored conduct history (NENRIN) and cite and recompute ledger records.

Uptime history 72 days of history · worst day 95%
72 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
154 ms
Response time
average over 24h
2
Stars
last commit 25 Oct 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 August 2026. No other catalogue keeps this.

30 Sep 5 tools appeared nenrin_ledger_entry, nenrin_ledger_head, nenrin_resume and 2 more
30 Sep a tool changed version
4 Sep a tool changed version
17 Aug a tool changed version

What the code does

We read the source, 1 h ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    return list(csv.DictReader(open(os.path.join(V1, "observations", fn), encoding="utf-8")))
    t8 = N(subprocess.run(["pdftotext", "-layout", os.path.join(OBS2, "raw", "mlit-gijutsusha-r8.pdf"), "-"], capture_output=True).stdout.decode())
Runs an external command ops/no_swallowed_read.mjs:106
  const r = spawnSync(process.execPath, ["--expose-internals", ...process.execArgv, script, ...process.argv.slice(2)], { stdio: "inherit" });
Executes code built at runtime tools/jcs_conformance.mjs:35
const canonicalJson = new Function(m[0] + "; return canonicalJson;")();
Executes code built at runtime tools/us_teardown_series.py:779
        val = eval(expr, {"__builtins__": {}})
  document.getElementById('main').innerHTML = fns[state.tab]();
<script src="https://www.paypal.com/sdk/js?client-id=AVePXfDeP_YDUgmcFEJNjFHuYkbXZ-VQcLEecJs5Li2la9qDbtZJamy-iXzTxWlPdUODt6KNV3nqUKHP&currency=JPY&locale=ja_JP"></script>
  for (const f of fs.readdirSync(feedDir)) {
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

            curl -s -X POST -H "Authorization: Bearer ${{ secrets.GITHUB_TOKEN }}" -H "Accept: application/vnd.github+json" https://api.github.com/repos/${{ github.repository }}/actions/workflows/static.yml/dispatches -d '{"ref":"main"}'

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 16 min ago.

run in your terminal
claude mcp add jidec --transport http https://jidec.horizonshield.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://jidec.horizonshield.dev/mcp
~/.codex/config.toml
[mcp_servers.jidec]
url = "https://jidec.horizonshield.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "jidec": {
      "url": "https://jidec.horizonshield.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "jidec": {
      "type": "http",
      "url": "https://jidec.horizonshield.dev/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

nenrin
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. Pair with jidec_how_to_verify to recompute 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. Compare it with a head you saw earlier to detect truncation or rewrite.
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. Includes resume_sha256 and a recompute recipe. A history, not a score. Absent means no record, not a negative finding.
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. No score, no allow or deny.
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. Use it to check a walk someone says they submitted.
jidec
jidec_cite
Resolve and INDEPENDENTLY verify any JIDEC citation. Accepts 'jidec:path:<sha>', 'jidec:entry:<n>', a bare 64-hex id, or a ledger URL. Fetches the record's exact bytes, recomputes SHA-256 locally, and confirms it equals the cited id. Returns integrity, Bitcoin anchoring status, the parsed record (verification path, claim, or v0 spec entry), and an explicit statement of what the proof does and does not cover. No trust in HORIZON SHIELD is required to accept the result.
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. Use this when you want to confirm the result yourself rather than repeat an assertion.
jidec_list_paths
List the anchored JIDEC verification paths (most recent first), with purpose, verdict and Bitcoin anchoring status.
jidec_replay
Re-observe an anchored JIDEC verification path against the live system right now and report drift. Returns MATCH (the live system still matches what was anchored) or DRIFT (it changed), node by node. Nodes that cannot be re-observed server-side are reported as deferred, never counted as drift.

Endpoints

URLTransportStateLatencyChecked
https://jidec.horizonshield.dev/mcp streamable-http answering 79 ms 16 min ago

Alternatives to JIDEC: Bitcoin-anchored public verification ledger (NENRIN)

same job, measured the same way
Rubric MCP Server
by 0xsims

Attest agent decisions and verify records on a public ledger. Evidence, not just data.

203 installs/wk local only
Verified by NPC
by bayo-de

Check products, credentials, claims, and agents against NPC Labs verification records.

570 installs/wk local only
Arkova Verification
by carson-see

Privacy-first document verification anchored to the public ledger.

answering
Touchstone
by touchstone

Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.

26 installs/wk answering
Video History Project
by videohistoryproject

Search experimental video history, read public records, follow sources and export citations.

6 tools answering
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering
AuthiChain
by undone0603

Look up AuthiChain product records. x402 paid verification and on-chain anchoring in development.

6 tools answering
M
Marvnor
by wendelxia

Hosted agent memory with record-based verification, conflict detection, correction and deletion.

answering

JIDEC: Bitcoin-anchored public verification ledger (NENRIN) — questions

Answers built from our own checks of this server.

What can JIDEC: Bitcoin-anchored public verification ledger (NENRIN) do?
It exposes 9 tools, read directly from the server on our last check. Among them: jidec_cite, jidec_how_to_verify, jidec_list_paths, jidec_replay, nenrin_ledger_entry, nenrin_ledger_head and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is JIDEC: Bitcoin-anchored public verification ledger (NENRIN) mostly used for?
Its tools cluster around nenrin and jidec. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is JIDEC: Bitcoin-anchored public verification ledger (NENRIN) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 154 ms. The bar chart above shows every period we have measured.
How do I connect JIDEC: Bitcoin-anchored public verification ledger (NENRIN)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does JIDEC: Bitcoin-anchored public verification ledger (NENRIN) need an API key?
No. JIDEC: Bitcoin-anchored public verification ledger (NENRIN) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is JIDEC: Bitcoin-anchored public verification ledger (NENRIN)?
It answers our handshake in 154 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is JIDEC: Bitcoin-anchored public verification ledger (NENRIN) open source?
The code is open source: it is published under the MIT licence, written in HTML, 2 stars on GitHub and 24 open issues. The licence covers the code in the repository, not the hosted service at jidec.horizonshield.dev, which runs on its operator's own terms.