A
licenseNot graded
qualityB
maintenanceEnables AI agents to access Product Hunt data via GraphQL API, including posts, products, and rankings. Part of the Pipeworx MCP gateway.
209 npm
MIT
Product Hunt Launches Feed MCP Server
by mambalabsdev
Related Servers
Alternatives to Product Hunt Launches Feed MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search new software launches, read product pages, find alternatives, and follow daily rankings from inside a chat using public read-only data.10MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to fetch and analyze Product Hunt trending products over 1-4 week periods, generating trend reports, top product lists, and category insights via MCP tools.-
LaunchOnIt MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to search launched software products, inspect weekly leaderboards and Hall of Fame winners, check upcoming launch calendar availability, and retrieve full product details. It can also draft a new product listing from a supplied URL, returning a private review link without publishing or charging.61MIT- AlicenseBqualityDmaintenanceProvides access to Product Hunt data via the Product Hunt API v2, enabling queries for posts, collections, users, topics, comments, goals, and maker groups.17127 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Product Hunt data, including launches, post details, comments, topic search, and user profiles, through MCP tools over Streamable HTTP.MIT
TDQS
A4.6/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose (fetch Product Hunt launch rows for chosen days with filters) is stated unambiguously in the description.
Naming Consistency5/5
The single name get_product_hunt_launches follows a clear verb_noun snake_case convention. With one tool there is no risk of mixed conventions, and the name is self-describing.
Tool Count4/5
The domain is a single read-only feed operation, and the one tool absorbs filtering, topic/keyword/vote thresholds, and incremental 'only_new' behavior, so it genuinely earns its place rather than being a trivial wrapper. It is still a one-tool surface, which feels thin if consumers later want per-product detail or comment retrieval.
Completeness4/5
For a feed reader the surface is largely complete: daily rows, maker metadata, links, topic/keyword/vote filters, incremental runs, and error reporting with run IDs. Minor gaps remain around deeper per-launch detail (e.g., comment bodies or multi-day historical backfill beyond the picked days), but core read workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues