Skip to main content
Glama
iflow-mcp

SentryFrogg MCP Server

by iflow-mcp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to SentryFrogg MCP Server

No user-submitted related servers found.

    Related Servers

    • connect

      grossmargin
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables teams to securely store and retrieve credentials, view decrypted secrets or live OAuth tokens, and connect to third-party MCP servers through a unified MCP endpoint.
      MIT
    • @weave-kit/engine by weavekit

      @weave-kit/engineofficial

      weavekit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to safely operate on PostgreSQL data through typed MCP tools with per-identity RBAC, guardrails, and immutable audit logging.
      1,070 npm
      MIT

    • Aegis

      nithyajangam
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables governing tenant-aware MCP tools with policy enforcement, scoped access, human approval workflows, and tamper-evident audit logging.
      -

    • PgGuard Agent

      vk-ai
      A
      license
      A
      quality
      B
      maintenance
      Enables governed access to corporate Postgres databases via MCP, supporting read-only queries, confirmed data and schema changes, query explanation, audit trail retrieval, and role-based policies with optional Vault secret integration.
      10
      MIT
    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 3 tools

    Disambiguation5/5

    Each tool targets a completely distinct domain: HTTP API calls, PostgreSQL database management, and SSH remote execution. There is no overlap in purpose or functionality, so an agent can clearly differentiate them.

    Naming Consistency5/5

    All tool names follow the pattern 'mcp_<domain>_<role>' (e.g., mcp_api_client, mcp_psql_manager, mcp_ssh_manager), using consistent snake_case and a descriptive prefix. The variation between 'client' and 'manager' is appropriate for their roles.

    Tool Count3/5

    With only three tools, the server covers three broad areas (API, database, SSH). While each tool is rich in sub-actions, the raw count is at the low end of the range, making it borderline but acceptable for a general-purpose server.

    Completeness4/5

    Within the declared domains, the tools provide comprehensive coverage: HTTP client supports all methods, PostgreSQL manager includes full CRUD and schema inspection, SSH manager handles command execution and system info. Minor gaps like bulk operations exist but do not hinder core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources