Tester Exchange MCP server

Which MCP servers are Tester Exchange's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to Tester Exchange

Whose server it is

Registry namecom.testerexchange/tester-exchangeverified in the MCP registry

The registry name sits under testerexchange.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28

Stateanswerschecked 2026-10-28
Tools17
Server calls itselftester-exchange
Server version1.2.0
Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 285 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 5 of the 7 days it takes to judge reliability.

Once connected

For "recruit real Android testers for a Google Play closed test", the likely first call is get_testers.
add_app, add_testers change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28

INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
Answeredmeasuring5 of the 7 daily checks it takes to print a share
Median first answer216 ms
Space in an agent's context≈ 1,497 tokensthe definitions of all its tools (17), which an agent carries on every turn
Tool definitionsA · 96 of 100
Typed results0 of 17 toolsdeclared outputSchema: results come typed, read once

Parameters without a description: in 4 of 17

What an agent can do with it

can do · recruit real Android testers for a Google Play closed test
not sure · verify daily app use on each tester's phone
not sure · collect tester feedback before requesting production access

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

Tools that change data, on a server that answers without a sign-in: add_app, add_testers

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-28

about
What Tester Exchange is, how credits work, and every available action.
get_testers
START HERE. One call gets an Android app its 12 Google Play closed-testing testers: adds the app if needed, opens its test, applies spare credits, and returns progress plus the few steps only a human can do (add our Google Group in Play…
platform_stats
Live platform numbers: members, apps testing, open tester slots, verified tester-days.
pricing
How credits are earned and spent, and credit pack prices.
my_account
The user's credit balance, invite link, phones linked and open tests. (needs a token)
my_apps
The user's apps and the live status of each testing campaign (active testers, waiting installs, open slots). (needs a token)
add_app
List an Android app that is in Google Play closed testing. The closed track must be published with the opt-in link enabled. (needs a token)
start_campaign
Start recruiting testers for one of the user's apps. Costs testers × 15 credits, held in escrow; unused credits are refunded. (needs a token)
campaign_report
Testers, daily active testers, feedback and the data needed to answer Play Console's production-access questions. (needs a token)
add_testers
Add tester slots to a live campaign (15 credits each). (needs a token)
set_campaign_status
Pause, resume or close a campaign. Closing refunds unused credits. (needs a token)
my_tests
Tests the user is doing as a tester, with verified days and credits earned. (needs a token)
share_kit
Public "help test my app" page, a ready message and a README badge for one of the user's apps. (needs a token)
buy_credits_links
Checkout links for credit packs. A human must complete the payment. (needs a token)
friends_status
Who fills the 12 seats of one of the user's apps (friends, swap circle, exchange testers), how many seats are left, what the exchange would cost for them, and the share link. (needs a token)
start_friends_test
Free: open a test for one of the user's apps so friends and family can join from the share link. Returns the link and a ready message. Their days are verified by the Tester Exchange phone app. (needs a token)
fill_from_exchange
Pay credits only for the seats friends and the circle don't fill (15 credits per seat); exchange testers then join. (needs a token)

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tester-exchange": {
      "type": "http",
      "url": "https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http testerexchange https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp as a custom connector in the settings.

OpenAPI spec

1 paths, read 2026-10-28. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.