Skip to main content
Glama
malkreide

hn-tech-signal-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to hn-tech-signal-mcp

No user-submitted related servers found.

    Related Servers

    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.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct source and action: HN feed retrieval vs keyword search vs thread reading; arXiv latest vs search; Lobsters hot; GitHub trending; and an aggregate digest. Overlap is minimal, and the aggregate tool is clearly positioned as a convenience rather than a replacement.

    Naming Consistency4/5

    All names use snake_case and mostly follow a source_descriptor convention (hn_, arxiv_, lobsters_, github_). The suffixes vary between verbs and nouns/adjectives (search, discussion, latest, hot), so the pattern is not a strict verb_noun convention.

    Tool Count5/5

    Eight tools is well-scoped for a four-source signal aggregator: three for HN, two for arXiv, one each for Lobsters and GitHub, plus an aggregator. No tool feels redundant or excessive.

    Completeness4/5

    Core workflows are covered: discover recent items per source, search HN and arXiv, read HN discussions, and aggregate across sources. Minor gaps exist (e.g., no keyword search for Lobsters or GitHub beyond hot/trending), but agents can work around them via the digest focus filter.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources