Skip to main content
Glama
pythagraph

Pythagraph RED MCP Server

by pythagraph

Related Servers

Alternatives to Pythagraph RED MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables retrieval and analysis of graph data from the Pythagraph RED API. Provides detailed graph statistics, node/edge distributions, and formatted table outputs for data visualization and analysis.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for AI-powered graph analysis, including relationship extraction, adjacency matrix creation, and network centrality calculations. It enables users to perform complex structural analysis and generate interactive D3.js visualizations from structured data.
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables querying MITRE ATT&CK and D3FEND data efficiently, providing techniques, detections, mitigations, actors, and countermeasures with token-aware summaries and paginated graph traversal.
      10
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Gremlin-compatible graph databases through natural language, supporting schema discovery, complex graph queries, relationship analysis, and data import/export operations.
      13 npm
      9
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs and AI agents to query a biomedical knowledge graph stored in RedisGraph, with tools for concept search, synonym enrichment, and study variable discovery through semantic relationships.
      -

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have distinct purposes: get_graph_data provides detailed, comprehensive graph data, while get_graph_summary offers a concise overview. However, the inclusion of an includeDetails parameter in get_graph_summary could cause some overlap or confusion, as it blurs the line between summary and detailed data retrieval.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_graph_data and get_graph_summary), using snake_case and the same verb 'get'. This makes them predictable and easy to understand, with no deviations in naming style.

    Tool Count2/5

    With only 2 tools, the server feels thin for a graph analysis domain, as it lacks essential operations like creating, updating, or deleting graph data. This limited scope may hinder agents from performing full workflows, making it inappropriate for comprehensive graph management.

    Completeness2/5

    The server is severely incomplete for graph analysis, covering only retrieval operations (detailed and summary). There are significant gaps, such as no tools for creating, modifying, or deleting graphs, which are core to graph lifecycle management and will likely cause agent failures in broader tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues