Skip to main content
Glama

Related Servers

Alternatives to LHO MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM hosts to query the WikiPathways and AOP-Wiki SPARQL endpoints without guessing their vocabulary, by serving live schema cards, entity resolution, curated example queries, and guarded read-only query execution with repair advice. Each response reports the dataset's release version, date, and licence.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to resolve named entities, retrieve curated Wikidata triples, discover cross-links and inbound relations, and run guarded SPARQL queries against a local Truthy knowledge graph for executive brief enrichment.
      12 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to inspect ontology schemas, search typed objects, and execute read-only SPARQL queries against an RDF triple store.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only analysis of architecture knowledge graphs converted to RDF, including ArchiMate, BPMN, C4/Structurizr, Backstage, and LeanIX models, through profile-gated SPARQL querying, pattern planning, validation, and reproducible evidence bundles.
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Executes SPARQL queries against biological and biomedical RDF databases from the RDF Portal, with additional REST API integrations for bioinformatics resources.
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a fairly distinct role: graph_overview for corpus metadata, test_statistics for numeric answers, list_values for enumerating a dimension, search_terms vs describe_term for ontology lookup vs detail. The main overlap is between graph_overview (which lists valid values of every dimension) and list_values (which lists values of one dimension with counts), so an agent may hesitate between them. Other boundaries are clear.

    Naming Consistency4/5

    All names are lowercase snake_case with two words, which is readable and predictable. However, the convention is mixed: list_values/search_terms/describe_term use verb_noun while graph_overview/test_statistics use noun-first forms. Minor deviation, not confusing.

    Tool Count5/5

    Five tools for a focused domain (aggregate statistics plus ontology lookup over a diagnostic-test graph) is well scoped. Each tool covers a distinct capability: metadata, querying, value discovery, ontology search, ontology description. Nothing feels redundant or missing at the count level.

    Completeness3/5

    The surface covers aggregate querying, dimension discovery, and ontology term lookup, but there is no way to combine two dimensions in one query (e.g., pathogen by country), no trend/time-series tool beyond group_by year, and no record-level or free-form query escape hatch. Agents hitting a cross-tab or raw-record question will hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues