Awesome Indie MCP server

Which servers in the official MCP registry are Awesome Indie's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-17

← Back to Awesome Indie

Whose server it is

Registry namecom.awesomeindie/mcpverified in the MCP registry

The registry name sits under awesomeindie.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-17

Stateanswerschecked 2026-10-17
Tools9
Server calls itselfawesomeindie
Server version1.0.0
Protocol version2025-06-18

On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 180 ms.

Tools it offers9 tools · read 2026-10-17

search_products
Search the Awesome Indie directory of launched indie/micro-startup products by keywords. Returns matches ranked by relevance and upvote score.
get_product
Fetch one product listing by its slug: tagline, description, maker, categories, upvotes and launch date.
get_todays_launches
The products launching on Awesome Indie today (UTC), in ranking order.
get_top_products
The ranked products for a period. Without a slug, the current period is a rolling window (last 1/7/30/365 days), exactly like the site. With a slug, an archived calendar period: daily "2026-08-06", weekly "2026-08-03" (a Monday), monthly…
list_categories
Every product category in the directory, most-populated first. Product counts are a periodic snapshot, not live.
get_maker
A maker profile by username: bio, links, streak, followers and their launched products.
get_launch_availability
When a product submitted today would launch: the free-queue window, and the paid "Skip the Line" slots that let a launch be booked for a specific day.
get_community_posts
The most recent posts from the Awesome Indie community feed.
get_article
Read one community article (markdown body) by its author username and article slug.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "awesomeindie": {
      "type": "http",
      "url": "https://awesomeindie.com/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.