# OpenApps (remote · theopenapps.com)

Rankings, launches and featuring across the ChatGPT, Claude, Cursor and Grok Bot app stores.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `theopenapps.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps.md), [page](https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps)

## Channel facts

- Endpoint: `https://theopenapps.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2392 tokens (~140/item across 17 items; 16 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
  - Structured output schemas are declared (13% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the OpenApps MCP server?

OpenApps is a hosted endpoint at https://theopenapps.com/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.

### Claude

```bash
claude mcp add --transport http com-theopenapps-openapps 'https://theopenapps.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-theopenapps-openapps": {
      "url": "https://theopenapps.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-theopenapps-openapps": {
      "type": "http",
      "url": "https://theopenapps.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-theopenapps-openapps]
url = "https://theopenapps.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-theopenapps-openapps": {
      "type": "remote",
      "url": "https://theopenapps.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-theopenapps-openapps --url 'https://theopenapps.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-theopenapps-openapps:
    url: "https://theopenapps.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-theopenapps-openapps": {
      "Transport": "http",
      "Url": "https://theopenapps.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-theopenapps-openapps -t streamable-http -u 'https://theopenapps.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-theopenapps-openapps": {
      "type": "http",
      "url": "https://theopenapps.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-11-20 (score 84, +1)

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

### 2026-11-17 (score 83, +1)

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

### 2026-11-15 (score 82, +1)

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

### 2026-11-13 (score 81, +1)

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

### 2026-11-12 (score 80, 0)

- [functional] Server version: 8b05ce4c-6ac8-4844-9f7a-0e08314cdb26 → 0079b3b0-c0d3-43c9-857d-b028069450c9

### 2026-11-11 (score 80, +1)

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

### 2026-11-10 (score 79, 0)

- [functional] Server version: ff10ee87-587b-4f1e-9631-b6567730c44c → 8b05ce4c-6ac8-4844-9f7a-0e08314cdb26

## MCP tools (16)

### `changes_list` (~162 tokens)

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.

Input parameters:

- `apps` (array): Listing refs or OpenApps URLs.
- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `limit` (integer)
- `region` (string): ChatGPT country code (default us).
- `response_format` (string)
- `since` (string): Window start: ISO-8601 or -24h, -7d.
- `store` (string, required)
- `types` (array): Default: all but release_change.

### `new_list` (~151 tokens)

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.

Input parameters:

- `category` (string): Category title (ChatGPT).
- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `kinds` (array): e.g. claude:connector; stores_get lists them.
- `limit` (integer)
- `response_format` (string)
- `since` (string): Window start: ISO-8601 or -24h, -7d.
- `sort` (string)
- `store` (string, required)

### `stores_get` (~109 tokens)

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.

Input parameters:

- `context` (string): The user's goal, briefly.
- `guide` (string)
- `response_format` (string)
- `store` (string)

### `charts_get` (~153 tokens)

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.

Input parameters:

- `at` (string): Past time: ISO-8601 or -24h, -7d.
- `chart` (string, required): Chart name; stores_get lists them.
- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `kinds` (array): e.g. claude:connector; stores_get lists them.
- `limit` (integer)
- `region` (string): ChatGPT country code (default us).
- `response_format` (string)
- `store` (string, required)

### `leaderboards_get` (~137 tokens)

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.

Input parameters:

- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `kinds` (array): e.g. claude:connector; stores_get lists them.
- `limit` (integer)
- `metric` (string, required): Metric name; stores_get lists each store's.
- `response_format` (string)
- `store` (string, required)

### `scores_list` (~120 tokens)

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).

Input parameters:

- `chart` (string): Chart name; stores_get lists them.
- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `limit` (integer)
- `response_format` (string)
- `store` (string, required)

### `listings_search` (~135 tokens)

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.

Input parameters:

- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `kind` (string)
- `limit` (integer)
- `publisher` (string): Publisher name, in any form.
- `query` (string, required): Words in app names, descriptions or publishers.
- `response_format` (string)
- `store` (string)

### `featuring_history` (~171 tokens)

Use this when you need when and where apps were featured, per app or home shelf, over up to 90 days.
Do not use for current shelf order; use charts_get.

Input parameters:

- `app` (string): Listing ref or OpenApps URL.
- `at` (string): Past time: ISO-8601 or -24h, -7d.
- `chart` (string): Chart name; stores_get lists them.
- `context` (string): The user's goal, briefly.
- `cursor` (string)
- `limit` (integer)
- `region` (string): ChatGPT country code (default us).
- `response_format` (string)
- `since` (string): Window start: ISO-8601 or -24h, -7d.
- `store` (string, required)

### `listings_profile` (~99 tokens)

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.

Input parameters:

- `apps` (array, required): Listing refs or OpenApps URLs.
- `context` (string): The user's goal, briefly.
- `include` (array): Sections per profile.
- `response_format` (string)

### `listings_copy` (~82 tokens)

Use this when you need what a listing says or shows: name, subtitle, description, keywords, starter prompts, and its widgets' images.
Do not use for ranks or metrics; use listings_profile.

Input parameters:

- `app` (string, required): Listing ref or OpenApps URL.
- `context` (string): The user's goal, briefly.
- `response_format` (string)

### `tags_get` (~123 tokens)

Use this when you need a job or brand tag's top apps per store and its related tags. tag: an id such as notion or developer-tools.
Do not use for finding an app by name; use listings_search.

Input parameters:

- `context` (string): The user's goal, briefly.
- `kinds` (array): e.g. claude:connector; stores_get lists them.
- `limit` (integer)
- `response_format` (string)
- `store` (string)
- `tag` (string, required): Tag id from tags_tree, e.g. gmail.

### `mcp_toolset_get` (~131 tokens)

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.

Input parameters:

- `app` (string): Listing ref or OpenApps URL.
- `at` (string): Past time: ISO-8601 or -24h, -7d.
- `context` (string): The user's goal, briefly.
- `diff_from` (string): Earlier toolset: snapshot hash or time.
- `response_format` (string)
- `server` (string): MCP server URL.

### `market_get` (~62 tokens)

Use this when you need store sizes, weekly launches, app kinds or MCP ecosystem statistics.
Do not use for app profiles or rankings.

Input parameters:

- `context` (string): The user's goal, briefly.
- `response_format` (string)
- `store` (string)

### `search` (~69 tokens)

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.

Input parameters:

- `query` (string, required): Words in app names, descriptions or publishers.

Output parameters:

- `results` (array)

### `fetch` (~82 tokens)

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.

Input parameters:

- `id` (string, required): A search result id: listing:{store}:{plugin_id}, app:{slug}, tag:{id}, chart:{store}:{chart} or server:{url}.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `feedback_send` (~192 tokens)

Send feedback to OpenApps

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 for other servers or the client app; it does not finish the user's task.

Input parameters:

- `details` (string)
- `initiator` (string, required): user if the user asked for it, else model.
- `issue` (string, required)
- `request_id` (string): From an error answer.
- `subject_id` (string): Ref, slug or URL.
- `subject_type` (string)
- `summary` (string, required): One line.
- `tool` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 84
- 2026-11-19: 83
- 2026-11-18: 83
- 2026-11-17: 83
- 2026-11-16: 82
- 2026-11-15: 82
- 2026-11-14: 81
- 2026-11-13: 81
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 79
- 2026-11-09: 79
- 2026-11-08: 78
- 2026-11-07: 78
- 2026-11-06: 77
- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72

## Common questions

### What is the OpenApps MCP server?

OpenApps is an MCP server listed in the public MCP registry as com.theopenapps/openapps. Rankings, launches and featuring across the ChatGPT, Claude, Cursor and Grok Bot app stores. This page covers its hosted endpoint (https://theopenapps.com/mcp).

### Is the OpenApps MCP server safe to use?

OpenApps scores 84 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 OpenApps MCP server expose?

OpenApps exposes 16 tools: changes_list, new_list, stores_get, charts_get, leaderboards_get, and 11 more. Their descriptions and schemas cost roughly 1,978 tokens of context every time the server is loaded.

### Does the OpenApps MCP server require authentication?

No. We connected to OpenApps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the OpenApps MCP server still maintained?

OpenApps 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 OpenApps MCP server?

VerifyMCP ran 13 checks on OpenApps, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://theopenapps.com/mcp
- Website: https://theopenapps.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps.json
- HTML version of this page: https://verifymcp.io/servers/com-theopenapps-openapps/theopenapps
