Skip to main content
Glama
tb8412

QAE-Claude-mcp-example

by tb8412
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to QAE-Claude-mcp-example

No user-submitted related servers found.

    Related Servers

    • AEGIS Governance

      undercurrentai
      A
      license
      Not graded
      quality
      D
      maintenance
      Quantitative governance gate for AI agents. Six gates (risk, profit, novelty, complexity, quality, utility) return PROCEED/PAUSE/HALT/ESCALATE with confidence scores and hash-chained, tamper-evident audit trails. Generates NIST AI RMF and EU AI Act Annex IV artifacts. 10 MCP tools; local stdio and hosted Streamable HTTP with a free tier.
      MIT

    • agent-sudo-mcp

      Kisyntra
      A
      license
      A
      quality
      A
      maintenance
      Local zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.
      4
      77 PyPI
      5
      Apache 2.0

    • blackwall-mcp

      bluetieroperations-create
      A
      license
      A
      quality
      D
      maintenance
      A pre-action risk gate for AI agents. Your agent calls the forecast tool before any irreversible action — send email, run SQL, make a payment, delete a file — and gets a risk score (0–100) and a GO / CONFIRM / STOP verdict in a few seconds.
      1
      98 npm
      MIT

    • cycles-mcp-server

      runcycles
      A
      license
      A
      quality
      A
      maintenance
      Runtime budget authority for autonomous agents - a set of tools to check, reserve, spend, and release budget before and after every costly, risky operation. The agent asks "can I afford this?" before acting, and reports what it actually used afterward.
      9
      38 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes with no overlap: certify_action evaluates safety for proposed actions, check_budget monitors budget utilization, and get_certification_history retrieves past certifications. Each tool serves a unique function in the safety certification workflow, making selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: certify_action, check_budget, and get_certification_history. The naming convention is uniform throughout, using clear action verbs followed by specific nouns that describe the tool's function.

    Tool Count4/5

    Three tools is reasonable for a safety certification server, covering core operations: certification, budget checking, and history retrieval. While slightly minimal, each tool earns its place, and the count aligns well with the server's focused purpose without being overly sparse.

    Completeness5/5

    The tool set provides complete coverage for the safety certification domain: certify_action handles the primary certification operation, check_budget manages budget monitoring, and get_certification_history offers audit capabilities. This covers the essential lifecycle of certification, budget tracking, and historical review with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources