Skip to main content
Glama

Related Servers

Alternatives to nyc-restroom-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to search and read over 2,400 New York City public datasets through the Socrata SODA API, with ready-made tools for restaurant health inspections and 311 service requests plus general dataset discovery and querying.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query a time-aware map of New York City's public defibrillator locations, including which are open at a given hour, and to analyze custom lists of places with opening hours. Also exposes coverage rankings for proposed 24/7 cabinet placements.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying NYC Open Data datasets using natural language, with tools to search datasets, run SoQL queries, and retrieve metadata, all without an API key.
      691 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to find nearby public places such as pharmacies, supermarkets, gas stations, EV chargers, libraries, and post offices, with attributed opening-hours data from OpenStreetMap.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access public NYC renter guides and neighborhood asking-rent data, and with scoped OAuth consent, read and manage a renter's apartment alerts, saved searches, tracked listings, and Housing Lottery application statuses. Public tools are read-only, while personal tools act only on the connected renter's account with write confirmations.
      MIT

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: find_restrooms discovers restrooms by proximity and open status, while get_restroom_status looks up a single restroom's detailed condition. No overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun snake_case pattern: find_restrooms and get_restroom_status. This is perfectly predictable.

    Tool Count3/5

    With only 2 tools, the server sits at the borderline lower end of the scale. The narrow domain could justify it, but the small surface area feels thin compared to typical MCP servers.

    Completeness4/5

    The two tools cover the essential workflow of finding restrooms and checking their status. A few minor gaps exist, such as no way to list all restrooms or filter by amenities, but these are not core dead ends for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues