Skip to main content
Glama
AzielEliab

aziel-runtime

by AzielEliab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to aziel-runtime

  • mcp-nexus

    fyrlabs
    A
    license
    A
    quality
    A
    maintenance
    Enables AI harnesses to connect to a single MCP endpoint that routes to multiple downstream MCP servers, discovering and executing capabilities on demand while keeping tool schemas out of context.
    4
    13 npm
    Apache 2.0

  • trades-runtime

    AzielEliab
    A
    license
    A
    quality
    B
    maintenance
    Private TypeScript runtime for a shadow-first AI operating system and company operating intelligence layer for HVAC, plumbing, electrical, sewer, and cross-trades businesses.
    4
    1
    Apache 2.0

Related Servers

  • MCP Nexus

    dsk-dev-ai
    A
    license
    Not graded
    quality
    A
    maintenance
    Provides a single MCP endpoint that dynamically discovers, routes, policy-checks, and executes hundreds of MCP tools from any agent, with optional LLM-based routing.
    10 npm
    1
    Apache 2.0

  • MCP Gateway

    mustforgiverHer
    A
    license
    Not graded
    quality
    B
    maintenance
    Exposes scattered business REST APIs and read-only databases to AI clients through a single MCP endpoint with unified API-key authentication, service- and operation-level authorization, department-scoped filtering, masking, and audit logging. AI agents discover only the tools and data they are permitted to use, without needing to know endpoint addresses, SQL, or credentials.
    MIT

  • ContextForge

    jetwind
    A
    license
    Not graded
    quality
    C
    maintenance
    Federates MCP, A2A, and REST/gRPC APIs with centralized governance, discovery, and observability, optimizing agent and tool calling with plugin support.
    Apache 2.0

  • MCP Proxy Server

    rberg59762
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables clients to connect through a unified MCP endpoint that aggregates and routes requests to multiple backend MCP resource servers, exposing their combined tools and resources with optional authentication and management.
    105 npm
    MIT

  • Relay

    adarshp14
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
    2 npm
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4/5.0

Scored across 36 tools

Disambiguation3/5

The tools span distinct subsystems (mesh, ChainLock, AKM memory, FragGate, raw sessions), and descriptions explicitly cross-reference alternatives. However, multiple exec doors (fraggate_call, runtime_run, runtime_session_exec) and parallel recall/append paths (chainlock_* vs memory_*) create real misselection risk despite the verbose warnings.

Naming Consistency3/5

Most tools follow a snake_case prefix_action pattern (mesh_join, chainlock_append, runtime_session_open). Deviations exist: 'Softwares' is capitalized and noun-only, and runtime_* mixes verbs and nouns (runtime_run, runtime_bundle, runtime_manifest). Mixed but still largely readable.

Tool Count2/5

36 tools is well above the 3–15 sweet spot and exceeds the 25+ threshold for 'too many'. While the server covers many subsystems, the surface is sprawling and includes redundant advanced/internal doors.

Completeness4/5

Core lifecycles are covered: session open→policy→exec→receipt→close, mesh join/heartbeat/leave/status, ChainLock append/tip/recall/verify/seal, memory observe/resolve/calibrate/recall/get. Minor gaps exist (e.g., mesh_disable is a refuse rather than a real off switch, no delete paths by design), but agents can work around them.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources