Skip to main content
Glama
EvanSener

snw-derived-mcp

by EvanSener

Related Servers

Alternatives to snw-derived-mcp

No user-submitted related servers found.

    Related Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables semantic search and exploration of a business glossary knowledge graph, allowing users to query terms, expand related concepts, trace dependencies, and resolve physical table mappings.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to inspect ontology schemas, search typed objects, and execute read-only SPARQL queries against an RDF triple store.
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to perform controlled enterprise data queries through semantic intent, with runtime validation of statistics, filters, granularity, permissions, and physical bindings. Exposes tools like semantic_query for safe, fail-closed access to data horizons and capabilities.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of SQL databases and REST APIs through the MCP protocol, grounded in a semantic layer.
      2,824 npm
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a read-only PostgreSQL SQL surface for LLM agents via MCP, with defense-in-depth security layers for safe database queries.
      135 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible agents to run governed, read-only analytics queries against Postgres using predefined metrics and dimensions, with safety checks and provenance on every result.
      20 npm
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: object type enumeration, graph neighborhood exploration, execution, analysis/planning, creation, and listing. There is no meaningful overlap that would cause an agent to confuse one tool with another.

    Naming Consistency5/5

    All tools share a consistent snw_ prefix and follow a clear verb_noun pattern. The minor singular/plural variation (derived_property vs derived_properties) is standard and does not create confusion.

    Tool Count5/5

    Six tools is well-scoped for the derived-property workflow. Each tool covers a distinct step in the lifecycle without unnecessary redundancy or bloat.

    Completeness4/5

    The server covers exploration, analysis, execution, creation/replacement, and listing of derived properties. The only notable gap is the lack of an explicit delete/drop operation, though replace_existing covers updates and the core workflow is otherwise complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues