Aziel Runtime is answering right now. Last checked 1 min ago. It exposes 36 tools. Last commit 15 Oct 2026.
Governed MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 September 2026. No other catalogue keeps this.
We read the source, 1 d ago · tools taken from the live server · rules ccca72095570
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const MALWARE = /meterpreter|rm -rf \/|TVpQAA|#!\/bin\/sh/i;
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
if (this.kv && typeof this.kv.delete === "function") {
await this.kv.delete(this.prefix + chainKey(n));
const child = spawn(process.execPath, [jail], { stdio: ["pipe", "pipe", "pipe"] });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Aziel Runtime and you get told the day something new turns up.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
claude mcp add aziel-runtime --transport http https://aziel-runtime.vibelock.workers.dev/mcp
{
"mcpServers": {
"aziel-runtime": {
"url": "https://aziel-runtime.vibelock.workers.dev/mcp"
}
}
}
[mcp_servers.aziel-runtime]
url = "https://aziel-runtime.vibelock.workers.dev/mcp"
{
"mcpServers": {
"aziel-runtime": {
"url": "https://aziel-runtime.vibelock.workers.dev/mcp"
}
}
}
{
"mcpServers": {
"aziel-runtime": {
"url": "https://aziel-runtime.vibelock.workers.dev/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
runtime_bundle
runtime_manifest
runtime_pull
runtime_run
runtime_session_close
runtime_session_exec
runtime_session_open
runtime_session_policy
runtime_session_receipt
runtime_session_receipts
runtime_skill
mesh_broadcast
mesh_disable
mesh_enable
mesh_heartbeat
mesh_join
mesh_leave
mesh_nodes
mesh_status
chainlock_append
chainlock_recall
chainlock_seal
chainlock_tip
chainlock_verify
memory_calibrate
memory_get
memory_observe
memory_recall
memory_resolve
fraggate_call
fraggate_describe
fraggate_list
fraggate_verify
decisiongate_check
library_lookup
Softwares
Tools this server used to expose. Anything built against them stopped working on the day they went.
runtime_software
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://aziel-runtime.vibelock.workers.dev/mcp | streamable-http | answering | 650 ms | 1 min ago |
MCP compliance proxy between agent and tools: deterministic governance, fail-closed, audit trail.
Fail-closed deterministic checks and hash-chained receipts for AI agent outputs via MCP.
Deterministic JSON checks with signed evidence and x402-paid execution
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Deterministic runtime enforcement of step order for AI agents: ALLOW/DENY before a step runs.
Governance runtime for AI agents with signed provenance, compliance audits, and OSINT.
Read-only CharacterCheck MCP server for deterministic character context with provenance and trust.
Deterministic pre-execution audit for trading agents. PASS/WAIT/FAIL, reproducible verdict_hash.
Answers built from our own checks of this server.