io.github.AzielEliab/aziel-runtime MCP server: daily status and tool changes

Answered initialize and tools/list on all 10 daily checks recorded in the last 30 days (2026-10-19 to 2026-10-28); 36 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; no tool definition change in 9 compared days; no agent-reported interactions.

Does it respond?

Latest daily check: 2026-10-28: the server answered initialize and tools/list.

Observed days in the last 30: 10
Answered initialize and tools/list: 10
Required authentication: 0
No response: 0
Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 10 observed days. Lowdown checks without credentials.

Did its tools change recently?

No change in tool schemas, descriptions or names across 9 compared days.

What tools does it list?

36 tools on 2026-10-28:

Softwares
chainlock_append
chainlock_recall
chainlock_seal
chainlock_tip
chainlock_verify
decisiongate_check
fraggate_call
fraggate_describe
fraggate_list
fraggate_verify
library_lookup
memory_calibrate
memory_get
memory_observe
memory_recall
memory_resolve
mesh_broadcast
mesh_disable
mesh_enable
mesh_heartbeat
mesh_join
mesh_leave
mesh_nodes
mesh_status
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

MCP Registry declaration

Registry name: io.github.AzielEliab/aziel-runtime
Declared version: 2.0.0-rc1
Status: active
Declared hosts: aziel-runtime.vibelock.workers.dev