ai.enyal/enyal

Est-ce que ai.enyal/enyal est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.enyal/enyal » 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

• get_entity≈ 167 tokens

  Get one entity's STRUCTURE by name_hash (SHA-256 of the normalised name). No content.

  Paramètres, retour & exemple (2)

  Paramètres

  • node_id · string · optionnel
    Accepted for compatibility but NOT used yet: the lookup is by name_hash only.
  • name_hash · string · optionnel
    SHA-256 hex of the entity's normalised name. Send it: without it the plan has no entity filter.

  Exemple d'appel

  {"name": "get_entity", "arguments": {"node_id": "texte", "name_hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_entity_content≈ 181 tokens

  Get one entity's DECRYPTED content by name_hash (SHA-256 of the normalised name). Content scope required (403 otherwise).

  Paramètres, retour & exemple (2)

  Paramètres

  • node_id · string · optionnel
    Accepted for compatibility but NOT used yet: the lookup is by name_hash only.
  • name_hash · string · optionnel
    SHA-256 hex of the entity's normalised name. Send it: without it the plan has no entity filter.

  Exemple d'appel

  {"name": "get_entity_content", "arguments": {"node_id": "texte", "name_hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_node_content≈ 202 tokens

  Get a node's DECRYPTED content by name_hash PLUS its connected nodes' content (neighbour depth, default 1; 0–5). Same plan schema as the structure tools. Content scope required (403).

  Paramètres, retour & exemple (2)

  Paramètres

  • name_hash · string · optionnel
    SHA-256 hex of the entity's normalised name. Send it: without it the plan has no entity filter.
  • include_neighbours_depth · integer · optionnel
    How many hops of connected nodes to include, 0-5 (clamped). Default 1.

  Exemple d'appel

  {"name": "get_node_content", "arguments": {"name_hash": "texte", "include_neighbours_depth": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_timeline≈ 226 tokens

  Temporally-ordered STRUCTURE view, optionally filtered by node_type and an ISO8601 date range. No content.

  Paramètres, retour & exemple (3)

  Paramètres

  • node_type · string · optionnel
    Only nodes of this type: entity, concept, decision, person, organisation, event, source or synthesis. Empty = all.
  • valid_to_before · string · optionnel
    Only nodes valid to before this time (ISO 8601). Empty = no upper bound.
  • valid_from_after · string · optionnel
    Only nodes valid from after this time (ISO 8601). Empty = no lower bound.

  Exemple d'appel

  {"name": "get_timeline", "arguments": {"node_type": "texte", "valid_to_before": "texte", "valid_from_after": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_timeline_content≈ 247 tokens

  Temporally-ordered DECRYPTED content view, optionally filtered by node_type + an ISO8601 date range. Same plan schema as get_timeline. Content scope required (403 otherwise).

  Paramètres, retour & exemple (3)

  Paramètres

  • node_type · string · optionnel
    Only nodes of this type: entity, concept, decision, person, organisation, event, source or synthesis. Empty = all.
  • valid_to_before · string · optionnel
    Only nodes valid to before this time (ISO 8601). Empty = no upper bound.
  • valid_from_after · string · optionnel
    Only nodes valid from after this time (ISO 8601). Empty = no lower bound.

  Exemple d'appel

  {"name": "get_timeline_content", "arguments": {"node_type": "texte", "valid_to_before": "texte", "valid_from_after": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• query_memory≈ 436 tokens

  Execute a structured query plan over your encrypted knowledge graph. Returns STRUCTURE ONLY (node_type, name_hash, relationships, chunk_ids, timestamps) — never content. Plan schema: { "entity_filters": [{"node_type": <type>} | {"name_hash": <sha256-hex>}], "edge_filters": [{"relationship": <rel>, "direction": "out"|"in"|"both"}], "temporal_bounds":{"valid_from_after": <ISO8601>, "valid_to_before": <ISO8601>}, "limit": <int <= 200>, "include_neighbours_depth": <0-5> } node_type in {entity, concept, decision, person, organisation, event, source, synthesis}. relationship in {references, contradicts, supports, supersedes, caused_by, related_to, part_of, informed_by, led_to, verifies}. Account scope is enforced server-side; it cannot be set from the plan.

  Paramètres, retour & exemple (2)

  Paramètres

  • plan · object · requis
    The structured query plan (a JSON object): entity_filters [{node_type} | {name_hash}], edge_filters [{relationship, direction out|in|both}], temporal_bounds {valid_from_after, valid_to_before} (ISO 8601), limit (<= 200), include_neighbours_depth (0-5). The schema and the allowed node_type / relationship values are in this tool's description.
  • include_chunks · boolean · optionnel
    Also return the chunk ids behind each node. Default false.

  Exemple d'appel

  {"name": "query_memory", "arguments": {"plan": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• query_memory_content≈ 312 tokens

  Execute a structured query plan and return DECRYPTED memory CONTENT (node names, summaries, properties; edge evidence + endpoint names) alongside structure. SAME plan schema as query_memory. REQUIRES a memory:read:content-scoped token — a structure-only token is rejected (403) by ENYAL. Account scope is enforced server-side; it cannot be set from the plan.

  Paramètres, retour & exemple (2)

  Paramètres

  • plan · object · requis
    The structured query plan (a JSON object): entity_filters [{node_type} | {name_hash}], edge_filters [{relationship, direction out|in|both}], temporal_bounds {valid_from_after, valid_to_before} (ISO 8601), limit (<= 200), include_neighbours_depth (0-5). The schema and the allowed node_type / relationship values are in this tool's description.
  • include_chunks · boolean · optionnel
    Also return the chunk ids behind each node. Default false.

  Exemple d'appel

  {"name": "query_memory_content", "arguments": {"plan": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• render≈ 215 tokens

  Render a structured query as a STRUCTURE-ONLY result set (β = structure; identical shape to query_memory). Reserved for richer rendering when content access (γ) lands.

  Paramètres, retour & exemple (1)

  Paramètres

  • plan · object · requis
    The structured query plan (a JSON object): entity_filters [{node_type} | {name_hash}], edge_filters [{relationship, direction out|in|both}], temporal_bounds {valid_from_after, valid_to_before} (ISO 8601), limit (<= 200), include_neighbours_depth (0-5). The schema and the allowed node_type / relationship values are in this tool's description.

  Exemple d'appel

  {"name": "render", "arguments": {"plan": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_chunk≈ 248 tokens

  Look up one identifier in ENYAL's PUBLIC verification index (relays GET /api/v1/verify/lookup/{id}; no decryption). ENYAL's answer is returned unchanged: `found`, and for a chunk or proof its `anchor_status` with `bsv_tx_id`; for a txid, `chain_status`. `degraded:true` means a source could not be checked (inconclusive, not an absence). ENYAL's route needs no key; calling it through this server still needs your eyl_ bearer, like every tool call. An id that is not a UUID or hex is refused (invalid_id) and nothing is sent.

  Paramètres, retour & exemple (1)

  Paramètres

  • identifier · string · requis
    The id to look up: a chunk, proof or transfer id (UUID), or a BSV transaction id (hex), 8-64 characters.

  Exemple d'appel

  {"name": "verify_chunk", "arguments": {"identifier": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://mcp.enyal.ai/mcp