Skip to main content
Glama
dayplayTeam

Dayplay

Official
by dayplayTeam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Dayplay

No user-submitted related servers found.

    Related Servers

    • @pipeworx/mcp-511-sf-bay by pipeworx-io

      @pipeworx/mcp-511-sf-bayofficial

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve live transit departures, vehicle positions, and service alerts for San Francisco Bay Area transit operators via the regional 511.org open-data API.
      16 npm
      MIT

    • daxoom

      CITROOT
      F
      license
      Not graded
      quality
      F
      maintenance
      The owner-verified local business data + service & menu-price layer for AI agents. Owner-authored business profiles where every response carries provenance — verification level, completeness score, freshness timestamps, and upstream sources. * Search & profiles — find businesses by name, category, city, or geo-radius; full profiles with contacts, hours, media, ratings. * Price layer
      -

    • DataSF MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and retrieve San Francisco open data from data.sfgov.org via the Socrata SODA API.
      246 npm
      MIT

    • G-Guest MCP server

      BlondeDevRules
      A
      license
      A
      quality
      A
      maintenance
      Book a table, an appointment or a place in a class at a real local business. Live availability, instant confirmation, no account and no API key. Eight tools: search, fetch, get_business, check_availability, create_booking, check_booking, cancel_booking and request_listing. Guest emails in eight languages. Hosted at https://g-guest.app/api/mcp
      8
      12 npm
      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

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct resource type: neighborhoods, events, and places. Though get_events and get_places share geographic constraints and filtering by neighborhood, their domain nouns are unambiguous and the descriptions clearly separate them.

    Naming Consistency5/5

    All three tools follow the same get_<plural-noun> naming convention. This is a consistent, predictable pattern with no mixed styles or vague verbs.

    Tool Count5/5

    Three tools is well-scoped for a read-only local discovery service, with each tool covering one core data type. No tool is redundant, and additional tools would likely be unnecessary.

    Completeness4/5

    The server provides neighborhood lookup plus event and place discovery, which covers the core read-only domain. Minor gaps exist, such as no explicit category enumeration or individual detail-fetch tool, but filtered queries should handle most typical requests.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources