Product Hunt Data (Official API)

io.github.brenton-kellerPublished by GitHub account brenton-kellerv0.1.0Updated Oct 7, 2026

Product Hunt launches, votes, makers, comments via the official API. Pay per result.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Queries Product Hunt launch data — products, votes, makers, and comments — through the official API, billed per result.

What you can do
This remote MCP server exposes Product Hunt data retrieved through the official API. According to the registry description, it covers launches, votes, makers, and comments, so an assistant can look up products and the people behind them. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when an assistant needs Product Hunt launch information — for example researching new products, tracking makers, or reviewing votes and comments — without building a direct API integration. It is a hosted endpoint, so nothing runs locally.
Requirements
A remote streamable HTTP endpoint at mcp.apify.com; no packages, environment variables, or headers are declared. The manifest declares no authentication, but the provider is Apify and the description says pay per result, so an Apify account and billing arrangement are likely needed.
Before you install
The description states pay per result, so usage can incur charges; confirm pricing and any spending limits before connecting. No credentials are declared in the manifest, but a hosted third-party service will see the queries sent to it.

Installation

In SourceWeft

  1. Open Product Hunt Data (Official API) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.brenton-keller%2Fproduct-hunt-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "product-hunt-data-official-api": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=brenton8907/product-hunt-data"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.