Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Awesome Indie

REMOTE · AWESOMEINDIE.COM

Search indie product launches, rankings and makers, and submit your own, on Awesome Indie.

Available components

0 this week 90 Trust /100

Last scanned (18 hours ago)

Scores higher than 97% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 635 tokens (~63/item across 10 items; 9 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Nov 26 0
    • Tool “get_launch_availability” rewrote its description, which is the text the model reads security
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
    • Tool “get_launch_availability” rewrote its description, which is the text the model reads security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 0
    • Tool “get_launch_availability” rewrote its description, which is the text the model reads security
  • 30 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://awesomeindie.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=awesomeindie.com CN=WE1,O=Google Trust Services,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA256 ef99fae70f29ea15131d2618cd561952
SANs: awesomeindie.com, *.awesomeindie.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of awesomeindie.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
awesomeindie.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://awesomeindie.com/api/mcp Verified 200
http (plaintext) http://awesomeindie.com/api/mcp HTTPS enforced 301 https://awesomeindie.com/api/mcp
MCP tools · 9 exposed · ~479 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_article ~51

Read one community article (markdown body) by its author username and article slug.

NameTypeReqDescription
slugstringyesThe article slug from its URL
usernamestringyesThe author username, without the @

No output schema declared.

No examples provided.

get_community_posts ~37

The most recent posts from the Awesome Indie community feed.

NameTypeReqDescription
limitinteger–How many posts to return (default 20)

No output schema declared.

No examples provided.

get_launch_availability ~44

When a product submitted today would launch: the free-queue window, and the paid "Skip the Line" window that lets a launch be booked for a specific day.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_maker ~40

A maker profile by username: bio, links, streak, followers and their launched products.

NameTypeReqDescription
usernamestringyesThe username, without the @

No output schema declared.

No examples provided.

get_product ~60

Fetch one product listing by its slug: tagline, description, maker, categories, upvotes and launch date.

NameTypeReqDescription
slugstringyesThe product slug, e.g. "acme-analytics" from awesomeindie.com/product/acme-analytics

No output schema declared.

No examples provided.

get_todays_launches ~26

The products launching on Awesome Indie today (UTC), in ranking order.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_top_products ~133

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 "2026-08", yearly "2026".

NameTypeReqDescription
limitinteger–How many products to return (default 20)
periodstringyesdaily, weekly, monthly or yearly
slugstring–Archived period slug; omit for the current period

No output schema declared.

No examples provided.

list_categories ~30

Every product category in the directory, most-populated first. Product counts are a periodic snapshot, not live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_products ~58

Search the Awesome Indie directory of launched indie/micro-startup products by keywords. Returns matches ranked by relevance and upvote score.

NameTypeReqDescription
querystringyesKeywords to search for, e.g. "screenshot tool" or "newsletter analytics"

No output schema declared.

No examples provided.

Install

How do I install the Awesome Indie MCP server?

Awesome Indie is a hosted endpoint at https://awesomeindie.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · awesomeindie.com

# add to Claude Code
claude mcp add --transport http com-awesomeindie-mcp 'https://awesomeindie.com/api/mcp'
Common questions

What is the Awesome Indie MCP server?

Awesome Indie is an MCP server listed in the public MCP registry as com.awesomeindie/mcp. Search indie product launches, rankings and makers, and submit your own, on Awesome Indie. This page covers its hosted endpoint (https://awesomeindie.com/api/mcp).

Is the Awesome Indie MCP server safe to use?

Awesome Indie scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Awesome Indie MCP server expose?

Awesome Indie exposes 9 tools: search_products, get_product, get_todays_launches, get_top_products, list_categories, and 4 more. Their descriptions and schemas cost roughly 479 tokens of context every time the server is loaded.

Does the Awesome Indie MCP server require authentication?

No. We connected to Awesome Indie without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Awesome Indie MCP server still maintained?

Awesome Indie is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Awesome Indie MCP server?

VerifyMCP ran 13 checks on Awesome Indie, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.