Index / MCP servers / Aziel Runtime

Aziel Runtime MCP server

Aziel Runtime is a remote MCP server that gives an AI agent 36 tools, among them Softwares, chainlock_append, chainlock_recall. It answers at https://aziel-runtime.vibelock.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 24 September 2026; the last check, on 7 November 2026, succeeded.

Status
Answering
Tools
36
Reliability
4 of 4 checks
Response time
475 ms
Transport
streamable HTTP
Last checked
7 November 2026

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

Description as the publisher wrote it.

The 36 tools Aziel Runtime offers

ToolWhat it does
SoftwaresRead 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 executing that slug
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 to stamp onto a name
Inputs: c, chain, subject, fact, k, confirm
chainlock_recallGrounded 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 not use it for adapti
Inputs: depth, q, c, chain
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 current tips. Do not use i
Inputs: ts, confirm, dry_run
chainlock_tipRead 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 adaptive memory exp
Inputs: c, chain
chainlock_verifyConfirm 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 trusting a recall. Do not u
Inputs: c, chain, require_seal
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 gate check without exe
Inputs: statement, evidence, impact_pos, impact_neg, values, accountable
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 → optional ASE → RoseClock →
Inputs: name, slug, op, payload, background, job_id
fraggate_describeInspect 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 Softwares, fraggate_list,
Inputs: name, slug
fraggate_listList 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_only, or digest statu
fraggate_verifyConfirm 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 listing the registry, d
Inputs: name, slug, digest
library_lookupSearch 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 after Softwares and fra
Inputs: q, op
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 posterior after evidence
Inputs: subject, fact, memory_id, use_case, confirm, dry_run
memory_getRead 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 it for ranked adapti
Inputs: memory_id, id, view
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 before resolve/calib
Inputs: subject, fact, memory_id, use_case, confirm, dry_run
memory_recallRanked 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 grounded stamps. Do not us
Inputs: q, use_case, depth, limit
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 for first observatio
Inputs: subject, fact, memory_id, use_case, outcome, outcome_label
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, publishing video, sending ma
Inputs: sha256, title, product, confirm, dry_run
mesh_disableConfirm 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 not use it for drop
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 rollup. Do not use
Inputs: bearer, confirm, dry_run
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 registration or dropping
Inputs: node_id, presence, heartbeat_mode, tip_hash, prev, confirm
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 not use it for refresh
Inputs: product, node_id, label, presence, heartbeat_mode, confirm
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 mesh_nodes or mesh_stat
Inputs: node_id, confirm, dry_run
mesh_nodesList 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 counts without the roster
mesh_statusRead 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-transfer cite is QNS-CD-1.
runtime_bundleRead 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, hashed registry discove
runtime_manifest[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 skill. Do not use it fo
runtime_pullOpen 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 use it for inspecting
Inputs: slug, product
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 use it for the defa
Inputs: slug, op, payload, session_id, confirm, dry_run
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. Do not use it for ord
Inputs: session_id, id, confirm, dry_run
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 not use it for the
Inputs: session_id, id, slug, product, op, payload
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 it for the default
Inputs: id, source, confirm, dry_run
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 allow_slugs / allow_o
Inputs: session_id, id, allow_slugs, allow_ops, max_payload_bytes, kv_increment
runtime_session_receipt[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 output the user did
Inputs: session_id, id
runtime_session_receipts[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; use runtime_session
Inputs: session_id, id
runtime_skillRead 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 session or choosing the do

Add Aziel Runtime to your AI client

Every block below points at https://aziel-runtime.vibelock.workers.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http aziel-runtime https://aziel-runtime.vibelock.workers.dev/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "aziel-runtime": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://aziel-runtime.vibelock.workers.dev/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "aziel-runtime": {
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "aziel-runtime": {
      "type": "http",
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "aziel-runtime": {
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "aziel-runtime": {
      "serverUrl": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "aziel-runtime": {
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Aziel Runtime
version: 0.0.1
schema: v1
mcpServers:
  - name: Aziel Runtime
    type: streamable-http
    url: https://aziel-runtime.vibelock.workers.dev/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "aziel-runtime": {
      "httpUrl": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "aziel-runtime": {
      "type": "http",
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "aziel-runtime": {
      "url": "https://aziel-runtime.vibelock.workers.dev/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Faziel-runtime.vibelock.workers.dev%2Fmcp&type=streamable_http&id=aziel-runtime&name=Aziel%20Runtime

Is Aziel Runtime up right now?

It answered our last check on 7 November 2026 in 475 ms. Over 4 checks since 24 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Aziel Runtime

Questions about Aziel Runtime

How many tools does Aziel Runtime have?

36, as returned by the server's own tools/list on 14 November 2026: Softwares, chainlock_append, chainlock_recall, chainlock_seal, chainlock_tip, chainlock_verify, decisiongate_check, fraggate_call, and 28 more.

Is Aziel Runtime down?

It answered our last check on 7 November 2026 in 475 ms. Over 4 checks since 24 September 2026 it answered 4.

How do I add Aziel Runtime to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://aziel-runtime.vibelock.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Aziel Runtime need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.azieleliab. Endpoint host: aziel-runtime.vibelock.workers.dev. ARD identifier: urn:air:io.github.azieleliab:mcp:aziel-runtime. First indexed 24 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.