Aziel Runtime is an MCP server that connects an AI assistant to software catalog discovery and execution tools. Through that connection, an assistant can inspect catalog entries, look up libraries, check registry information, and call supported operations. The service also exposes tools for proposal checks, ledger operations, adaptive memory, and mesh-related work. What is available to call depends on the specific operation and product; some catalog entries cannot be executed through the public endpoint.
What can Aziel Runtime do?
The server groups discovery and execution capabilities around software catalogs. An assistant can inspect available entries, request descriptions, call supported operations, and use verification tools. Library search and proposal checks provide additional ways to look up information and evaluate proposed actions.
- Discover software and inspect catalog descriptions.
- Call supported operations and verify registry entries.
- Search libraries and check proposals.
- Use ChainLock ledger operations, adaptive memory, and mesh-related tools.
- Use operation previews, confirmation-gated writes, background jobs, and receipt-related outputs where supported.
These capabilities do not mean every listed item is executable remotely. Some entries are stubs or local-only, and public execution depends on the operation and product.
How Aziel Runtime connects and authenticates
Aziel Runtime can run as a local stdio MCP server through the project’s CLI packaging, or connect remotely over Streamable HTTP at its public MCP endpoint. Public remote access is described as requiring no API key or OAuth; a runtime token can be configured for protected deployments. The project documents Claude Desktop, Cursor, Grok, ChatGPT GPT Actions, and Venice, and also describes support for other clients that work with MCP or OpenAPI. For hosted calls, payloads are sent to a third-party Worker operated for the project.
Who is Aziel Runtime best for?
Aziel Runtime is suited to people who want an AI assistant to discover and call supported software operations, search libraries, check proposals or registry entries, or use its ledger, memory, and mesh-related tools. The verified information identifies a free open-source option and does not identify a required vendor account or separate vendor service plan. Choose the local stdio route when running the project’s CLI packaging; choose the public remote endpoint when a compatible client should connect over HTTP.
What Aziel Runtime can access and change
The assistant can request catalog descriptions, library lookups, registry verification, and other information exposed by supported tools. It can also invoke supported operations that change state, including ledger-related operations; mutating calls require explicit confirmation or dry-run behavior. Some entries are stubs or local-only and refuse public execution, so access and changes are operation- and product-specific. When using the hosted endpoint, call payloads are sent to the project-operated third-party Worker.
Alternatives to Aziel Runtime
For assistants focused on connecting to other software services, GitHub MCP is an alternative for GitHub-related work, while Supabase MCP Server is an alternative for Supabase-related work. These are adjacent choices when the target service, rather than a general software catalog, determines which MCP server fits the task.
