mesh_status — Aziel Runtime MCP Tool
mesh_status
(mesh status) is one of 36 tools on the
Aziel Runtime
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mesh_status from your client
- Claude Code Aziel Runtime mesh_status run in your project directory
- Claude Desktop Aziel Runtime mesh_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aziel Runtime mesh_status ~/.cursor/mcp.json
- VS Code Aziel Runtime mesh_status .vscode/mcp.json
- Zed Aziel Runtime mesh_status ~/.config/zed/settings.json
- Windsurf Aziel Runtime mesh_status ~/.codeium/windsurf/mcp_config.json
- Cline Aziel Runtime mesh_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aziel Runtime mesh_status ~/.gemini/settings.json
- Grok Aziel Runtime mesh_status .mcp.json (in your project root)
- ChatGPT Aziel Runtime mesh_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Aziel Runtime mesh_status Settings → Connectors → Add custom connector
- LangChain Aziel Runtime mesh_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aziel-runtime https://aziel-runtime.vibelock.workers.dev/mcpOther tools on this server
- runtime_skill
- fraggate_list
- fraggate_describe
- fraggate_verify
- fraggate_call
- decisiongate_check
- library_lookup
- mesh_enable
- mesh_disable
- mesh_join
- mesh_heartbeat
- mesh_leave
- mesh_nodes
- mesh_broadcast
- chainlock_append
- chainlock_tip
- chainlock_recall
- chainlock_verify
- chainlock_seal
- memory_observe
- memory_resolve
- memory_calibrate
- memory_recall
- memory_get
- runtime_software
- runtime_bundle
- runtime_pull
- runtime_run
- runtime_manifest
- runtime_session_open
- runtime_session_policy
- runtime_session_exec
- runtime_session_receipt
- runtime_session_receipts
- runtime_session_close
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.