Skip to main content
Glama
mbrummerstedt

secoda-analysis-mcp

by mbrummerstedt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to secoda-analysis-mcp

No user-submitted related servers found.

    Related Servers

    • databricks-mcp

      ChrisChoTW
      A
      license
      C
      quality
      D
      maintenance
      A read-only MCP server that enables users to query Databricks SQL, browse metadata, and monitor Delta Lake tables. It also supports tracking Databricks Jobs, DLT Pipelines, and cluster metrics through natural language interfaces.
      25
      4
      MIT

    • starrocks-mcp

      jason-ung
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server that enables users to query and explore StarRocks databases through AI assistants like Claude. It supports SQL execution, schema discovery, and secure LDAP authentication for data analysis and metadata exploration.
      4
      1
      MIT

    • Secure Schema MCP

      Siddharth-coder13
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that provides AI coding tools with database schema structure (tables, columns, keys, relationships) without exposing row data.
      3
      Apache 2.0

    • mssql-mcp

      dhipskind253
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for Microsoft SQL Server that retrieves connection details from AWS Secrets Manager, enabling database exploration and querying via natural language.
      12
      5 npm
      MIT

    • sqldb-mcp-server

      akrym1582
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that exposes SQL database access to LLMs, supporting multiple database types, compact columnar results, pagination, and file export.
      6
      12 npm
      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.8/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools have distinct purposes, but 'get_resource' and 'retrieve_entity' overlap significantly, both retrieving a catalog item by ID. This creates ambiguity for an agent about which to use.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (e.g., get_collection, list_resources), but 'entity_lineage' and 'glossary' are noun-only names, breaking consistency. The pattern is mostly readable but not uniform.

    Tool Count5/5

    With 12 tools, the set is well-scoped for a data catalog analysis server. It covers listing, retrieval, search, and AI chat without being bloated.

    Completeness4/5

    The tools cover core read operations (list, get, search) and AI chat, but miss a dedicated tool to retrieve a single glossary term by ID. For an analysis server, this is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources