_ registry / mcp streamable-http · checked 3h ago

rankcusp

https://rankcusp.com

Registry code: 8b3e1eb0fa25333a

api record

rankcusp finds the keywords an app ranks 11-30 for on the App Store. Call list_apps first to find the app, then cusp_actions for the priority work. Unmeasured values come back as null; do not read them as zero.

endpoint
https://rankcusp.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is rankcusp live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is rankcusp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does rankcusp have?
9 tools: ranking_keywords, audit_metadata, add_keywords, country_priorities, list_keywords, cusp_actions, list_apps, get_keyword, ….
Is rankcusp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.8%· all time 99.8%

latency
196ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 467 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • find app store keywords ranking 11 to 30
  • track keywords for an app
  • audit app title and keyword field
  • find competitors for a keyword
takes → gives
text → data
tools
8 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • ranking_keywords reads auth-required 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    },
    "limit": {
      "type": "number",
      "description": "How many rows, at most 200."
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "maxRank": {
      "type": "number",
      "description": "Only positions at or above this, e.g. 30 for the reachable band."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • audit_metadata reads auth-required 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Up to 30 characters."
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "subtitle": {
      "type": "string",
      "description": "Up to 30 characters."
    },
    "keywordField": {
      "type": "string",
      "description": "The 100-character field, comma-separated, as App Store Connect wants it."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • add_keywords changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId",
    "country",
    "keywords"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "keywords": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The phrases to track."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • country_priorities reads auth-required 13h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • list_keywords reads auth-required 17h ago

    Lists an app's keywords in one storefront, with rank, popularity and difficulty.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId",
    "country"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    },
    "limit": {
      "type": "number",
      "description": "How many rows, at most 200."
    },
    "offset": {
      "type": "number"
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "cuspOnly": {
      "type": "boolean",
      "description": "The 11-30 band only: the ones that reach the first page with the least effort."
    },
    "rankedOnly": {
      "type": "boolean",
      "description": "Only the ones ranking in the top 200."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • cusp_actions reads auth-required 10h ago

    The keywords in the 11-30 band, ordered by popularity. The work list a metadata edit pays off on most.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId",
    "country"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    },
    "limit": {
      "type": "number"
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • list_apps reads auth-required 17h ago

    Lists the apps and rivals tracked on the account. The appId and storefront codes the other tools want come from here.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_keyword reads auth-required 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "appId",
    "country",
    "keyword"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "App Store app id"
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "keyword": {
      "type": "string",
      "description": "The phrase to look up."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • keyword_competitors reads auth-required 10h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "keyword",
    "country"
  ],
  "properties": {
    "limit": {
      "type": "number"
    },
    "country": {
      "type": "string",
      "description": "Storefront code, e.g. us, tr, de"
    },
    "keyword": {
      "type": "string",
      "description": "The phrase to look up."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8b3e1eb0fa25333a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8b3e1eb0fa25333a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8b3e1eb0fa25333a/badge.svg)](https://brick.blue/agent/8b3e1eb0fa25333a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.