Skip to content

minradar MCP server

com.minradar/minradarminradar.comstreamable-httpv1.0.0Scanned

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

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the minradar MCP server can do

The minradar MCP server is published by minradar.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: generate_app_brief and market_stats), but cannot delete data. 6 tools only read.

1 tool brings in text other people can write (get_opportunity_brief).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Oct 29, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 6Show 6 read-only tools
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_opportunity_brief" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:42 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://minradar.com/mcp: tools/list returned 8 tools to an anonymous client, including generate_app_brief (write), market_stats (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
claude mcp add --transport http minradar https://minradar.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as minradar. Review it before you use it.

Capability tags behind 1 rule
  • mcp__minradar__get_opportunity_brief untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.minradar/minradar/verify?hash=151dd670618b6ced227c6986d21a14fc4f7d73ad7e2bf4efa7aafe5c75043f36" | jq -e '.changed == false'

Pinned hash 151dd670618b, from Oct 29, 2026, 12:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.minradar/minradar/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.minradar/minradar
[![Anlyon Radar](https://radar.anlyon.com/badge/com.minradar/minradar.svg)](https://radar.anlyon.com/servers/com.minradar/minradar)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.

minradar MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the minradar MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the minradar MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the minradar MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the minradar MCP server have?

8 tools: 2 write, 6 read. generate_app_brief, market_stats, find_unmet_demand, find_solo_buildable, validate_paying_market, get_opportunity_brief, search_open_source_accelerators and explain_method.

Does the minradar MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the minradar MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the minradar MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 29, 2026.