Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dekadans ASO

REMOTE · DEKADANS.NET

App Store keyword rankings, popularity, difficulty and keyword research across 175 storefronts.

Available components

+4 this week 76 Trust /100

Last scanned (7 minutes ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 924 tokens (~71/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 24% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 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.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 71

    First indexed and scored.

Diagnostics

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://dekadans.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dekadans.net CN=WE1,O=Google Trust Services,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA256 5096d5598e71debe133f5f3c929816e3
SANs: dekadans.net, *.dekadans.net
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 dekadans.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
dekadans.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer

Bearer

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dekadans.net/mcp Verified 200
http (plaintext) http://dekadans.net/mcp HTTPS enforced 301 https://dekadans.net/mcp
MCP tools · 13 exposed · ~851 tokens

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 →

Tool Tokens
add_app ~109

Track an app by App Store ID; its name is looked up automatically. Omit appStoreId (and pass name) for a temporary app. Free plan: 1 app.

NameTypeReqDescription
appStoreIdstring–Omit for a temporary (unpublished) app
homeStorestring–Store where the app is available; used to look it up
namestring–Defaults to the App Store name. Required for temporary apps.
platformstring––

No output schema declared.

No examples provided.

add_keywords ~83

Track up to 100 keywords for an app in a store and measure rank, popularity and difficulty. Plan limit on total tracked keywords (free: 10); a batch over the limit is rejected entirely.

NameTypeReqDescription
appIdintegeryesLocal app id from list_apps, not the App Store ID
keywordsarrayyes–
storestringyes–

No output schema declared.

No examples provided.

get_app_details ~63

App Store details (developer, rating, price, description, screenshots) for up to 50 App Store IDs. IDs not available in the store are omitted. Counts toward the research quota.

NameTypeReqDescription
appStoreIdsarrayyes–
storestring––

No output schema declared.

No examples provided.

get_app_keywords ~39

Tracked keywords of an app with latest metrics.

NameTypeReqDescription
appIdintegeryesLocal app id from list_apps, not the App Store ID

No output schema declared.

No examples provided.

get_competitor_keywords ~88

Derives 1–3 word candidates from the top 10 competitors ranking for a keyword and returns those with popularity > 5, highest first. Pass your appStoreId to exclude your own app. Counts toward the research quota.

NameTypeReqDescription
appStoreIdstring––
platformstring––
storestring––
termstringyes–

No output schema declared.

No examples provided.

get_keyword_history ~96

Daily rank, popularity and difficulty history of one tracked keyword (keywordId from get_app_keywords), oldest first; days without a measurement are omitted. Free plan: last 7 days.

NameTypeReqDescription
appIdintegeryesLocal app id from list_apps, not the App Store ID
days––Days of history to return, or "all". Free plan: capped at 7.
keywordIdintegeryes–

No output schema declared.

No examples provided.

get_keyword_popularity ~47

Popularity scores for up to 100 keywords in a store, without tracking them. Counts toward the research quota.

NameTypeReqDescription
storestring––
termsarrayyes–

No output schema declared.

No examples provided.

get_keyword_suggestions ~63

Keyword ideas for an App Store app with popularity and difficulty for the selected platform. Counts toward the research quota.

NameTypeReqDescription
appStoreIdstringyes–
highPopularityboolean––
platformstring––
storestring––

No output schema declared.

No examples provided.

get_most_searched_keywords ~84

One page of the most searched keywords in a store, optionally for an App Store category id (e.g. 6013). Check `month`: data can be from an earlier month. Counts toward the research quota.

NameTypeReqDescription
categorystring––
limitinteger––
pageinteger––
storestring––

No output schema declared.

No examples provided.

get_usage ~38

Current plan, tracked apps, keywords and research calls in the current quota period (free: month, pro: day). A null limit means unlimited.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_apps ~15

Tracked apps of the user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

refresh_app_keywords ~42

Measure all tracked keywords of an app now and append to history.

NameTypeReqDescription
appIdintegeryesLocal app id from list_apps, not the App Store ID

No output schema declared.

No examples provided.

search_app_store ~84

Live App Store search for a keyword. Returns ranked apps and difficulty; with appStoreId also that app's ranking (null = not in the returned results). Counts toward the research quota.

NameTypeReqDescription
appStoreIdstring––
limitinteger––
platformstring––
storestring––
termstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Dekadans ASO MCP server?

Dekadans ASO is a hosted endpoint at https://dekadans.net/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 · dekadans.net

# add to Claude Code
claude mcp add --transport http net-dekadans-aso 'https://dekadans.net/mcp'
Common questions

What is the Dekadans ASO MCP server?

Dekadans ASO is an MCP server listed in the public MCP registry as net.dekadans/aso. App Store keyword rankings, popularity, difficulty and keyword research across 175 storefronts. This page covers its hosted endpoint (https://dekadans.net/mcp).

Is the Dekadans ASO MCP server safe to use?

Dekadans ASO scores 76 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 Dekadans ASO MCP server expose?

Dekadans ASO exposes 13 tools: list_apps, add_app, add_keywords, refresh_app_keywords, get_app_keywords, and 8 more. Their descriptions and schemas cost roughly 851 tokens of context every time the server is loaded.

Does the Dekadans ASO MCP server require authentication?

Yes. Dekadans ASO asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Dekadans ASO MCP server still maintained?

Dekadans ASO 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.