Skip to main content
Glama
Sign In
earlyon-mcp

earlyon-mcp

by anaqi-blvl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to earlyon-mcp

No user-submitted related servers found.

    Related Servers

    • calendar-mcp

      jbeker
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to calendar events from iCal feeds, enabling agents to query schedules, search events, and check availability via natural language.
      AGPL 3.0

    • OpenAgenda MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search event calendars by keyword and list upcoming or date-filtered events from a chosen calendar, returning titles, dates, venues, coordinates, and keywords.
      349 npm
      MIT

    • Countdowns Online MCP

      Rocniubi
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to retrieve verified countdown event dates, semantics, and FAQ from Countdowns Online, allowing users to browse event categories and understand date contexts without API keys.
      2
      MIT

    • br.com.oiair/marketplace

      makeev11
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search current public children's activities in Florianópolis, Brazil, read organization profiles and their published groups with schedules and prices, and obtain a canonical link for requesting a visit. All five tools are read-only, publicly accessible over Streamable HTTP with no API key, and never submit a request or confirm a booking.
      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

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct: search_events handles name/place/topic lookup, get_event_details handles a single occurrence, and the metadata tools (get_status, get_closures, get_registrations, get_recent_changes) each target a unique resource. The only mild overlap is the temporal-listing trio get_events (one day), get_week (one week), and get_events_range (arbitrary range), which an agent could plausibly confuse, though the descriptions make the granularity difference explicit.

    Naming Consistency5/5

    All 11 tools use snake_case verb_noun form (get_events, list_program_types, search_events, refresh_now, etc.). The get_/list_/search_/refresh_ prefixes map predictably to retrieval vs enumeration vs query vs action.

    Tool Count5/5

    Eleven tools is well within the sweet spot and each one covers a distinct retrieval shape (day, week, range, search, detail, metadata, maintenance). No tool feels redundant enough to remove.

    Completeness4/5

    The read surface is thorough for a scraped program-schedule domain: date-scoped listings, search, details, closures, registrations, change history, freshness status, and a manual refresh. Minor gaps remain — list_program_types returns categories with counts but there is no way to fetch events filtered by program type, and no venue/location listing tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources