Skip to main content
Glama
AIwithhassan

Scoped Support Tools Server

by AIwithhassan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Scoped Support Tools Server

No user-submitted related servers found.

    Related Servers

    • SecureAgentServer

      bhargavlukka
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure support-ticket and customer-account operations with signed JWT authentication, prompt-injection and tool-poisoning guardrails, and human-in-the-loop confirmation for destructive actions.
      MIT

    • Broker

      Abhishekvoid
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to securely perform privileged actions like creating GitHub issues by minting short-lived, single-purpose tokens on demand, with policy enforcement and audit logging.
      MIT

    • agent-trust-firewall

      krishnashahane
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely invoke tools by enforcing identity proof, capability verification, and risk scoring on every request, blocking unsafe calls before they execute.
      MIT

    • MCP Customer Support Example

      odelvalle
      A
      license
      A
      quality
      B
      maintenance
      Simulates a multi-tenant customer support backend with tools for profile, order, ticket, and refund management, demonstrating security controls like tenant isolation, role-based access, and input validation.
      6
      MIT

    • SecureMCP Agent Hub

      sgt-9304
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.
      -
    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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct resource/action: customer lookup, listing, order ID retrieval, refund processing, product info, and a generic answer fallback. The only potential overlap is answer_user_query, but its purpose as a canned-response fallback is clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., process_refund, get_order_id, list_customers). No mixed conventions or unclear verbs.

    Tool Count5/5

    With 6 tools, the server is well-scoped for a support-focused toolkit. The number is reasonable and each tool has a clear role without unnecessary redundancy.

    Completeness4/5

    Core support workflows are covered: customer lookup, product info, order ID retrieval, refund processing, and generic canned answers. Minor gaps exist (e.g., no order detail retrieval beyond ID), but these can be worked around with the existing tools.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources