Testflight MCP Server

@orellbuehler/testflight-mcp npm v0.3.2 Source verified

Published by orellbuehler — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Model Context Protocol server for TestFlight & App Store Connect: retrieve beta tester feedback (screenshots, crashes, crash logs), builds, testers, analytics and provisioning over the official App Store Connect API.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • download_analytics_report_segmentingests untrusted input
  • download_finance_reportingests untrusted input
  • download_sales_reportingests untrusted input
  • get_crash_feedbackingests untrusted input
  • get_screenshot_feedbackingests untrusted input
  • list_analytics_report_segmentsingests untrusted input
  • list_ci_artifactsingests untrusted input
  • create_analytics_report_requestno sensitive capability
  • get_appno sensitive capability
  • get_app_store_version_localizationno sensitive capability
Show 31 more tools ↓
  • get_app_store_version_statusno sensitive capability
  • get_beta_app_review_detailno sensitive capability
  • get_beta_tester_metricsno sensitive capability
  • get_buildno sensitive capability
  • get_build_statusno sensitive capability
  • get_build_usage_metricsno sensitive capability
  • get_crash_logno sensitive capability
  • get_diagnostic_logsno sensitive capability
  • get_perf_power_metricsno sensitive capability
  • list_analytics_reportsno sensitive capability
  • list_app_store_version_localizationsno sensitive capability
  • list_app_store_versionsno sensitive capability
  • list_appsno sensitive capability
  • list_beta_app_localizationsno sensitive capability
  • list_beta_groupsno sensitive capability
  • list_beta_testersno sensitive capability
  • list_buildsno sensitive capability
  • list_bundle_idsno sensitive capability
  • list_certificatesno sensitive capability
  • list_ci_build_actionsno sensitive capability
  • list_ci_build_runsno sensitive capability
  • list_ci_issuesno sensitive capability
  • list_ci_productsno sensitive capability
  • list_crash_feedbackno sensitive capability
  • list_customer_reviewsno sensitive capability
  • list_devicesno sensitive capability
  • list_diagnostic_signaturesno sensitive capability
  • list_group_testersno sensitive capability
  • list_profilesno sensitive capability
  • list_review_submissionsno sensitive capability
  • list_screenshot_feedbackno sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.2 latest A 97/100 0 1.13.0 2026-09-10
v0.3.1 A 97/100 0 1.13.0 2026-09-09
v0.2.1 A 97/100 0 1.12.1 2026-08-15

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/orellbuehler-testflight-mcp/badge.svg)](https://mcptrustchecker.com/registry/orellbuehler-testflight-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/orellbuehler-testflight-mcp"><img src="https://mcptrustchecker.com/registry/orellbuehler-testflight-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/orellbuehler-testflight-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @orellbuehler/testflight-mcp --online

Use the free API → How scoring works

More in Developer Tools