agentgates.aiVerified
Confidential computers for AI swarms: sealed VMs (Intel TDX) by the hour, USDC over x402.
Finance & CryptoPayments & trading
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 514 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Read Bitcoin-anchored conduct history (NENRIN), admissions and daily check roots; cite records.
0 failed · 7 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 1 | 0 | 3 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using JIDEC: Bitcoin-anchored public verification ledger (NENRIN)
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http jidec-bitcoin-anchored-public-verification-ledger-nenrin https://jidec.horizonshield.dev/mcpCapabilities
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.
DiscoveredReturn 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.
DiscoveredList the anchored JIDEC verification paths (most recent first), with purpose, verdict and Bitcoin anchoring status.
DiscoveredRe-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.
DiscoveredReturn one admission record (a2a-admission-v0) as the ledger stores it, by its canonical SHA-256: the exact record bytes, pending or anchored, and the ledger entry once anchored. A door writes one before it lets an agent's action run; version 0.4 carries the content check as fields only (a salted commitment to the content, the digest of the check, the rule set, decision, marks), no text. The anchored admissions of a relying party are also listed in admissions[] of its Résumé (nenrin_resume).
DiscoveredReturn one agreement record as the ledger stores it, by its canonical SHA-256: the exact record bytes, pending or anchored, and the ledger entry once anchored. The anchored agreements of an endpoint are listed in agreements[] of its Résumé (nenrin_resume).
DiscoveredReturn the day record (furui-check-day-v0) of the content check runner: the signed RFC 6962 root of one UTC day's check envelopes and their count. Give its SHA-256, or a day (YYYY-MM-DD) to find it through the runner's day status. This server reads the record from the ledger and the key from the ledger's /.well-known/furui-check-keys.json, and recomputes: the bytes hash to the SHA-256, the shape is closed, the key is listed for the record's heights, the Ed25519 signature verifies, and whether the record is anchored. No content, scope or answer text is in it.
DiscoveredReturn envelope i of a closed UTC day as the content check runner serves it (kept 7 days after the day), with its RFC 6962 audit path. This server recomputes: the envelope has the closed shape (digests, numbers, booleans, fixed words; no text), the leaf hash is sha256(0x00 || canonical envelope), the audit path rebuilds the root of the day record the ledger stores, and the runner's Ed25519 signature verifies under the key the ledger lists. An admission of version 0.4 names the check of such an envelope by its digest.
DiscoveredReturn 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.
DiscoveredReturn 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.
DiscoveredReturn 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[] (anchored agreements), admissions[] (the anchored admissions whose relying party is on the endpoint's host: record_sha256, ledger entry, decision, the closed part of a 0.4 content block, revoked; no text), 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.
DiscoveredReturn 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.
DiscoveredReturn 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 48 ms | 13 | |
| Connected | 82 ms | 13 |