Skip to main content
Glama
chrassy

klanex-mcp

by chrassy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to klanex-mcp

No user-submitted related servers found.

    Related Servers

    • toolgate

      Rakshit-gen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call backend tools under per-agent policy, deciding which tools each agent can see, what arguments it may pass, how often it may call, and which writes wait for human approval. It also redacts secrets and PII from tool results, fences untrusted output against injection, and records every call in a hash-chained audit log.
      25 npm
      MIT

    • AgentPay MCP Server

      Rumblingb
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides a trust and governance layer for AI agents, enabling secure API access, credential vaulting, paid execution with human approval, and automatic call resume.
      7 npm
      2
      -

    • sentinel-mcp

      haibaoseal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables governed tool-calling agents with policy decisions, optional human approval, hash-chained audit logging, and deterministic evaluation.
      MIT

    • enterprise-agent-lab

      isaac-dev-ai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.
      1
      -

    • Belay

      Jairogelpi
      A
      license
      Not graded
      quality
      B
      maintenance
      Safe, reversible tool execution for AI agents. It sits between an agent and its tool servers, adding contracts, dry-run planning, policy, approvals, saga execution, and rewind.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_execution fetches execution state, get_usage reports account usage, and replay_execution re-runs a terminal execution. No ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_execution, get_usage, replay_execution. No deviations.

    Tool Count3/5

    Only 3 tools for an execution management platform is on the low end. While focused, typical CRUD operations would benefit from more tools (e.g., create, list, cancel).

    Completeness2/5

    Obvious gaps exist: no tool to create a new execution (only replay), no list/cancel functionalities. The workflow is incomplete for full lifecycle management.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources