Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Linktest 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.
95/100
trust score
18
downloads a day
local
runs on your machine
86
downloads in 30d
What it does
MCP server for LinkTest — automate Google Play closed testing via AI
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user linktest-mcp '--' npx -y linktest-mcp-server
# 2 — ask your agent for something these tools do
# linktest_validate, linktest_verify, linktest_order and 7 more
Linktest costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LMAll 1 server
linktest-mcp-server1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Linktest as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user linktest-mcp '--' npx -y linktest-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
10 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.
Validate a Google Play closed testing opt-in link before placing an order. Checks that the link is correctly formatted and accessible on the Play Store. Always validate the link first before calling linktest_order to catch issues early. Args: - opt_in_link (string): The closed testing opt-in…
No parameter schema on file.
Verify that LinkTest devices can actually access and install the user's app. This triggers a real device to attempt accessing the app on Google Play Store. It checks whether the tester emails are properly registered in the user's closed testing track. IMPORTANT: After calling this tool, wait 30…
No parameter schema on file.
No parameter schema on file.
Check the status of one or all LinkTest orders. If order_id is provided, returns detailed info about that specific order. If omitted, returns a summary list of all orders. Args: - order_id (string, optional): Specific order ID to look up. If omitted, lists all orders. Returns (with order_id):…
No parameter schema on file.
Retrieve screenshot URLs taken by LinkTest devices for an order. Screenshots are captured daily from each Android device running the app. Returns a list of URLs that can be opened in a browser to verify the app is running correctly. Args: - order_id (string): The order ID to get screenshots…
No parameter schema on file.
Cancel or complete an order. Orders in 'pending', 'payment_failed', or 'active' status can be cancelled. - pending/payment_failed → cancelled (order removed) - active → completed (devices uninstall the app) Args: - order_id (string): The order ID to cancel Returns: Confirmation message or…
No parameter schema on file.
Request a free retry for a closed testing order that was rejected by Google Play. After 14+ days of testing, if Google Play rejects the production readiness review, the user can request ONE free retry per order. This extends testing by another 14 days. Conditions: - Order must be "active"…
No parameter schema on file.
View payment history and get receipt details. Returns a list of all payments made, including amounts, dates, and order associations. Optionally provide a payment_id to get a specific receipt. Args: - payment_id (string, optional): Specific payment ID for receipt details. Omit for full history.…
No parameter schema on file.
Get the LinkTest tester email list for Google Play closed testing registration. ALWAYS call this tool FIRST before anything else — registering these emails in Google Play Console is a required prerequisite before an opt-in link even exists. The workflow is: 1. Call THIS TOOL → get the…
No parameter schema on file.
Generate pre-filled answers for the Google Play production readiness survey. After closed testing completes (14+ days), Google Play requires developers to fill out a 9-question survey in the Play Console before the production review. This tool generates complete draft answers based on: -…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public, though no licence is declared for it
- Runs on your machine — nothing of it reaches our gateway
- 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 Linktest or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 95 / 100
Release 1.0.17 · scanned 14 Oct 2026
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.
Threat score100
Client score95
Findings2 threat · 1 capability
Capabilitymoderate
Coveragesource
Verificationnone
Surface digest31caca6edc81296f6ba0e4c59152a4ab5e0c64dde9747675109cff53fff7c445
Score vectorthreat 100 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| linktest_validate | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| linktest_verify | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| linktest_order | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| linktest_status | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| linktest_screenshots | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| linktest_cancel | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| linktest_retry | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| linktest_billing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| linktest_testers | no tags | |
| linktest_survey | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest31caca6edc81296f
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.17. Pin a release below and the command asks for exactly that one.
1.0.17
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Linktest can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.