rankcusp
REMOTE · RANKCUSP.COM · SCANNED SEP 22
App Store keyword ranks, the 11-30 cusp band, metadata audits and rival positions.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 918 tokens (~102/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management86
- Stability check failed: schema churn in the 28 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the rankcusp MCP server?
rankcusp is a hosted endpoint at https://rankcusp.com/api/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 · rankcusp.com
claude mcp add --transport http com-rankcusp-aso 'https://rankcusp.com/api/mcp'
{
"mcpServers": {
"com-rankcusp-aso": {
"url": "https://rankcusp.com/api/mcp"
}
}
} {
"servers": {
"com-rankcusp-aso": {
"type": "http",
"url": "https://rankcusp.com/api/mcp"
}
}
} [mcp_servers.com-rankcusp-aso] url = "https://rankcusp.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rankcusp-aso": {
"type": "remote",
"url": "https://rankcusp.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-rankcusp-aso --url 'https://rankcusp.com/api/mcp' --transport streamable-http
mcp_servers:
com-rankcusp-aso:
url: "https://rankcusp.com/api/mcp" {
"McpServers": {
"com-rankcusp-aso": {
"Transport": "http",
"Url": "https://rankcusp.com/api/mcp"
}
}
} assistant mcp add com-rankcusp-aso -t streamable-http -u 'https://rankcusp.com/api/mcp'
{
"mcpServers": {
"com-rankcusp-aso": {
"type": "http",
"url": "https://rankcusp.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 76.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 66 to 70.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 56 to 60.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 46.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 36 to 40.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
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 22 Sept 2026 · Probed https://rankcusp.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rankcusp.com | CN=YR1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | RSA 4096 | SHA256-RSA | 6f5787f99154055f110a745f7de7a4413ee |
| SANs: rankcusp.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rankcusp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rankcusp.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rankcusp.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://rankcusp.com/api/mcp | HTTPS enforced | 301 | https://rankcusp.com/api/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 →
add_keywords ~102
Adds keywords to an app's tracked set in one storefront. Takes a list or a comma-separated paste. They arrive unscored - scoring costs requests to Apple and happens on the collector's schedule - so do not read a null popularity here as a zero.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
| country | string | yes | Storefront code, e.g. us, tr, de |
| keywords | array | yes | The phrases to track. |
No output schema declared.
No examples provided.
audit_metadata ~128
Audits a draft title, subtitle and 100-character keyword field against Apple's rules and against each other. Returns what is wasted, what Apple will actually index, and the field rewritten without the waste. Nothing is submitted anywhere - this only reads the text you pass in.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Storefront code, e.g. us, tr, de |
| keywordField | string | – | The 100-character field, comma-separated, as App Store Connect wants it. |
| subtitle | string | – | Up to 30 characters. |
| title | string | – | Up to 30 characters. |
No output schema declared.
No examples provided.
country_priorities ~75
Ranks the storefronts an app is tracked in by how much is winnable there: how many keywords sit in the cusp band, how many already reach the top ten, and whether the rivals' ratings leave an opening. Answers which market to work on first.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
No output schema declared.
No examples provided.
cusp_actions ~71
The keywords in the 11-30 band, ordered by popularity. The work list a metadata edit pays off on most.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
| country | string | yes | Storefront code, e.g. us, tr, de |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_keyword ~87
One keyword: its rank, its scores, its first page and the verdict - should it be targeted, and why. Every unmeasured value comes back null, never zero.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
| country | string | yes | Storefront code, e.g. us, tr, de |
| keyword | string | yes | The phrase to look up. |
No output schema declared.
No examples provided.
keyword_competitors ~95
Who ranks for a phrase, deeper than the ten the first page carries. Use it to find the rivals a first-page reading misses - an app at 40 for a phrase you sit at 60 for is the one to study.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Storefront code, e.g. us, tr, de |
| keyword | string | yes | The phrase to look up. |
| limit | number | – | – |
No output schema declared.
No examples provided.
list_apps ~32
Lists the apps and rivals tracked on the account. The appId and storefront codes the other tools want come from here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_keywords ~121
Lists an app's keywords in one storefront, with rank, popularity and difficulty.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
| country | string | yes | Storefront code, e.g. us, tr, de |
| cuspOnly | boolean | – | The 11-30 band only: the ones that reach the first page with the least effort. |
| limit | number | – | How many rows, at most 200. |
| offset | number | – | – |
| rankedOnly | boolean | – | Only the ones ranking in the top 200. |
No output schema declared.
No examples provided.
ranking_keywords ~152
Which keywords an app is already ranking for, from the pooled record of every search this product has run. Works on any App Store id, not only the ones on this account - point it at a rival to read theirs. Apple publishes no endpoint for this; the answer is only as wide as what has been observed, so an app nobody has swept near returns little.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | App Store app id |
| country | string | – | Storefront code, e.g. us, tr, de |
| limit | number | – | How many rows, at most 200. |
| maxRank | number | – | Only positions at or above this, e.g. 30 for the reachable band. |
No output schema declared.
No examples provided.
What is the rankcusp MCP server?
rankcusp is an MCP server listed in the public MCP registry as com.rankcusp/aso. App Store keyword ranks, the 11-30 cusp band, metadata audits and rival positions. This page covers its hosted endpoint (https://rankcusp.com/api/mcp).
Is the rankcusp MCP server safe to use?
rankcusp scores 81 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 rankcusp MCP server expose?
rankcusp exposes 9 tools: list_apps, list_keywords, get_keyword, audit_metadata, country_priorities, and 4 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.
Does the rankcusp MCP server require authentication?
No. We connected to rankcusp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the rankcusp MCP server still maintained?
rankcusp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.