Skip to content
ProtocolProbe
Explore

MCP servers › com.apkcube › apkcube

MCP server · registry snapshot 2026-11-04 · last tested 2026-11-04

apkcube MCP server

Registry name com.apkcube/apkcube

by apkcube.com · domain (the registry's namespace rule)Website ↗

Search Android apps, check APK signing and scans, and get verified APK download links. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-04version 1.0.0streamable HTTP36 tools

Summary

com.apkcube/apkcube is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain apkcube.com. On 2026-11-04 ProtocolProbe connected to it in read-only mode and read its inventory: 36 tools, 0 resources and 8 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
36
Last tested
2026-11-04

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-04 (apkcube.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (console_update_listing, console_set_version_notice). That is our reading of the names; we did not call them. Source: our connection, 2026-11-04.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-04
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-03 (registry, as of the 2026-11-04 snapshot)
First listed version
2026-11-03 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-04
Package and repository
checked 2026-11-04
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-03, listed on 2026-11-04 with version 1.0.0 (published 2026-11-03).

Source: the official MCP Registry list on 2026-11-03 and on 2026-11-04.

What it is

What does this server offer?

Observed inventory
36tools
0resources
8prompts

None of its 36 tools are described as changing anything. For 36 the reading was uncertain, so no mark is shown.

  • search_appson 20 other servers

    “Search the APK catalogue by name, publisher or package id.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    5 inputs, 1 required
    • qstringrequired“Search phrase, publisher, or exact package id.”
    • typestring“Restrict to games or apps.”
    • categorystring“Category id from list_categories.”
    • sortstring“Result ordering.”
    • pageinteger“1-based page number, 1–3.”
  • get_appon 28 other servers

    “Full record for one package: description, screenshots, rating, tags, and whether a download would be refused.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • packageNamestringrequired“Android package id, e.g.”
  • check_availabilityon 120 other servers

    “Free.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • packageNamesarrayrequired“Android package ids, 1–100.”
  • list_versionson 27 other servers

    “Every APK/XAPK build held for a package, newest first, each with its SHA-256.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • packageNamestringrequired“Android package id.”
  • get_download_urlon 9 other servers

    “Mint a short-lived signed URL for one build — the newest held unless you pass an apkId from list_versions.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
    • variantIdstring“Optional: an on-demand variant build of that release, from get_variant_status.”
  • request_fetch

    “Ask us to download an app from Google Play when list_versions came back empty.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • packageNamestringrequired“Android package id.”
  • get_fetch_status

    “Where the fetch request_fetch started stands now: FETCHING (keep waiting), READY (call list_versions), or FAILED with a reason.”

    Publisher declares: read-only yes · idempotent no · open-world yes

    1 input, 1 required
    • packageNamestringrequired“Android package id.”
  • request_varianton 1 other server

    “Ask for an on-demand build of an app's newest release that the ordinary download does not carry: every language (`+all-langs`), the 32-bit ARM build (`armeabi-v7a`), both ARM ABIs in one bundle (`uni…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • packageNamestringrequired“Android package id.”
    • variantstringrequired“Which build: `<arch>[+all-langs][@sdkNN|@vcN]` with arch one of arm64-v8a, armeabi-v7a, universal, or `device:<slug>[+all-langs]`.”
  • get_variant_status

    “Where one variant of an app stands: READY with the build (its `variantId` goes to get_download_url), FETCHING (keep waiting, 10–30 seconds between checks), FAILED with a reason (request_variant retri…”

    Publisher declares: read-only yes · idempotent no · open-world yes

    2 inputs, 2 required
    • packageNamestringrequired“Android package id.”
    • variantstringrequired“Which build: `<arch>[+all-langs][@sdkNN|@vcN]` with arch one of arm64-v8a, armeabi-v7a, universal, or `device:<slug>[+all-langs]`.”
  • list_developer_appson 1 other server

    “Every app we hold from one publisher, most-installed first.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    3 inputs, 1 required
    • slugstringrequired“Publisher slug, from an app's developerSlug field.”
    • pageinteger“1-based page.”
    • perinteger“Rows per page, 1–96.”
  • list_categorieson 556 other servers

    “The category taxonomy, for filtering a search.”

    Publisher declares: read-only yes · idempotent yes · open-world no

    Takes no inputs.

  • list_chart

    “A ranked section of the catalogue.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    3 inputs
    • sectionstring“Which chart.”
    • typestring“Restrict to games or apps.”
    • limitinteger“Rows to return, 1–50.”
Show 24 more tools
  • list_similar_apps

    “Apps related to one package — alternatives and neighbours, as the app's page on the site shows them.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • limitinteger“Rows to return, 1–24.”
  • get_play_details

    “Google Play's full store listing for one package, in any storefront: the star histogram, install estimate, IAP price range, release date, declared permissions, content-rating descriptors, legal publi…”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    3 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • langstring“Language code, e.g.”
    • countrystring“Two-letter storefront country, e.g.”
  • list_reviewson 19 other servers

    “One page of Google Play user reviews for a package, live: stars, text, helpful votes, the app version the reviewer ran, and the developer's reply.”

    Publisher declares: read-only yes · idempotent no · open-world yes

    6 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • sortstring“newest (default), rating, or helpfulness.”
    • numinteger“Reviews per page, 1–100.”
    • cursorstring“`nextCursor` from the previous page.”
    • langstring“Language code, e.g.”
    • countrystring“Two-letter storefront country, e.g.”
  • get_version_security

    “What one build actually IS: its SHA-256, the anti-malware verdict, the certificates that signed it, and every Android permission it declares with a plain-English gloss.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • list_sdks

    “What OTHER companies' code is inside an app: the ad, analytics, attribution, crash-reporting, push and sign-in libraries matched in the build, each with its vendor and where it was recognised.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • get_protectionon 1 other server

    “Whether this build is wrapped in a commercial protector — DexProtector, Jiagu, Bangcle, Legu, AppSealing, Google's own PairIP — and what that means for everything else you can find out about it.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • list_trackerson 1 other server

    “The privacy question on its own: which advertising, analytics, install-attribution, crash-reporting, push and social sign-in SDKs are in this build, and nothing else.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • list_permissionson 3 other servers

    “Every Android permission this build declares, sensitive ones first, each with a readable label, its capability family and a sentence saying what the app can actually do with it.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • get_manifeston 10 other servers

    “What the artifact's own AndroidManifest.xml says beyond the permissions it requests — targetSdk, compileSdk, debuggable, cleartext traffic, backup, sharedUserId, install location, uses-feature, uses-…”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • get_raw_scan

    “The whole stored analysis record for one build, exactly as stored and with none of our rules applied — for when you want to judge the facts yourself rather than read our conclusions.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    2 inputs, 1 required
    • packageNamestringrequired“Android package id.”
    • apkIdstring“A specific build from list_versions.”
  • lookup_hash

    “Which app and which build a file checksum names.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • hashstringrequired“An MD5, SHA-1 or SHA-256 hex digest of the file.”
  • lookup_certificateon 3 other servers

    “Every package we hold that one signing certificate is on record for.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    3 inputs, 1 required
    • fingerprintstringrequired“SHA-256 fingerprint of the signing certificate, 64 hex characters, with or without colons.”
    • pageinteger“1-based page.”
    • perinteger“Rows per page, 1–96.”
  • list_developer_certificates

    “Every signing key on record for one publisher's apps — lookup_certificate read the other way round.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • slugstringrequired“Publisher slug, from an app's developerSlug field.”
  • get_signing_history

    “Which certificate signed which releases of a package, and where the key moved.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • packageNamestringrequired“Android package id.”
  • compare_versionson 17 other servers

    “What changed between two releases: permissions gained and lost, whether the signing key moved, size and minimum Android.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    3 inputs, 3 required
    • packageNamestringrequired“Android package id.”
    • fromstringrequired“One release, by version name or version code.”
    • tostringrequired“The other release, by version name or version code.”
  • get_appson 1 other server

    “Summary rows for up to 100 package ids in one call — use this instead of calling get_app in a loop.”

    Publisher declares: read-only yes · idempotent yes · open-world yes

    1 input, 1 required
    • packageNamesarrayrequired“Android package ids, 1–100.”
  • get_accounton 133 other servers

    “How many credits are left on the key you are using, and what that key is.”

    Publisher declares: read-only yes · idempotent no · open-world no

    Takes no inputs.

  • console_list_apps

    “The apps you manage in the APKCube Developers Console — every app of every developer whose team you are on, 50 a page, with your role on each.”

    Publisher declares: read-only yes · idempotent no · open-world no

    1 input
    • pageinteger“1-based page.”
  • console_app_stats

    “Downloads of one of your apps: per UTC day for the last 30 days (with the 30 before for comparison), the lifetime total, and the top countries of the last 7 days.”

    Publisher declares: read-only yes · idempotent no · open-world no

    1 input, 1 required
    • packageNamestringrequired“Package id of an app on your Developers Console team, e.g.”
  • console_list_uploads

    “Builds submitted for your apps from the console or the Publishing API, newest first, with each one's status (uploading, verifying, scanning, held, published, rejected …) and, for a held or rejected b…”

    Publisher declares: read-only yes · idempotent no · open-world no

    1 input
    • packageNamestring“Optional: only this app's uploads.”
  • console_upload_status

    “Where one upload stands, with the scan summary once it has one (VirusTotal counts, signing certificates and how each compares with the keys on record).”

    Publisher declares: read-only yes · idempotent no · open-world no

    1 input, 1 required
    • uploadIdintegerrequired“The upload's id, from console_list_uploads.”
  • console_security_report

    “Every build we store for one of your apps with our scan verdict, VirusTotal counts, signature scheme, how its signing key compares with the keys on record, and any notice you have put on it — plus a …”

    Publisher declares: read-only yes · idempotent no · open-world no

    1 input, 1 required
    • packageNamestringrequired“Package id of an app on your Developers Console team, e.g.”
  • console_update_listing

    “Change the text visitors read on your app's page: the short description (≤80 characters), full description (≤4000, plain text), what's new (≤500) and a YouTube link.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    5 inputs, 1 required
    • packageNamestringrequired“Package id of an app on your Developers Console team, e.g.”
    • summarystring“Short description, up to 80 characters.”
    • descriptionstring“Full description, plain text, up to 4000 characters.”
    • recentChangesstring“What's new in the current release, up to 500 characters.”
    • videoUrlstring“A youtube.com/watch?v= or youtu.be link.”
  • console_set_version_notice

    “Put a warning on one stored build of your app — `vulnerable` or `withdrawn`, a message of up to 300 characters, and optionally the version code to use instead — or lift it (`lift: true`).”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    7 inputs, 2 required
    • packageNamestringrequired“Package id of an app on your Developers Console team, e.g.”
    • apkIdstringrequired“The stored build's apkId, from console_security_report.”
    • liftboolean“True removes the notice; the fields below are ignored.”
    • kindstring“Why the build is pulled.”
    • messagestring“Shown to visitors, up to 300 characters.”
    • recommendedVersionCodeinteger“Optional: the version code visitors should take instead.”
    • blockDownloadboolean“Also refuse downloads of this build.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-04.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 75
Tools with a description
100% of 36
Typical description length
538 characters

The tool set

Counted from the listing

Tools
36
Size of the list
about 29,606 tokens for an agent to load (characters ÷ 4)
Naming
36 of 36 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 36 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-04 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://apkcube.com/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "apkcube": {
      "url": "https://apkcube.com/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "apkcube": {
      "type": "http",
      "url": "https://apkcube.com/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"apkcube","type":"http","url":"https://apkcube.com/api/mcp"}'
Claude Code
claude mcp add --transport http apkcube https://apkcube.com/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "apkcube": {
      "type": "streamableHttp",
      "url": "https://apkcube.com/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "apkcube": {
      "httpUrl": "https://apkcube.com/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.apkcube]
url = "https://apkcube.com/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "apkcube": {
      "url": "https://apkcube.com/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://apkcube.com/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint apkcube.com/api/mcpSession openedmatchesour test · 2026-11-04
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-04

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-04. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.apkcube/apkcube

Answered from the data above

Who publishes com.apkcube/apkcube?

The registry ties the namespace com.apkcube to the domain apkcube.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.apkcube/apkcube need an API key or sign-in?

It opened a session without any credential on 2026-11-04. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.apkcube/apkcube been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-04
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-04, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,182 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 36 tools, 0 resources, 8 prompts.
  4. 4,831 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-11-04; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
remote (hosted by the publisher)
registry · 2026-11-04
MCP capability
prompts, tools
our test · 2026-11-04
Transport
streamable HTTP
registry · 2026-11-04
Required credentials
none declared
registry · 2026-11-04 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-04
Lifecycle status
active
registry · 2026-11-04
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-04

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.apkcube/apkcube: MCP server record.” Data checked 2026-11-04. https://protocolprobe.com/mcp/servers/com.apkcube/apkcube

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.apkcube/apkcube)](https://protocolprobe.com/mcp/servers/com.apkcube/apkcube)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology