Tester Exchange
REMOTE · VVRLXZBNGXFXDDYWIDOQ.SUPABASE.CO
Get 12 testers for 14 days for Google Play closed testing, with verified daily use on real phones.
Available components
Last scanned (18 hours ago)
Scores higher than 48% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Testing and QA
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1090 tokens (~49/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 23 Oct 26 0
- Tool “swap_circle_status” rewrote its description, which is the text the model reads security
- Schema quality: 883 → 1090 ▼ functional
- Tool coverage: 67% → 72% ▲ functional
- Schema quality: fair → good functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “fill_from_exchange” functional
- New tool “friends_status” functional
- New tool “start_friends_test” functional
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 64
First indexed and scored.
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 23 Oct 2026 · Probed https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 vvrlxzbngxfxddywidoq.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | 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=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp | Verified | 200 | |
| http (plaintext) | http://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp |
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 →
about ~21
What Tester Exchange is, how credits work, and every available action.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
add_app add app ~98
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)
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| group_url | string | – | Google Group link if the track uses a group |
| instructions | string | – | What testers should try |
| name | string | yes | – |
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
add_testers add testers ~51
Add tester slots to a live campaign (15 credits each). (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
buy_credits_links buy credits links ~28
Checkout links for credit packs. A human must complete the payment. (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
campaign_report campaign report ~52
Testers, daily active testers, feedback and the data needed to answer Play Console's production-access questions. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
fill_from_exchange fill from exchange ~55
Pay credits only for the seats friends and the circle don't fill (15 credits per seat); exchange testers then join. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
friends_status friends status ~71
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)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
join_swap_circle join swap circle ~58
Put one of the user's apps in the free swap circle. Needs the Tester Exchange app on the user's phone (a linked phone). (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
join_test join test ~53
Join another developer's test as a tester. Returns the opt-in steps the human must do on their phone. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
leave_swap_circle leave swap circle ~24
Leave the swap circle while it is still filling. (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_open_tests list open tests ~29
Android apps currently looking for closed-testing testers. With a token, only tests the user can join.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_account my account ~27
The user's credit balance, invite link, phones linked and open tests. (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_apps my apps ~34
The user's apps and the live status of each testing campaign (active testers, waiting installs, open slots). (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_swap_circle my swap circle ~31
The user's swap circle: status, how many developers are in, and the apps. (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_tests my tests ~29
Tests the user is doing as a tester, with verified days and credits earned. (needs a token)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
platform_stats platform stats ~25
Live platform numbers: members, apps testing, open tester slots, verified tester-days.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pricing ~19
How credits are earned and spent, and credit pack prices.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_campaign_status set campaign status ~52
Pause, resume or close a campaign. Closing refunds unused credits. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
| status | string | yes | – |
No output schema declared.
No examples provided.
share_kit share kit ~55
Public "help test my app" page, a ready message and a README badge for one of the user's apps. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
start_campaign start campaign ~64
Start recruiting testers for one of the user's apps. Costs testers × 15 credits, held in escrow; unused credits are refunded. (needs a token)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
| testers | integer | – | – |
No output schema declared.
No examples provided.
start_friends_test start friends test ~74
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)
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | yes | Android package name, e.g. com.example.app |
No output schema declared.
No examples provided.
swap_circle_status swap circle status ~47
How full the next free swap circle is. It starts at 6 developers (or on Monday with at least 3); then everyone tests everyone else's app for 14 days, free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Tester Exchange MCP server?
Tester Exchange is a hosted endpoint at https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/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 · vvrlxzbngxfxddywidoq.supabase.co
claude mcp add --transport http com-testerexchange-tester-exchange 'https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp'
What is the Tester Exchange MCP server?
Tester Exchange is an MCP server listed in the public MCP registry as com.testerexchange/tester-exchange. Get 12 testers for 14 days for Google Play closed testing, with verified daily use on real phones. This page covers its hosted endpoint (https://vvrlxzbngxfxddywidoq.supabase.co/functions/v1/mcp).
Is the Tester Exchange MCP server safe to use?
Tester Exchange scores 65 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 Tester Exchange MCP server expose?
Tester Exchange exposes 22 tools: about, platform_stats, pricing, list_open_tests, my_account, and 17 more. Their descriptions and schemas cost roughly 997 tokens of context every time the server is loaded.
Does the Tester Exchange MCP server require authentication?
No. We connected to Tester Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tester Exchange MCP server still maintained?
Tester Exchange is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.