Skip to main content
Glama
io.github.benjamin-di/earnings-watch

io.github.benjamin-di/earnings-watch

by benjamin-di

Related Servers

Alternatives to io.github.benjamin-di/earnings-watch

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Normalizes and serves corporate events (earnings, dividends, splits, M\&A) from US, UK, Canada, and Australia via a programmatic MCP API.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides access to financial market data via the Finnhub API, focusing on earnings calendars. It allows users to retrieve historical and upcoming earnings announcements including EPS and revenue data.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to look up public company earnings dates and reporting windows by providing identifiers like ticker, domain, or CIK. It returns fiscal year end, next reporting date, and an outreach window, helping plan investor communications.
      5
      230 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides macro-economic event data, earnings reports, and market overviews as MCP tools, enabling AI agents to query calendars, check event proximity, and assess trade safety.
      57 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search licensed news, regulatory filings, earnings call transcripts, broker research and private documents with inline citations, and to retrieve company, country, market, ETF, sentiment and portfolio tearsheets, screens and an events calendar.
      2
      -

    TDQS

    B3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct role: events, upcoming dates, documents, change feed, watchlist, follow/unfollow, calendar planning/acknowledgment, and status. The read-only public-data tools are clearly separated by resource, and the write tools are clearly separated by action. No two tools appear to do the same thing.

    Naming Consistency3/5

    All tools use the same earnings_ prefix and snake_case, which keeps them readable. However, the suffix conventions are mixed: get_events is verb_noun, upcoming/documents/changes/watchlist/status are noun-oriented, and watch/unwatch/calendar_plan/calendar_ack mix action and object styles. The pattern is understandable but not consistently verb_noun.

    Tool Count5/5

    Ten tools is a well-scoped set for an earnings-watch service. It covers reads, follows, change tracking, calendar coordination, and status without obvious redundancy. Each tool appears to earn its place.

    Completeness4/5

    The surface covers the core lifecycle: upcoming dates, events, documents, change feed, watchlist, follow/unfollow, calendar plan/ack, and status. Minor gaps may exist around explicit event search/filtering or calendar cancellation, but agents can likely work around them. Overall coverage is strong for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues