Skip to main content
Glama

Related Servers

Alternatives to shm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a governance proxy layer for MCP servers, enforcing per-tool allowlists, human approval for write operations, quotas, secret redaction, and a hash-chained audit log of all calls.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enforces default-deny policies, budgets, and tamper-evident audit logging for MCP tool calls before they reach upstream servers.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for regulated enterprises, providing per-tool RBAC, redacted audit logging, and structured error handling. Exposes bank tools for customer lookup, statement search, and dispute resolution over stdio and HTTPS transports.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enforces allow/deny/ask policies on MCP tool calls before they reach downstream servers, with tamper-evident audit logging.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
      Academic Free v1.1

    TDQS

    C2.4/5.0

    Scored across 152 tools

    Disambiguation3/5

    Many tools come in near-duplicate pairs: collection-level and by_key variants of the same action (e.g. admin_config_post vs admin_config_by_key_post, user_storage_manage_put vs user_storage_manage_by_name_put both described as 'Создать данные'). Admin and user specs also mirror each other (admin_service_get vs user_service_get), so an agent must carefully weigh scope to pick correctly.

    Naming Consistency4/5

    Names follow a largely predictable {scope}_{resource}_{path}_{httpverb} snake_case pattern (admin_promo_post, user_otp_delete), which is easy to parse. Minor deviations exist: the meta tools api_search/api_describe/api_status/api_audit_tail break the scheme, and the user CRUD tools drop the resource prefix (user_get, user_post, user_put).

    Tool Count1/5

    152 tools is an extreme count that overwhelms selection and context. It is a raw 1:1 dump of two OpenAPI specs rather than a curated surface, so most tools do not earn individual places in an agent-facing set.

    Completeness4/5

    Because it is auto-generated from full admin and user specs, coverage is broad: CRUD, auth (passkey, OTP, Telegram), payments, storage, templates, and services are all present. Minor gaps may exist around non-exposed endpoints, but no obvious dead ends for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues