Skip to main content
Glama
woonstadrotterdam

io.github.woonstadrotterdam/monumenten

Official

Related Servers

Alternatives to io.github.woonstadrotterdam/monumenten

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying Dutch property context for an address, returning building, energy, neighborhood, environment, heritage, and school data from public registers, with explicit match verification and signals.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language search and exploration of the Dutch WWII Oorlogsbronnen archives, allowing users to query historical documents, photographs, and personal accounts through AI assistants.
      9 npm
      15
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      Enables querying over 3,200 Dutch statutes (AVG, Wetboek van Strafrecht, Burgerlijk Wetboek, etc.) with verbatim, citation-grounded text from official sources, directly from MCP-compatible AI assistants.
      18
      48 npm
      13
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query UK property data including EPCs, sale history, planning, flood risk, council tax, demographics, and more via the Homedata API.
      18
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query the Swiss Federal Register of Buildings and Dwellings (GWR/RegBL) — including building lookups, address geocoding, construction statistics, and housing pipeline analysis — through MCP tools.
      9
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables language models to search and query Statistics Netherlands open data, turning natural-language questions into traceable statistics by discovering tables, resolving codes, and retrieving filtered observations.
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one resolves an address to a verblijfsobject ID, and the other retrieves monumental status for a verblijfsobject. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both tools follow a consistent get_<object>_<attribute> pattern, though the second tool's name (get_verblijfsobject_id) describes the return value rather than the resource attribute, which is a minor deviation.

    Tool Count3/5

    Two tools is on the thin side for a server, but the narrow domain (looking up monumental status by address) makes the count defensible. It is borderline but not unreasonable.

    Completeness3/5

    The two tools form a complete workflow: address → verblijfsobject ID → monumental status. However, there is no direct lookup by verblijfsobject ID, no monument details endpoint, and no support for provinciaal monument lookups, leaving some gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues