Google Search Console integration for Model Context Protocol (MCP)
OpenApps is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Rankings, launches and featuring across the ChatGPT, Claude, Cursor and Grok Bot app stores.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http openapps-mcp https://theopenapps.com/mcp
# 2 — ask your agent for something these tools do
# changes_list, new_list, stores_get and 11 more
OpenApps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http openapps-mcp https://theopenapps.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when the user asks what changed in a store: chart moves, featuring, launches, delistings, metric moves or MCP changes, newest first with counts per type. Do not use for a chart's full current order; use charts_get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| region | string | no | ChatGPT country code (default us). |
| since | string | no | Window start: ISO-8601 or -24h, -7d. |
| apps | array | no | Listing refs or OpenApps URLs. |
| types | array | no | Default: all but release_change. |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when the user asks which apps are new in a store since a time, by launch date or else the day each went live. Do not use for rank or toolset changes; use changes_list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| since | string | no | Window start: ISO-8601 or -24h, -7d. |
| sort | string | no | — |
| limit | integer | no | — |
| cursor | string | no | — |
| category | string | no | Category title (ChatGPT). |
| kinds | array | no | e.g. claude:connector; stores_get lists them. |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need stores, app counts, countries, freshness, charts or metrics. Pass store for chart names. guide returns a playbook's steps: weekly_brief (a store's week), competitor_watch (compare apps), audit_my_server (an MCP server's tools). Do not use for rankings; use charts_get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | no | — |
| guide | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need a chart now or at a past time, with movement and 1-based positions. Do not use for a listing across charts; use listings_profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| chart | string | yes | Chart name; stores_get lists them. |
| region | string | no | ChatGPT country code (default us). |
| at | string | no | Past time: ISO-8601 or -24h, -7d. |
| kinds | array | no | e.g. claude:connector; stores_get lists them. |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when the user asks which apps lead a store by a published number. claude: installs, popularity_score, trending_score, gh_stars; cursor: dir_installs, dir_stars. Do not use for chart positions; use charts_get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| metric | string | yes | Metric name; stores_get lists each store's. |
| kinds | array | no | e.g. claude:connector; stores_get lists them. |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when the user asks which apps are popular in a store over the last month: OpenApps Rank, a 28-day aggregate of its popularity charts, with tier and momentum. Do not use for one day's chart order (charts_get) or published counts (leaderboards_get).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| chart | string | no | Chart name; stores_get lists them. |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need an app's ref from its name, its publisher, a brand it works with or what it does ("create jira ticket"); one row per app, best match first. Do not use for popularity or rankings; use charts_get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words in app names, descriptions or publishers. |
| publisher | string | no | Publisher name, in any form. |
| store | string | no | — |
| kind | string | no | — |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need when and where apps were featured, per app or home shelf, over at most 30 days. Do not use for current shelf order; use charts_get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | yes | — |
| app | string | no | Listing ref or OpenApps URL. |
| chart | string | no | Chart name; stores_get lists them. |
| region | string | no | ChatGPT country code (default us). |
| since | string | no | Window start: ISO-8601 or -24h, -7d. |
| at | string | no | Past time: ISO-8601 or -24h, -7d. |
| limit | integer | no | — |
| cursor | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need a listing profile, or up to 5 (Pro): its app, country availability, ranks, metrics and MCP tools. Stale or refused countries read unknown. Do not use for discovery; use listings_search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| apps | array | yes | Listing refs or OpenApps URLs. |
| include | array | no | Sections per profile. |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need a tracked app or server's stored MCP tools or changes. at selects a past snapshot; diff_from compares versions. Do not use for arbitrary URLs; only tracked servers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app | string | no | Listing ref or OpenApps URL. |
| server | string | no | MCP server URL. |
| at | string | no | Past time: ISO-8601 or -24h, -7d. |
| diff_from | string | no | Earlier toolset: snapshot hash or time. |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when you need store sizes, weekly launches, app kinds or MCP ecosystem statistics. Do not use for app profiles or rankings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| store | string | no | — |
| response_format | string | no | — |
| context | string | no | The user's goal, briefly. |
Use this when ChatGPT deep research needs listings, apps, tags (query tag:<id>), charts or tracked MCP URLs. Returns typed ids for fetch. Do not use for rankings or events; use charts_get or changes_list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words in app names, descriptions or publishers. |
Use this when ChatGPT deep research needs a document for an id returned by search: listing, app, tag, chart or MCP toolset. Do not use for ids outside search results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A search result id: listing:{store}:{plugin_id}, app:{slug}, tag:{id}, chart:{store}:{chart} or server:{url}. |
Use this when OpenApps' tools or data fail the user: an error, data the user says is wrong (such as an app bound to the wrong listing), a missing capability, or something confusing. Ask the user before sending a report they did not ask for. It is stored privately with the caller's account and client; no reply comes in this conversation. Summarize; never include secrets or personal data. Do not use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| issue | string | yes | — |
| summary | string | yes | One line. |
| initiator | string | yes | user if the user asked for it, else model. |
| details | string | no | — |
| tool | string | no | — |
| subject_type | string | no | — |
| subject_id | string | no | Ref, slug or URL. |
| request_id | string | no | From an error answer. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenApps or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| changes_list | no tags | |
| new_list | no tags | |
| stores_get | no tags | |
| charts_get | no tags | |
| leaderboards_get | no tags | |
| scores_list | no tags | |
| listings_search | no tags | |
| featuring_history | no tags | |
| listings_profile | no tags | |
| mcp_toolset_get | no tags | |
| market_get | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| feedback_send | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OpenApps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.