Skip to content

com.minradar/minradar

by minradar.com · remote · no sign-in to list tools · v1.0.0 · published by com.minradar

App Store opportunity data for coding agents: unmet demand, paying markets, build briefs.

Changes · 2
CompareRegistry entry

8 tools: 2 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http minradar https://minradar.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 2Claude Code: ask
  • generate_app_briefProduce a ready-to-build product specification for an opportunity, formatted for a specific AI coding agent (codex, claude, or cursor).No findings

    Why it is in this group

    • The name "generate_app_brief" says "generate": a word for a change.
    Description, as the server wrote it
    Produce a ready-to-build product specification for an opportunity, formatted for a specific AI coding agent (codex, claude, or cursor). Includes the wedge, the verbatim complaints to fix, verified open-source accelerators, and a verification plan.
  • market_statsReport local data coverage (apps, reviews, chart snapshots) and the last ingest run.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Report local data coverage (apps, reviews, chart snapshots) and the last ingest run.
Only reads 6Claude Code: allow
  • explain_methodExplain the scoring formulas, weights, and the honest limitations of the data.No findings

    Why it is in this group

    • The name "explain_method" says "explain": a word for reading.
    Description, as the server wrote it
    Explain the scoring formulas, weights, and the honest limitations of the data. Use when a user questions the numbers.
  • find_solo_buildableFind opportunities a single developer can realistically build: clear winnability plus an explicit single-user, local or offline core.No findings

    Why it is in this group

    • The name "find_solo_buildable" says "find": a word for reading.
    Description, as the server wrote it
    Find opportunities a single developer can realistically build: clear winnability plus an explicit single-user, local or offline core. Use when solo feasibility is the primary constraint.
  • find_unmet_demandRank App Store opportunities in apps that already have a large user base but whose users are clearly unhappy (unmet demand).No findings

    Why it is in this group

    • The name "find_unmet_demand" says "find": a word for reading.
    Description, as the server wrote it
    Rank App Store opportunities in apps that already have a large user base but whose users are clearly unhappy (unmet demand). Returns a ranked table with tier, score, rating and scale. Use this first when deciding what app to build.
  • get_opportunity_briefFull evidence dossier for one app: score breakdown, plain-language diagnosis, complaint themes with verbatim user quotes, review provenance, and matching open-source accelerators.No findings

    Why it is in this group

    • The name "get_opportunity_brief" says "get": a word for reading.
    Description, as the server wrote it
    Full evidence dossier for one app: score breakdown, plain-language diagnosis, complaint themes with verbatim user quotes, review provenance, and matching open-source accelerators. Use after find_low_hanging_fruit to inspect a specific candidate.
  • search_open_source_acceleratorsFind maintained, commercially reusable open-source projects for a niche, with license posture.No findings

    Why it is in this group

    • The name "search_open_source_accelerators" says "search": a word for reading.
    Description, as the server wrote it
    Find maintained, commercially reusable open-source projects for a niche, with license posture. Use to avoid rebuilding infrastructure and to check whether a dependency is safe to ship.
  • validate_paying_marketRank app categories by evidence that users already pay inside them: how many of its apps reach the store-wide Top-Grossing chart, how many charge upfront, paywall language in sampl…No findings

    Why it is in this group

    • The name "validate_paying_market" says "validate": a word for reading.
    Description, as the server wrote it
    Rank app categories by evidence that users already pay inside them: how many of its apps reach the store-wide Top-Grossing chart, how many charge upfront, paywall language in sampled reviews, and review depth. Call this before building to confirm a market monetises.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http minradar https://minradar.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__minradar__find_unmet_demand",
      "mcp__minradar__find_solo_buildable",
      "mcp__minradar__validate_paying_market",
      "mcp__minradar__get_opportunity_brief",
      "mcp__minradar__search_open_source_accelerators",
      "mcp__minradar__explain_method"
    ],
    "ask": [
      "mcp__minradar__generate_app_brief",
      "mcp__minradar__market_stats"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as minradar. Review it before you use it.