Skip to main content
Glama
vicentesiis

espaciarte-mcp

by vicentesiis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to espaciarte-mcp

No user-submitted related servers found.

    Related Servers

    • @terranode-co/mcp-server by terranode-co

      @terranode-co/mcp-serverofficial

      terranode-co
      A
      license
      A
      quality
      D
      maintenance
      MCP server for spatial queries via the Terranode Geospatial API, enabling AI agents to perform point-in-polygon lookups, nearest feature search, distance calculations, and spatial joins.
      6
      35
      MIT

    • geocontext

      mborne
      A
      license
      Not graded
      quality
      F
      maintenance
      An experimental MCP server providing spatial context for LLMs by interfacing with French Geoplateforme services. It enables tasks such as geocoding, altitude lookups, and querying administrative, cadastral, or urban planning data.
      11
      4
      MIT

    • geopera-mcp

      geo-pera
      A
      license
      C
      quality
      D
      maintenance
      MCP server for the Geopera geospatial data platform that enables AI agents to discover imagery, place and manage orders, and run analytics using the same API as other Geopera clients.
      100
      MIT

    • SpaceTraders MCP Server

      TheValverde
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to interact with the SpaceTraders API, managing agents, fleets, contracts, and trading operations in the SpaceTraders universe.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one searches for spaces with filtering, while the other retrieves full details for a specific space. There is no overlap or ambiguity in their intended use.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (search_spaces, get_space_details). Though the verbs differ, the structure is predictable and readable.

    Tool Count3/5

    With only 2 tools, the server feels minimal but not absurdly thin. The scope appears to be read-only space exploration, and these two tools cover the primary needs, though more operations could be expected.

    Completeness4/5

    For a public-facing space discovery API, the combination of search and detail retrieval covers the core use case. Missing operations like booking or creating are outside the apparent purpose, so no critical gaps are evident.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources