APP NAVI
REMOTE · APPNAVI.DEV
Search indie and small-team apps and their developers (7 languages). Unverified fields are null.
Available components
Last scanned (13 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security51
- 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 6 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 475 tokens (~79/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +3
- HSTS header: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- “search_apps” reworded the description of “query” cosmetic
- 14 Nov 26 57
First indexed and scored.
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://appnavi.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=appnavi.dev | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d087dab8a135c0a0e16d38029cc9fb2 |
| SANs: appnavi.dev, *.appnavi.dev | ||||||
| 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 appnavi.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| appnavi.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://appnavi.dev/mcp | Verified | 200 | |
| http (plaintext) | http://appnavi.dev/mcp | Served over HTTP | 200 |
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 →
get_app ~42
slug で 1 件のアプリの詳細(料金・機能・出典・確認日)を取得する。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_developer ~42
slug で 1 人(1 チーム)の開発者と、掲載しているアプリ一覧を取得する。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_ranking ~103
★評価に基づくランキング。評価が3件以上のアプリだけが順位に載る(ranked)。評価が少ないアプリは rising に件数だけ出る。順位は評価だけで決まり、広告や掲載料は関係しない。Ranking by user star ratings (3+ ratings required).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | カテゴリー slug(省略すると総合) |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_categories ~19
カテゴリー一覧と件数を返す。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_apps ~168
APP NAVI のアプリを検索する。値が null の項目は「未確認」(推測していない)。Search indie/small-team apps; null means unverified.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_only | boolean | – | AI を使っているものだけ |
| category | string | – | カテゴリー slug(list_categories で取得) |
| free_only | boolean | – | 無料プランがあるものだけ |
| japanese_only | boolean | – | 日本語対応のものだけ |
| limit | integer | – | – |
| query | string | – | キーワードまたはやりたいことの文(例: 現場で見積もりができるアプリ)。合う順に返す / keyword or what you want to do, ranked by relevance |
No output schema declared.
No examples provided.
search_developers ~101
開発者を検索する。contract_work は開発者本人の申告(yes/no/undecided、null は未確認)。Search developers; contractWork is self-declared.
| Name | Type | Req | Description |
|---|---|---|---|
| contract_only | boolean | – | 受託開発を受けると申告している開発者だけ |
| limit | integer | – | – |
| query | string | – | 開発者名のキーワード / name keyword |
No output schema declared.
No examples provided.
How do I install the APP NAVI MCP server?
APP NAVI is a hosted endpoint at https://appnavi.dev/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 · appnavi.dev
claude mcp add --transport http dev-appnavi-appnavi 'https://appnavi.dev/mcp'
What is the APP NAVI MCP server?
APP NAVI is an MCP server listed in the public MCP registry as dev.appnavi/appnavi. Search indie and small-team apps and their developers (7 languages). Unverified fields are null. This page covers its hosted endpoint (https://appnavi.dev/mcp).
Is the APP NAVI MCP server safe to use?
APP NAVI scores 62 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 APP NAVI MCP server expose?
APP NAVI exposes 6 tools: search_apps, get_app, search_developers, get_developer, get_ranking, list_categories. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Does the APP NAVI MCP server require authentication?
No. We connected to APP NAVI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the APP NAVI MCP server still maintained?
APP NAVI 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 APP NAVI MCP server?
VerifyMCP ran 12 checks on APP NAVI, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about APP NAVI: Authorization. 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.