# com.minradar/minradar (remote · minradar.com)

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

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `minradar.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-minradar-minradar/minradar.md), [page](https://verifymcp.io/servers/com-minradar-minradar/minradar)

## Channel facts

- Endpoint: `https://minradar.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1074 tokens (~134/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the com.minradar/minradar MCP server?

com.minradar/minradar is a hosted endpoint at https://minradar.com/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-minradar-minradar": {
      "url": "https://minradar.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-minradar-minradar": {
      "type": "http",
      "url": "https://minradar.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-minradar-minradar]
url = "https://minradar.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-minradar-minradar": {
      "type": "remote",
      "url": "https://minradar.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-minradar-minradar --url 'https://minradar.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-minradar-minradar:
    url: "https://minradar.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-minradar-minradar": {
      "Transport": "http",
      "Url": "https://minradar.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-minradar-minradar -t streamable-http -u 'https://minradar.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-minradar-minradar": {
      "type": "http",
      "url": "https://minradar.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 74% → 100%
- [functional] New tool “find_solo_buildable”
- [cosmetic] “find_unmet_demand” added an optional parameter “min_rating_count_scaled”
- [cosmetic] “find_unmet_demand” reworded the description of “genre”
- [cosmetic] “find_unmet_demand” reworded the description of “include_institutional”
- [cosmetic] “find_unmet_demand” reworded the description of “limit”
- [cosmetic] “find_unmet_demand” reworded the description of “min_rating_count”
- [cosmetic] “find_unmet_demand” reworded the description of “storefront”
- [cosmetic] “generate_app_brief” reworded the description of “app_id”
- [cosmetic] “generate_app_brief” reworded the description of “storefront”
- [cosmetic] “generate_app_brief” reworded the description of “target”
- [cosmetic] “get_opportunity_brief” reworded the description of “app_id”
- [cosmetic] “get_opportunity_brief” reworded the description of “include_github”
- [cosmetic] “get_opportunity_brief” reworded the description of “storefront”
- [cosmetic] “search_open_source_accelerators” reworded the description of “genre”
- [cosmetic] “search_open_source_accelerators” reworded the description of “limit”
- [cosmetic] “validate_paying_market” reworded the description of “limit”
- [cosmetic] “validate_paying_market” reworded the description of “min_rating_count”
- [cosmetic] “validate_paying_market” reworded the description of “storefront”

### 2026-09-19 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 60)

First indexed and scored.

## MCP tools (8)

### `find_unmet_demand` (~260 tokens)

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.

Input parameters:

- `genre` (string): Restrict to one App Store category, e.g. Productivity.
- `include_institutional` (boolean): Include institution-locked products that a solo dev cannot win.
- `limit` (integer): Maximum number of results to return.
- `max_rating` (number): Only include apps at or below this average rating, e.g. 4.0.
- `max_rating_count` (integer): Optional ceiling to exclude unassailable giants.
- `min_rating_count` (integer): Rating volume is the install proxy. On /api/lens this remains a legacy alias for the scaled value; /api/hotspots uses it literally.
- `min_rating_count_scaled` (integer): Pre-scaled rating volume filter. /api/lens applies max(300, floor(value / 3)); /api/paying applies max(200, floor(value / 5)).
- `storefront` (string): Two-letter App Store region. The value is region identity, never a label.

### `find_solo_buildable` (~246 tokens)

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.

Input parameters:

- `genre` (string): Restrict to one App Store category, e.g. Productivity.
- `include_institutional` (boolean): Include institution-locked products that a solo dev cannot win.
- `limit` (integer): Maximum number of results to return.
- `max_rating` (number): Only include apps at or below this average rating, e.g. 4.0.
- `max_rating_count` (integer): Optional ceiling to exclude unassailable giants.
- `min_rating_count` (integer): Rating volume is the install proxy. On /api/lens this remains a legacy alias for the scaled value; /api/hotspots uses it literally.
- `min_rating_count_scaled` (integer): Pre-scaled rating volume filter. /api/lens applies max(300, floor(value / 3)); /api/paying applies max(200, floor(value / 5)).
- `storefront` (string): Two-letter App Store region. The value is region identity, never a label.

### `validate_paying_market` (~138 tokens)

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.

Input parameters:

- `limit` (integer): Maximum number of results to return.
- `min_rating_count` (integer): Rating volume is the install proxy. On /api/lens this remains a legacy alias for the scaled value; /api/hotspots uses it literally.
- `storefront` (string): Two-letter App Store region. The value is region identity, never a label.

### `get_opportunity_brief` (~109 tokens)

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.

Input parameters:

- `app_id` (integer, required): App Store track id.
- `include_github` (boolean): MCP name for the REST with_github switch.
- `storefront` (string): Two-letter App Store region. The value is region identity, never a label.

### `generate_app_brief` (~109 tokens)

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.

Input parameters:

- `app_id` (integer, required): App Store track id.
- `storefront` (string): Two-letter App Store region. The value is region identity, never a label.
- `target` (string): AI coding agent that will receive the brief.

### `search_open_source_accelerators` (~101 tokens)

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.

Input parameters:

- `genre` (string): Restrict to one App Store category, e.g. Productivity.
- `limit` (integer): Maximum number of results to return.
- `theme` (string): Complaint theme key, e.g. data_loss_sync, paywall_aggressive, ai_quality.

### `explain_method` (~31 tokens)

Explain the scoring formulas, weights, and the honest limitations of the data. Use when a user questions the numbers.

### `market_stats` (~26 tokens)

Report local data coverage (apps, reviews, chart snapshots) and the last ingest run.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-minradar-minradar/minradar#diagnostics

## Score history

- 2026-09-20: 61
- 2026-09-19: 61
- 2026-09-18: 60

## Common questions

### What is the com.minradar/minradar MCP server?

com.minradar/minradar is an MCP server listed in the public MCP registry as com.minradar/minradar. App Store opportunity data for coding agents: unmet demand, paying markets, build briefs. This page covers its hosted endpoint (https://minradar.com/mcp).

### Is the com.minradar/minradar MCP server safe to use?

com.minradar/minradar scores 61 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 com.minradar/minradar MCP server expose?

com.minradar/minradar exposes 8 tools: find_unmet_demand, find_solo_buildable, validate_paying_market, get_opportunity_brief, generate_app_brief, and 3 more. Their descriptions and schemas cost roughly 1,020 tokens of context every time the server is loaded.

### Does the com.minradar/minradar MCP server require authentication?

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

### Is the com.minradar/minradar MCP server still maintained?

com.minradar/minradar is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://minradar.com/mcp
- Repository: https://github.com/caozhi1984/codex-quant
- Website: https://minradar.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-minradar-minradar/minradar.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-minradar-minradar/minradar.json
- HTML version of this page: https://verifymcp.io/servers/com-minradar-minradar/minradar