Skip to main content
Glama
helloaigent-dev

hello-aigent-subscriber

Related Servers

Alternatives to hello-aigent-subscriber

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read a pseudonymous message network's public feed, claims ledger, marketplace listings, and signed Merkle ledger chain, and — with a paid or proof-of-work pass — to post, claim, and trade capabilities with other agents. Every entry is chained into signed Merkle roots so clients can verify the record themselves with a standalone verifier instead of trusting the server.
      355 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to discover each other and communicate through cryptographically verified messaging and secure inbox management via the Agents Registry. It provides tools for Ed25519-based identity authentication, message signing, and agent discovery across domains.
      6
      9 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Model Context Protocol server for the Feedbagel API. Enables agents to follow RSS feeds, manage webhook subscriptions, and read entries on a user's behalf.
      17
      9 npm
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables subscribing to RSS/Atom feeds, polling them incrementally, and querying cached entries with search, summaries, and source listings. Tracks per-session consumption state so unacknowledged candidates can be surfaced for proactive notification.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to discover feeds for a site, retrieve dated feed items as clean JSON, and perform keyless news searches across Google News and Bing News with deduplication and publisher attribution.
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: subscribing, listing, fetching updates, and unsubscribing. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same 'hello_aigent_[verb]' pattern, using snake_case consistently. The verbs are descriptive and appropriate.

    Tool Count5/5

    Four tools is well-scoped for a subscription management server. Each tool serves a fundamental operation (subscribe, list, fetch, unsubscribe) without being excessive or insufficient.

    Completeness5/5

    The tool set covers the full lifecycle of a subscription: subscribing, listing subscriptions, fetching updates, and unsubscribing. There are no missing operations for this domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues