com.minradar/minradar
REMOTE · MINRADAR.COM
App Store opportunity data for coding agents: unmet demand, paying markets, build briefs.
Available components
Last scanned (4 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 26 +1
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 17 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 70. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 60. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://minradar.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=minradar.com | CN=YE1,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5648d82143eb06fd78e7ed0e53dd08d1b6b |
| SANs: minradar.com, www.minradar.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of minradar.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| minradar.com. | absent | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://minradar.com/mcp | Verified | 200 | |
| http (plaintext) | http://minradar.com/mcp | HTTPS enforced | 301 | https://minradar.com/mcp |
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 →
explain_method ~31
Explain the scoring formulas, weights, and the honest limitations of the data. Use when a user questions the numbers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_solo_buildable ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
find_unmet_demand ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
generate_app_brief ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | integer | yes | 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. |
No output schema declared.
No examples provided.
get_opportunity_brief ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | integer | yes | 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. |
No output schema declared.
No examples provided.
market_stats ~26
Report local data coverage (apps, reviews, chart snapshots) and the last ingest run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_open_source_accelerators ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
validate_paying_market ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · minradar.com
claude mcp add --transport http com-minradar-minradar 'https://minradar.com/mcp'
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 74 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.