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.

OpenApps

REMOTE · THEOPENAPPS.COM

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

Available components

+3 this week 84 Trust /100

Last scanned (21 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security80
  • 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. 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability64
  • 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
  • Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 12 Nov 26 0
    • Server version: 8b05ce4c-6ac8-4844-9f7a-0e08314cdb26 → 0079b3b0-c0d3-43c9-857d-b028069450c9 functional
  • 11 Nov 26 +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.

  • 10 Nov 26 0
    • Server version: ff10ee87-587b-4f1e-9631-b6567730c44c → 8b05ce4c-6ac8-4844-9f7a-0e08314cdb26 functional
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 21 Nov 2026 · Probed https://theopenapps.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=theopenapps.com CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 b252a600a93760180e6e0ad576f5ea51
SANs: theopenapps.com, admin.theopenapps.com, *.admin.theopenapps.com
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 theopenapps.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
theopenapps.com. No DS 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
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://theopenapps.com/mcp Verified 200
http (plaintext) http://theopenapps.com/mcp HTTPS enforced 301 https://theopenapps.com/mcp
MCP tools · 16 exposed · ~1,978 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
changes_list ~162

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.

NameTypeReqDescription
appsarray–Listing refs or OpenApps URLs.
contextstring–The user's goal, briefly.
cursorstring––
limitinteger––
regionstring–ChatGPT country code (default us).
response_formatstring––
sincestring–Window start: ISO-8601 or -24h, -7d.
storestringyes–
typesarray–Default: all but release_change.

No output schema declared.

No examples provided.

charts_get ~153

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.

NameTypeReqDescription
atstring–Past time: ISO-8601 or -24h, -7d.
chartstringyesChart name; stores_get lists them.
contextstring–The user's goal, briefly.
cursorstring––
kindsarray–e.g. claude:connector; stores_get lists them.
limitinteger––
regionstring–ChatGPT country code (default us).
response_formatstring––
storestringyes–

No output schema declared.

No examples provided.

featuring_history ~171

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.

NameTypeReqDescription
appstring–Listing ref or OpenApps URL.
atstring–Past time: ISO-8601 or -24h, -7d.
chartstring–Chart name; stores_get lists them.
contextstring–The user's goal, briefly.
cursorstring––
limitinteger––
regionstring–ChatGPT country code (default us).
response_formatstring––
sincestring–Window start: ISO-8601 or -24h, -7d.
storestringyes–

No output schema declared.

No examples provided.

feedback_send ~192

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.

NameTypeReqDescription
detailsstring––
initiatorstringyesuser if the user asked for it, else model.
issuestringyes–
request_idstring–From an error answer.
subject_idstring–Ref, slug or URL.
subject_typestring––
summarystringyesOne line.
toolstring––

No output schema declared.

No examples provided.

fetch ~82

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.

NameTypeReqDescription
idstringyesA search result id: listing:{store}:{plugin_id}, app:{slug}, tag:{id}, chart:{store}:{chart} or server:{url}.
NameTypeReqDescription
idstring––
metadataobject––
textstring––
titlestring––
urlstring––

No examples provided.

leaderboards_get ~137

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.

NameTypeReqDescription
contextstring–The user's goal, briefly.
cursorstring––
kindsarray–e.g. claude:connector; stores_get lists them.
limitinteger––
metricstringyesMetric name; stores_get lists each store's.
response_formatstring––
storestringyes–

No output schema declared.

No examples provided.

listings_copy ~82

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.

NameTypeReqDescription
appstringyesListing ref or OpenApps URL.
contextstring–The user's goal, briefly.
response_formatstring––

No output schema declared.

No examples provided.

listings_profile ~99

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.

NameTypeReqDescription
appsarrayyesListing refs or OpenApps URLs.
contextstring–The user's goal, briefly.
includearray–Sections per profile.
response_formatstring––

No output schema declared.

No examples provided.

listings_search ~135

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.

NameTypeReqDescription
contextstring–The user's goal, briefly.
cursorstring––
kindstring––
limitinteger––
publisherstring–Publisher name, in any form.
querystringyesWords in app names, descriptions or publishers.
response_formatstring––
storestring––

No output schema declared.

No examples provided.

market_get ~62

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

NameTypeReqDescription
contextstring–The user's goal, briefly.
response_formatstring––
storestring––

No output schema declared.

No examples provided.

mcp_toolset_get ~131

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.

NameTypeReqDescription
appstring–Listing ref or OpenApps URL.
atstring–Past time: ISO-8601 or -24h, -7d.
contextstring–The user's goal, briefly.
diff_fromstring–Earlier toolset: snapshot hash or time.
response_formatstring––
serverstring–MCP server URL.

No output schema declared.

No examples provided.

new_list ~151

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.

NameTypeReqDescription
categorystring–Category title (ChatGPT).
contextstring–The user's goal, briefly.
cursorstring––
kindsarray–e.g. claude:connector; stores_get lists them.
limitinteger––
response_formatstring––
sincestring–Window start: ISO-8601 or -24h, -7d.
sortstring––
storestringyes–

No output schema declared.

No examples provided.

scores_list ~120

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

NameTypeReqDescription
chartstring–Chart name; stores_get lists them.
contextstring–The user's goal, briefly.
cursorstring––
limitinteger––
response_formatstring––
storestringyes–

No output schema declared.

No examples provided.

search ~69

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.

NameTypeReqDescription
querystringyesWords in app names, descriptions or publishers.
NameTypeReqDescription
resultsarray––

No examples provided.

stores_get ~109

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.

NameTypeReqDescription
contextstring–The user's goal, briefly.
guidestring––
response_formatstring––
storestring––

No output schema declared.

No examples provided.

tags_get ~123

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.

NameTypeReqDescription
contextstring–The user's goal, briefly.
kindsarray–e.g. claude:connector; stores_get lists them.
limitinteger––
response_formatstring––
storestring––
tagstringyesTag id from tags_tree, e.g. gmail.

No output schema declared.

No examples provided.

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.

remote · theopenapps.com

# add to Claude Code
claude mcp add --transport http com-theopenapps-openapps 'https://theopenapps.com/mcp'
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.