Skip to main content
Glama
Park & Keep MCP Server
by tresor4k

Related Servers

Alternatives to Park & Keep MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to report what a car hire will really cost at 120+ airports in Europe, the UK and the US, drawing on measured data for second-driver fees, deposits, debit-card acceptance, desk hours and excess-cover prices. Also builds links to live prices for a person's exact dates and needs, ranked by the total they will actually pay.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to query the AppyWay API for UK kerbside parking rules and prices, on-street bays, lines and car parks, controlled zones, local authorities and reference data. All lookups are read-only, covering parking quotes for a time window, operating hours, zone default rules and authority restriction links.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying current and historical retail petrol, diesel, and LPG prices across European countries, comparing prices by week, and checking data coverage.
      141 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for querying parking management systems using natural language and secure SQL. It enables searching for parking locations, retrieving billing configurations, and understanding database schemas through business context tools.
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool answers a different question: what car parks exist at an airport, what a stay costs, and how competitive the local market is. The two 'snapshot' tools share the same underlying index and could be momentarily confused, but the descriptions sharply separate consumer price questions from operator/analyst market questions, and each explicitly cross-references the others.

    Naming Consistency5/5

    All three tools use the same airport_<subject>_<noun> snake_case pattern with no deviations. The suffixes (options, price_snapshot, market_snapshot) are predictable and self-describing.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a narrow, read-only data index where each tool maps to a distinct user intent. Nothing feels padded and no obvious query type is missing from the surface.

    Completeness3/5

    Coverage is reasonable for a read-only price/listing index, but there are dead ends: no way to look up a single named car park's details, no airport/country browse or discovery tool, and no per-operator pricing. Agents asking about one specific lot or an unsupported airport have nowhere to go.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues