Skip to main content
Glama
italia

Schema.gov.it MCP Server

Official
by italia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Schema.gov.it MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-dati-it

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying Italy's open data portal (dati.gov.it) via its CKAN API, providing access to thematic categories and datasets.
      149 npm
      MIT

    • datos-gob-es

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and retrieve datasets, publishers, and themes from Spain's national open-data catalogue through keyless MCP tools or HTTP endpoints.
      336 npm
      MIT

    • ontology

      nrwoodpsh
      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

    • CKAN MCP Server

      ondata
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to search, explore, and query any CKAN open data portal through natural language, making public datasets accessible without requiring knowledge of the portal's API.
      20
      696 npm
      59
      MIT

    • istat-mcp-server

      Halpph
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to access and analyze Italian statistical data from ISTAT via natural language queries, supporting dataset discovery, exploration, and data retrieval.
      9
      2
      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.9/5.0

    Scored across 47 tools

    Disambiguation3/5

    Many tools have distinct purposes, but there are several overlapping pairs (e.g., query_sparql vs query_local_ontology vs query_external_endpoint; inspect_concept vs inspect_local_concept). The descriptions help differentiate, but with 47 tools an agent may still struggle to select the correct one.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern with underscores (e.g., list_ontologies, explore_classes). A few names are longer phrases (find_recommended_scheme_for_property), but overall the pattern is predictable.

    Tool Count3/5

    At 47 tools, the count is high for a single server. While the domain is broad (semantic catalog, external endpoints, OKG, territorial codes), many tools are specialized. The count is borderline between 'slightly over' and 'too many' for typical use.

    Completeness4/5

    The tool set covers a wide range: SPARQL execution, ontology/vocabulary/dataset exploration, quality checks, coverage analysis, external endpoint integration, and OKG catalog interaction. Missing reasoning or classification tools, but the surface is largely complete for the stated catalog purpose.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources