Agents Index

Aziel Runtime

Online

Governed MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution.

Visit publisherConnectJSON

What it can do: 36 tools

  • runtime_skill read-onlyRead the agent how-to (one door — discover, route, refuse; pipeline fraggate_list → fraggate_describe → fraggate_call). This is playbook markdown, not a catalog and not a machine manifest. Use this when starting a sessio
  • fraggate_list read-onlyList hashed FragGate names and digests after Softwares so you can discover names. Discovery first — not the Softwares catalog and not exec. Use this when Softwares already returned a slug and you need live, stub, local_o
  • fraggate_describe read-onlyInspect one FragGate card for the slug you picked from Softwares (live vs stub vs local_only, public ops, engine_digest). Not execute and not a digest-only proof. Use this when you already have a name or slug from Softwa
  • fraggate_verify read-onlyConfirm a name, slug, or 64-hex engine_digest against the hashed FragGate registry — a proof, not a card listing. Use this when you must prove a listed name or digest exists after fraggate_describe. Do not use it for lis
  • fraggate_callExecute the slug you picked from Softwares through the FragGate single door (CallEnvelope → FragGate → Lamb Lens → SweepGate → Sentinel → Provenance → ChainLock-IN → DecisionGATE → AZPIPE → Internal Domain Layer → option
  • decisiongate_checkRun the named DecisionGATE five sequential gates on a proposal (Freedom without clarity is chaos) without executing a catalog product. Also runs automatically inside fraggate_call before exec. Use this when you want a ga
  • library_lookup read-onlySearch the Aziel Digital Library for papers and cites (aziel-corpus search, example, or skill) — cites, not beliefs and not vault stamps. Use this when you need a library paper, cite, example record, or library skill aft
  • mesh_status read-onlyRead QNM suite rollup totals (enabled?, bearers, nodes = human mesh users + cited human uses, live_nodes = human mesh users + site_live_viewers, software_nodes = {slug}-worker roster) — not the node roster. Packet-transf
  • mesh_enableDeclare an extra QNM suite bearer (POST /v1/mesh/enable) — additive presence, not a first-time on-switch. Use this when an operator wants to declare an additional bearer (example: suite-presence) on top of the default-on
  • mesh_disable read-onlyConfirm that read-only QNM suite-presence stays ON (POST /v1/mesh/disable refuses MESH-DISABLE-REFUSED) — not a kill switch. Use this when a client still posts the historical disable route and needs the honest refuse. Do
  • mesh_joinRegister one product node into the QNM rollup (POST /v1/mesh/join) — first presence, not a TTL refresh. Use this when transmission radios are LIVE and a catalog product should appear in live/locked/isolated counts. Do no
  • mesh_heartbeatBeat one registered node (POST /v1/mesh/heartbeat) — restores live from stale; not a first join. Use this when you already have a node_id from mesh_join and transmission radios are LIVE. Do not use it for first-time regi
  • mesh_leaveDrop one node from the QNM rollup (POST /v1/mesh/leave) — not a suite-wide radio off. Use this when a previously joined node should leave the counts. Do not use it for turning suite-presence off or listing nodes; use mes
  • mesh_nodes read-onlyList the QNM node roster (node_id + presence_class; durable rows stay, {slug}-worker keeps a 5-minute TTL) — not suite totals. Use this when you need the current node list after mesh_status. Do not use it for suite count
  • mesh_broadcastRegister the SHA-256 of a local file as a hash receipt — never a publish or upload path. Use this when the operator already holds a local file and wants only its hash recorded. Do not use it for uploading bytes, publishi
  • chainlock_appendAppend one fact-bearing stamp to a local ChainLock chain (CL-WP-0.4). Grounded write — not a tip read, not AKM observe, not a LOCKSET seal. Fabric, not Softwares-tab. No Node Gate. Use this when you have a concrete fact
  • chainlock_tip read-onlyRead only the live tip card of one local ChainLock chain — not depth recall and not LOCKSET verify. Use this when you need the current tip of a named chain. Do not use it for depth-0–5 grounded recall, LOCKSET verify, or
  • chainlock_recall read-onlyGrounded ChainLock recall at depth 0–5 (id+h+fh facts or refuse=no-stamp). Stamped vault facts — not Bayesian rank and not tip-only. Use this when you need stamped facts from the local vault, not a Bayesian ranking. Do n
  • chainlock_verify read-onlyConfirm fail-closed integrity of ChainLock chains and LOCKSET (LS-WP-0.1): broken prev, tip drift, missing GodLock cite. Integrity check — not a new seal. Use this when you must prove local chain integrity before trustin
  • chainlock_sealWrite a new local LOCKSET over live chain tips (members {c,id,h,fh} + TemporalLock + GodLock cite, LS-WP-0.1). Not a raw-session close and not verify-only. Use this when the operator wants a new local lockset over curren
  • memory_observeAppend the first memory_observation to the ChainLock learn chain (AKM-TRIAD-1.0). New fact in — not an outcome resolve and not a grounded ChainLock append. Posterior ≠ truth. Use this when you have a new fact to observe
  • memory_resolveAppend a memory_resolution outcome on an already-observed memory (AKM-TRIAD-1.0). UNKNOWN is distinct from MISS. Does not rewrite history. Use this when an observed memory_id or subject now has an outcome. Do not use it
  • memory_calibrateCalibrate one memory with the deterministic 3-of-4 triad plus Bayesian posterior (AKM-TRIAD-1.0). Writes a LEARN stamp — not a ranked search and not an explain view. Use this when an observed memory should receive a post
  • memory_recall read-onlyRanked adaptive recall after ChainLock verify (AKM-TRIAD-1.0). Belief list — not raw grounded stamps, not a public corpus cite, not one-id explain. Use this when you want a ranked belief list after verify, not raw ground
  • memory_get read-onlyRead one memory's stored explanation (node, history, or calibration: posterior, triad legs, effective N, Brier) — not a ranked list. Use this when you have a memory_id (or id) and need the stored explanation. Do not use
  • Softwares read-onlyRead the Softwares catalog and pick a slug (first call). Not the hashed live/stub registry. Use this when an agent starts, or a hub refreshes the Software tab, and a slug is needed before fraggate_call. Do not use it for
  • runtime_bundle read-onlyRead a compact bootstrap of every product skill URL and invoke prefix — not Software-tab cards and not the hashed registry. Use this when a client needs skill URLs in one shot. Do not use it for Software-tab refresh, has
  • runtime_pull read-onlyOpen one hub product card by slug (name, version, skill, download, ops) — not FragGate live/stub status. Use this when you already have a slug from GET /v1/software or fraggate_list and need the card, not exec. Do not us
  • runtime_run[advanced/internal] Advanced exec façade: admit a slug+op (still DecisionGATE-admitted) and run it through a raw session. Not the default door. Use this when you were explicitly asked for the raw runtime_run path. Do not
  • runtime_manifest read-only[advanced/internal] Read the machine runtime manifest JSON (version, role, door=fraggate, engine slugs, registry_digest) — not the human how-to. Use this when a client needs the machine manifest rather than the human ski
  • runtime_session_open[advanced/internal] Open a raw session object (session.id). First step of open → policy → exec → receipt(s) → close. Not the default exec path. Use this when you were explicitly asked for raw session plumbing. Do not use
  • runtime_session_policy[advanced/internal] Attach allow rules on an already-open raw session (allow_slugs / allow_ops). Policy overlay — not open and not exec. Identity remains Aziel Eliab. Use this when an already-open session needs tighter a
  • runtime_session_exec[advanced/internal] Raw session exec on an already-open session_id (FragGate-admitted). Not fraggate_call and not runtime_run auto-open. Use this when you already have a session_id and were asked for raw session exec. Do
  • runtime_session_receipt read-only[advanced/internal] Read the last receipt only for a raw session — not the full chain. Use this when the user asked for the latest receipt on an open or sealed session. Do not use it for the full receipt chain or product
  • runtime_session_receipts read-only[advanced/internal] Read the full receipt chain for a raw session — not the last receipt only. Use this when the user asked for the whole receipt chain. Do not use it for only the last receipt or ordinary product output;
  • runtime_session_close[advanced/internal] Seal a raw session so further exec or policy on that session_id is rejected. End of the raw lifecycle — not a LOCKSET seal and not a FragGate call. Use this when the user asked to close the session. D

Connect it

Claude Code
claude mcp add --transport http aziel-runtime https://aziel-runtime.vibelock.workers.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://aziel-runtime.vibelock.workers.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "aziel-runtime": {
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "aziel-runtime": {
      "type": "http",
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}

Questions

What does Aziel Runtime do?

Governed MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution. It exposes 36 tools to AI assistants.

What tools does Aziel Runtime provide?

36 tools, including runtime_skill, fraggate_list, fraggate_describe, fraggate_verify, fraggate_call, decisiongate_check, library_lookup, mesh_status, mesh_enable, mesh_disable, mesh_join, mesh_heartbeat….

How do I connect Aziel Runtime to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://aziel-runtime.vibelock.workers.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Aziel Runtime require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Aziel Runtime online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Aziel Runtime?

@AzielEliab on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Memory & RAG