com.shonanfarm/sukimalabo-tester
REMOTE · EGBTSQYGTBKDFKYWJOFB.SUPABASE.CO
みんなのテスター（スキマラボ）公開情報MCP。Google Playクローズドテストのテスター集めを支援する相互テストコミュニティの情報を提供する。
Available components
Last scanned (10 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1574 tokens (~393/item across 4 items; 4 tools + 0 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_service_info” rewrote its description, which is the text the model reads security
- Tool “check_optin_link” rewrote its description, which is the text the model reads security
- Tool “how_to_get_testers” rewrote its description, which is the text the model reads security
- Tool “list_recruiting_apps” rewrote its description, which is the text the model reads security
- Schema quality: 199 → 393 ▼ functional
- Server version: 2.2.1 → 2.3.0 functional
- 2 Oct 26 0
- Server version: 2.2.0 → 2.2.1 functional
- 1 Oct 26 0
- Tool “list_recruiting_apps” rewrote its description, which is the text the model reads security
- Server version: 2.0.0 → 2.2.0 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 5 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester
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 | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| 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 egbtsqygtbkdfkywjofb.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://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester | Verified | 200 | |
| http (plaintext) | http://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester | HTTPS enforced | 301 | https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester |
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 →
check_optin_link テスト参加URLの形式診断 ~310
Google Playのテスト参加URLの形式を、ログインなしで診断する。クローズドテストの参加URL（https://play.google.com/apps/testing/<パッケージ名>）の形か、要件に数えられない内部テストのURLや公開ストアのページではないかを判定し、理由と直し方を日本語と英語で返す。利用者が、配っている参加URLが正しいかを確かめたいときや、テスターが参加したのにPlay Consoleの人数が増えない原因を探すときに使う。形式だけを見る診断で、そのURLを開かず、そのテストが実在するか・公開中かは確認しない。 / Checks the format of a Google Play testing opt-in URL (closed test vs. internal test vs. store page) and returns the reason and how to fix it, in Japanese and English. Use it when the user wants to check the link they share with testers, or when testers joined but the Play Console count does not go up. Format check only: it does not open the URL and does NOT verify that the test exists or is open.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 診断するURL（例 https://play.google.com/apps/testing/com.example.app） / The URL to check (e.g. https://play.google.com/apps/testing/com.example.app) |
No output schema declared.
No examples provided.
get_service_info みんなのテスターの概要といまの状態 ~279
みんなのテスター（運営：スキマラボ）の概要・仕組み（シート）・テスターとして参加する流れ・いまの新規の掲載受付の状態・約束しないことを返す。みんなのテスターは、Google Playのクローズドテスト（テスター12人×14日間）に必要なテスターを、会員どうしの相互テストで集めるための日本語のWebサービス。利用者が『みんなのテスターとは何か』『どうやって参加・掲載するのか』『いま新しく掲載できるか』を知りたいときに使う。数字はすべて運営の設定から読んだ、呼んだ時点の値。 / Returns an overview of "Minna no Tester" (a Japanese mutual-testing service for Google Play closed testing, 12 testers x 14 days): how it works, how to join as a tester, whether new listings are being accepted now, and what it does NOT promise. Use it when the user asks what the service is, how to join or list an app, or whether a new app can be listed now. Numbers are read from the operator's settings at call time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_get_testers テスターの集め方 ~194
Google Playのクローズドテスト用のテスター（テスター12人×14日間）を集める主な方法を、費用の目安と注意点つきで返す。みんなのテスターに限らない一般的な説明で、最後にみんなのテスターの仕組みを短く添える。利用者が『クローズドテストのテスターをどうやって集めればいいか』『人数が集まらない』と聞いたときに使う。 / Explains the main ways to gather testers for Google Play closed testing (12 testers x 14 days), with typical costs and cautions. General guidance, not limited to this service; a short note about Minna no Tester is added at the end. Use it when the user asks how to get testers for closed testing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recruiting_apps テスター募集中の掲載一覧 ~248
みんなのテスターで、いまテスターを募集中のアプリ（掲載）の一覧を返す。利用者が『いまテストできるアプリは』『テスターとして参加したい』と聞いたときに使う。人数は出所（掲載者がPlay Consoleで確認した人数／このサイトでの参加申告）と日付を必ず添えて返すので、利用者に伝えるときも出所と日付を省かないこと。テストに参加するには、サイトでの会員登録が必要。「預けた枚数の残り」は人数の上限ではない（1本のアプリをテストできる人数に上限はない）。 / Lists the apps currently recruiting testers on Minna no Tester. Use it when the user asks which apps they can test now or wants to join as a tester. Every tester count comes with its source (owner-reported Play Console count with its date, or self-declared on this site); keep the source and date when relaying. Joining a test requires signing up on the website.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.shonanfarm/sukimalabo-tester MCP server?
com.shonanfarm/sukimalabo-tester is a hosted endpoint at https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester, 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 · egbtsqygtbkdfkywjofb.supabase.co
claude mcp add --transport http com-shonanfarm-sukimalabo-tester 'https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester'
What is the com.shonanfarm/sukimalabo-tester MCP server?
com.shonanfarm/sukimalabo-tester is an MCP server listed in the public MCP registry as com.shonanfarm/sukimalabo-tester. みんなのテスター（スキマラボ）公開情報MCP。Google Playクローズドテストのテスター集めを支援する相互テストコミュニティの情報を提供する。 This page covers its hosted endpoint (https://egbtsqygtbkdfkywjofb.supabase.co/functions/v1/sukimalabo-tester).
Is the com.shonanfarm/sukimalabo-tester MCP server safe to use?
com.shonanfarm/sukimalabo-tester 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 com.shonanfarm/sukimalabo-tester MCP server expose?
com.shonanfarm/sukimalabo-tester exposes 4 tools: get_service_info, list_recruiting_apps, how_to_get_testers, check_optin_link. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Does the com.shonanfarm/sukimalabo-tester MCP server require authentication?
No. We connected to com.shonanfarm/sukimalabo-tester without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.shonanfarm/sukimalabo-tester MCP server still maintained?
com.shonanfarm/sukimalabo-tester is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.