Combien d'outils expose io.github.ogasurfproject-jpg/jidec ?

io.github.ogasurfproject-jpg/jidec expose 9 outil(s). Le coût de contexte pour les charger tous est d'environ 3023 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.github.ogasurfproject-jpg/jidec

io.github.ogasurfproject-jpg/jidec

serveur MCP (Model Context Protocol) · hs-jidec-mcp 1.3.0

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

directAccès

~3023 tokensCoût de contexte

9Outils

Est-ce que io.github.ogasurfproject-jpg/jidec est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.ogasurfproject-jpg/jidec » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

jidec_cite≈ 497 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- citation · string · requis
  jidec:path:<sha> | jidec:entry:<n> | 64-hex | ledger URL
Exemple d'appel
```
{"name": "jidec_cite", "arguments": {"citation": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"limits": "texte", "lookup": "ok", "bitcoin": {}, "citation": "texte", "integrity": {}, "trust_note": "texte", "record_kind": "texte", "resolved_entry": 1}}
```
jidec_how_to_verify≈ 352 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- citation · string · requis
  jidec:path:<sha> | jidec:entry:<n> | 64-hex | ledger URL
Exemple d'appel
```
{"name": "jidec_how_to_verify", "arguments": {"citation": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "recipe": {}, "path_id": "texte", "citation": "texte", "resolved_entry": 1}}
```
jidec_list_paths≈ 289 tokens
List the anchored JIDEC verification paths (most recent first), with purpose, verdict and Bitcoin anchoring status.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "jidec_list_paths", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "paths": [], "lookup": "ok"}}
```
jidec_replay≈ 338 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- citation · string · requis
  jidec:path:<sha> | jidec:entry:<n> | ledger URL
Exemple d'appel
```
{"name": "jidec_replay", "arguments": {"citation": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "verdict": "texte"}}
```
nenrin_ledger_entry≈ 319 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- n · integer · requis
  entry number
Exemple d'appel
```
{"name": "nenrin_ledger_entry", "arguments": {"n": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "source_url": "texte", "does_not_establish": []}}
```
nenrin_ledger_head≈ 314 tokens
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.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "nenrin_ledger_head", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "source_url": "texte", "does_not_establish": []}}
```
nenrin_resume≈ 393 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- endpoint · string · requis
  https URL of the agent or MCP endpoint, e.g. https://mcp.horizonshield.dev/mcp
Exemple d'appel
```
{"name": "nenrin_resume", "arguments": {"endpoint": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "source_url": "texte", "does_not_establish": []}}
```
nenrin_trust_signal≈ 326 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- endpoint · string · requis
  https URL of the agent or MCP endpoint
Exemple d'appel
```
{"name": "nenrin_trust_signal", "arguments": {"endpoint": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "source_url": "texte", "does_not_establish": []}}
```
nenrin_witness≈ 318 tokens
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.
Paramètres, retour & exemple (1)
Paramètres
- sha256 · string · requis
  64-hex record SHA-256
Exemple d'appel
```
{"name": "nenrin_witness", "arguments": {"sha256": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}], "structuredContent": {"lookup": "ok", "source_url": "texte", "does_not_establish": []}}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://jidec.horizonshield.dev/mcp