Skip to main content
Glama
jsilvanus

skosmos-mcp

by jsilvanus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to skosmos-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • schema-org-mcp

      Theycallmeholla
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling AI assistants to explore schema.org types, generate JSON-LD examples, validate structured data, and navigate the complete ontology with fuzzy matching and caching.
      21 npm
      21
      MIT

    • wot-mcp

      macc-n
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges Web of Things (WoT) devices to AI assistants via MCP, enabling discovery, monitoring, and control of IoT devices through natural language.
      9
      GPL 3.0

    • RDF4J MCP Server

      odysa
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI-powered exploration of RDF data and SPARQL querying via RDF4J. It provides tools for executing queries, searching knowledge graph resources, and retrieving schema summaries.
      13
      1
      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

    B3.4/5.0

    Scored across 13 tools

    Disambiguation3/5

    Most tools have distinct purposes, but 'get_concept_label' and 'labels' overlap significantly, both retrieving labels for a concept URI. Additionally, 'broader_concepts' and 'traverse_concepts' can be confused since traverse supports broader traversal. This creates some ambiguity for an agent.

    Naming Consistency4/5

    Tool names mostly follow a consistent verb_noun pattern (e.g., list_vocabularies, get_concept, resolve_label). However, 'autocomplete' is a single word and 'concept_path' is noun_noun, breaking the pattern. The overall structure is clear despite these minor deviations.

    Tool Count5/5

    With 13 tools, the server is well-scoped for SKOS vocabulary browsing. It covers listing, searching, detail retrieval, and hierarchy traversal without being overwhelming. The count is appropriate for its purpose.

    Completeness4/5

    The tool surface covers core SKOS operations: vocabulary listing, concept details, labels, hierarchy traversal (broader, narrower, related), and search (autocomplete, full-text, label resolution). Missing are concept creation/modification (likely out of scope) and some non-core features like concept collections, but the browsing workflow is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources