Skip to main content
Glama
Sign In
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

    • Relay

      previdus
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables governed agent access to tools by routing and authorizing MCP requests through configurable policies, credential-bound upstream connections, human approval workflows, and an administration console.
      MIT

    • mcp-session-gateway

      jaeseongs95
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agent sessions to reach a database through MCP with per-session, human-approved access grants, exclusive leased pool credentials, and revocable, auditable operations. It can be deployed locally or remotely with passkey-verified session administration.
      Apache 2.0

    • 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

    • Gate22

      stewart137
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables teams to onboard remote MCP servers, enforce function-level permissions and credential modes, and let developers expose permitted tools through a unified MCP endpoint with search and execute functions while auditing usage.
      MIT

    • Remote Runtime

      weimin96
      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
    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