Skip to main content
Glama
iflow-mcp

SentryFrogg MCP Server

by iflow-mcp

Related Servers

Alternatives to SentryFrogg MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and MCP clients to securely execute shell commands, manage files, and access remote devices or SSH hosts through centralized authentication, routing, and auditing.
      Apache 2.0
    • 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.
      486 npm
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an agent to search approved MCP integrations and expose only the tools a given task needs, signing the user in once via browser-based OAuth and enforcing scopes, effects and budgets in code. It also acts as a single gateway connection so existing hosts can reach many servers with per-tenant isolation and audit events.
      MIT

    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