MCP servers · azieleliab

Aziel Runtime MCP server for FragGate catalogue operations with receipts

An MCP server that lists, describes and calls catalogue product operations through one FragGate entry point, and can keep a receipt for each call.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

Aziel Runtime exposes catalogue products (Softwares) over MCP through FragGate, a single executable entry point. Clients list the available products, describe one to choose a slug, then call its operation with fraggate_call. A separate library_lookup tool searches library papers and returns citations. Calls can pass through ChainLock, TemporalLock and ForgeReceipts when a ledger entry is needed. A dry_run option previews a call without writing anything, and a background option returns a running status until a receipt hash exists. Per the publisher, each call can leave a receipt that records the engine digest, slug, operation and where it ran.

Use it when an agent needs to run catalogue product operations over MCP or OpenAPI and keep the receipt that each run returns. The publisher also lists decisiongate_check for testing a short proposal and forgereceipts for issuing a receipt after a completed task.

The public remote endpoint uses Streamable HTTP and needs no API key. It can be added through the Glama listing, which the publisher describes as the primary install page. A terminal CLI provides session open and status commands for local use. The local stdio path requires cloning the repository and is described as a development path.

Limitations and requirements

Write operations require confirm set to true. The Glama hosted Install Server is optional and its usage is metered separately from the Worker usage endpoint. The local stdio path requires cloning the repository and is described by the publisher as a development path.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    Aziel Runtime

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

    v2.0.0-rc1
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026