Skip to main content
Glama
andreadecorte

GABI MCP Server

by andreadecorte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GABI MCP Server

No user-submitted related servers found.

    Related Servers

    • opentargets-mcp

      nickzren
      A
      license
      B
      quality
      D
      maintenance
      MCP server that exposes the Open Targets Platform GraphQL API as a set of tools for querying biomedical data such as targets, diseases, drugs, and genetic evidence.
      68
      19
      MIT

    • AccelMCP

      t-ogawa-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -

    • mcp-server

      gwanghun-choi
      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

    • mcp-sparql

      daedalus
      A
      license
      A
      quality
      C
      maintenance
      MCP server exposing SPARQL query functionalities for LLMs, enabling query execution, validation, and graph exploration across SPARQL endpoints.
      7
      MIT

    • SentinelScan Cloud MCP Server

      vndpal
      F
      license
      Not graded
      quality
      D
      maintenance
      A remote MCP server that exposes mock application security testing data (applications, scans, issues) for LLM clients to query security posture using natural language.
      -
    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

    B3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one retrieves the database name, while the other executes SQL queries. There is no overlap or ambiguity between them, making it clear which tool to use for each task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_' prefixes (get_db_name and get_query_result). This naming convention is uniform and predictable across the tool set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a database interaction domain. It lacks essential operations like create, update, or delete queries, making it insufficient for typical database workflows. The count is too low for the apparent scope.

    Completeness2/5

    The tool set is severely incomplete for database operations. It only allows retrieving the database name and executing queries, missing critical CRUD operations (e.g., insert, update, delete) and other common functions like listing tables or managing connections. This will cause significant agent failures in handling database tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources