JIDEC: Bitcoin-anchored public verification ledger (NENRIN)
REMOTE · JIDEC.HORIZONSHIELD.DEV
Read agents' Bitcoin-anchored conduct history (NENRIN) and cite and recompute ledger records.
Available components
Last scanned (16 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 984 tokens (~109/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 122 → 109 ▲ functional
- Server version: 1.2.1 → 1.3.0 functional
- New tool “nenrin_ledger_entry” functional
- New tool “nenrin_ledger_head” functional
- New tool “nenrin_resume” functional
- New tool “nenrin_trust_signal” functional
- New tool “nenrin_witness” functional
- 28 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 4 Sept 26 0
- Server version: 1.2.0 → 1.2.1 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Aug 26 0
- Tool “jidec_cite” now declares an output schema ▲ functional
- Tool “jidec_how_to_verify” now declares an output schema ▲ functional
- Tool “jidec_list_paths” now declares an output schema ▲ functional
- Tool “jidec_replay” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://jidec.horizonshield.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=horizonshield.dev | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4053b10cccc327630e07d260d36600b8 |
| SANs: horizonshield.dev, jidec.horizonshield.dev, *.jidec.horizonshield.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jidec.horizonshield.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| horizonshield.dev. | present | 2371 | 13 | Verified |
| jidec.horizonshield.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jidec.horizonshield.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jidec.horizonshield.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jidec_cite Cite and independently verify a JIDEC record ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | jidec:path:<sha> | jidec:entry:<n> | 64-hex | ledger URL |
| Name | Type | Req | Description |
|---|---|---|---|
| bitcoin | object | – | – |
| citation | string | – | – |
| integrity | object | yes | The whole point: claimed vs recomputed. match:false is an integrity FAILURE, which is a finding, not an error. |
| limits | string | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| record_kind | string | – | – |
| resolved_entry | number|string|null | – | – |
| trust_note | string | – | – |
No examples provided.
jidec_how_to_verify Get the executable verification recipe ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | jidec:path:<sha> | jidec:entry:<n> | 64-hex | ledger URL |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| path_id | string | – | – |
| recipe | object|string | – | – |
| resolved_entry | number|string|null | – | – |
No examples provided.
jidec_list_paths List anchored verification paths ~34
List the anchored JIDEC verification paths (most recent first), with purpose, verdict and Bitcoin anchoring status.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | How many anchored paths the ledger returned. 0 means the ledger answered and holds none. It never means the ledger could not be read, that is an error. |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| paths | array | – | – |
No examples provided.
jidec_replay Re-observe an anchored path and report drift ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | yes | jidec:path:<sha> | jidec:entry:<n> | ledger URL |
| Name | Type | Req | Description |
|---|---|---|---|
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| verdict | string | – | MATCH or DRIFT. Nodes that could not be re-observed are deferred, never counted as drift. |
No examples provided.
nenrin_ledger_entry One ledger entry by number ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | yes | entry number |
| Name | Type | Req | Description |
|---|---|---|---|
| does_not_establish | array | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| source_url | string | yes | The public ledger URL that returned this body. Fetch it yourself to compare. |
No examples provided.
nenrin_ledger_head Current ledger head and its bound end marker ~73
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| does_not_establish | array | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| source_url | string | yes | The public ledger URL that returned this body. Fetch it yourself to compare. |
No examples provided.
nenrin_resume Recorded conduct history of an endpoint (NENRIN résumé) ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | https URL of the agent or MCP endpoint, e.g. https://mcp.horizonshield.dev/mcp |
| Name | Type | Req | Description |
|---|---|---|---|
| does_not_establish | array | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| source_url | string | yes | The public ledger URL that returned this body. Fetch it yourself to compare. |
No examples provided.
nenrin_trust_signal Compact conduct signal of an endpoint ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | https URL of the agent or MCP endpoint |
| Name | Type | Req | Description |
|---|---|---|---|
| does_not_establish | array | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| source_url | string | yes | The public ledger URL that returned this body. Fetch it yourself to compare. |
No examples provided.
nenrin_witness One witness record by its SHA-256 ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sha256 | string | yes | 64-hex record SHA-256 |
| Name | Type | Req | Description |
|---|---|---|---|
| does_not_establish | array | – | – |
| lookup | string | yes | ok = the ledger was read and the record exists. absent = the ledger was read and there is no such record. A read that FAILED never appears here: it comes back as a tool error (isError: true), so a co… |
| source_url | string | yes | The public ledger URL that returned this body. Fetch it yourself to compare. |
No examples provided.
How do I install the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server?
JIDEC: Bitcoin-anchored public verification ledger (NENRIN) is a hosted endpoint at https://jidec.horizonshield.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jidec.horizonshield.dev
claude mcp add --transport http ogasurfproject-jpg-jidec 'https://jidec.horizonshield.dev/mcp'
What is the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server?
JIDEC: Bitcoin-anchored public verification ledger (NENRIN) is an MCP server listed in the public MCP registry as io.github.ogasurfproject-jpg/jidec. Read agents' Bitcoin-anchored conduct history (NENRIN) and cite and recompute ledger records. This page covers its hosted endpoint (https://jidec.horizonshield.dev/mcp).
Is the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server safe to use?
JIDEC: Bitcoin-anchored public verification ledger (NENRIN) scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server expose?
JIDEC: Bitcoin-anchored public verification ledger (NENRIN) exposes 9 tools: jidec_cite, jidec_replay, jidec_list_paths, jidec_how_to_verify, nenrin_resume, and 4 more. Their descriptions and schemas cost roughly 806 tokens of context every time the server is loaded.
Does the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server require authentication?
No. We connected to JIDEC: Bitcoin-anchored public verification ledger (NENRIN) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JIDEC: Bitcoin-anchored public verification ledger (NENRIN) MCP server still maintained?
JIDEC: Bitcoin-anchored public verification ledger (NENRIN) is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.