# AppForShare (npm · appforshare-mcp)

Share iOS and Android test builds: upload, install links, testers, store readiness and releases.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `appforshare.io`: 37/100, [markdown](https://verifymcp.io/servers/io-appforshare-appforshare/api-mcp.md), [page](https://verifymcp.io/servers/io-appforshare-appforshare/api-mcp)
- npm · `appforshare-mcp`: 76/100 (this document), [markdown](https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp.md), [page](https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp)

## Channel facts

- Registry: `npm`
- Package: `appforshare-mcp`
- Version: `1.0.11`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 7800 tokens (~136/item across 57 items; 57 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 68% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AppForShare MCP server?

AppForShare runs locally as an npm package, launched with npx -y appforshare-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add io-appforshare-appforshare -- npx -y appforshare-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-appforshare-appforshare": {
      "command": "npx",
      "args": [
        "-y",
        "appforshare-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-appforshare-appforshare": {
      "command": "npx",
      "args": [
        "-y",
        "appforshare-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-appforshare-appforshare -- npx -y appforshare-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-appforshare-appforshare": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "appforshare-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-appforshare-appforshare --command npx --arg -y --arg appforshare-mcp
```

### Hermes

```yaml
mcp_servers:
  io-appforshare-appforshare:
    command: "npx"
    args: ["-y", "appforshare-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-appforshare-appforshare": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "appforshare-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-appforshare-appforshare -t stdio -c npx -a -y appforshare-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-appforshare-appforshare": {
      "command": "npx",
      "args": [
        "-y",
        "appforshare-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 72, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-11 (score 72, 0)

- [functional regression] Schema quality: 6808 → 7800
- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 1.0.10 → 1.0.11

### 2026-11-10 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 71, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [functional regression] Schema quality: 5261 → 6808
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.0.8 → 1.0.10
- [functional] Package version: 1.0.8 → 1.0.9

## MCP tools (57)

### `upload_build` (~182 tokens)

Upload a build

Upload an .ipa, .apk or .aab from this computer to AppForShare and return its install link and store readiness result. An .aab is turned into one APK for testers. Pro and Team also share desktop builds (.dmg, .pkg, zipped .app, .msix, .msixbundle, .appx, .appxbundle, .msi), which testers download from the install page. Optional release notes and a channel (such as beta) whose stable link then opens this build.

Input parameters:

- `channel` (string): Put the build into this channel when it is ready (Pro and Team)
- `notes` (string): Release notes shown to testers (Pro and Team)
- `path` (string, required): Path to the build file (.ipa, .apk, .aab, or a desktop build on Pro and Team)

### `check_local_build` (~141 tokens)

Check a local build before sharing

Check an .ipa, .apk or .aab on this computer without uploading it: the store readiness check (App Store and Google Play rules, each finding with a fix), why a phone would refuse to install it (signing, provisioning profile, bundle ID, test only, v1 only signature), and the Security scan counts. The file never leaves this computer. With a Pro or Team token the Security scan findings (masked secrets, MASVS category, fix) are included too. Guidance only, not a promise of store approval. Read only.

Input parameters:

- `path` (string, required): Path to the .ipa, .apk or .aab file

### `whoami` (~45 tokens)

Who am I

The account, plan and role this AppForShare token works in, and whether the workspace requires two step sign in for members (read only; the rule is set in the dashboard).

### `list_projects` (~27 tokens)

List projects

Projects (one per app and platform) in the account, newest first, with their ids.

### `list_builds` (~125 tokens)

List builds

Recent builds with install link, version, size, installs, store readiness status, channels and the known malware check status.

Input parameters:

- `app` (string): Bundle id (iOS, macOS) or package name (Android, Windows MSIX)
- `channel` (string): Channel name such as beta or live: builds in that channel, newest put in first
- `limit` (integer)
- `platform` (string): Only builds of this platform (macos and windows = desktop builds, Pro and Team)
- `project` (integer): Project id from list_projects

### `latest_build` (~112 tokens)

Latest build

The newest build matching the filters, with its install link, release notes and store readiness findings.

Input parameters:

- `app` (string): Bundle id (iOS, macOS) or package name (Android, Windows MSIX)
- `channel` (string): Channel name such as beta or live: builds in that channel, newest put in first
- `platform` (string): Only builds of this platform (macos and windows = desktop builds, Pro and Team)
- `project` (integer): Project id from list_projects

### `build_info` (~326 tokens)

Build details and store readiness

One build: install link, version, installs, release notes, permissionsPlain (each permission in plain words: what it lets the app do, the app's own iOS reason verbatim, and isNew against the previous build of the app; facts, not a safety verdict) and the store readiness check (App Store and Google Play rules) with a fix for each finding. Expo apps also get their Expo facts (SDK, expo-updates runtime version, update channel and URL, development client) and the Expo checks (development build shared with testers, test build on the production channel, runtime version against native changes). Flutter apps also get their Flutter facts (build mode, engine and Dart version, obfuscation hint, Impeller flag) and the Flutter checks (debug or profile build shared with testers). malwareScan is the check for known malware run on every upload (status pending, clean, flagged, error or skipped, and scannedAt; it only finds malware that is already known, and a flagged build is held for staff review). desktop is set for macOS and Windows builds (Pro and Team): file kind, SHA-256, minimum OS, architectures, signature (developer-id, apple, adhoc, signed, unsigned) and signer, notarization ticket stapled or not (macOS), publisher and package name; testers download the file from the install page, and readiness lists unsigned, ad hoc signed and not notarized files. Guidance only, not a promise of store approval.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `get_security_scan` (~179 tokens)

Security scan of a build

Security scan of one build, read at upload from the .ipa or .apk: hardcoded secrets (only the kind, the file and a masked value, never the full key), Android backup, exported components, R8 hint, WebView debugging and user certificates, iOS App Transport Security exceptions, symbols and get-task-allow, root, jailbreak and tamper libraries, and library versions with a known advisory. Each finding has a level (block, warn, info), an OWASP MASVS category, a detail and a fix; the summary counts them ("1 to fix, 3 warnings"). Findings and hints from a static scan, not a penetration test or a certification. Builds uploaded before the scan say status unknown. Read only. Pro and Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `get_install_badge` (~182 tokens)

Download button for a README

A download button for a README or docs page: Markdown and HTML snippets with a 200 x 60 "Install test build" badge (dark and light) that links to the install page of a build, or to a channel link. For a channel the badge is live: it shows the version of the newest build in the channel (refreshed every 5 minutes) and the link always opens that build. Give a build id or install link slug, or a channel address (the part after /c/). The link carries ?ref=badge so visits from the button show in analytics. The badge says "test build" and never names a store. Read only. Free and up for builds; channels need Pro or Team.

Input parameters:

- `target` (string, required): Build id, install link slug, or channel address (the part after /c/)

### `build_installs` (~63 tokens)

Who installed a build

Installs of one build, newest first (up to 200): device, OS version, model, country and the tester when known, with totals by device and country. Read only.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `build_install_issues` (~119 tokens)

Why a tester cannot install a build

Why testers' phones may refuse one build: signing (App Store or unsigned), profile expired or ending soon, no devices in the profile, Developer Mode, enterprise trust, test key, plus the minimum iOS or Android version, and how many devices the profile lists. Use it to answer "my tester cannot install". Pass the tester's UDID to check their device too. Read only.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `udid` (string): Tester device UDID (optional)

### `export_test_plan` (~113 tokens)

Export the test plan for Firebase or Maestro

The build's AI test plan as a file other tools run: format "firebase" gives Firebase App Testing agent test cases (YAML for firebase apptesting:execute --test-dir, Android only, preview), "maestro" a Maestro starter flow with a screenshot and an assertWithAI check per task. Needs a plan (test_plan with generate: true). Read only. Pro and Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `format` (string)

### `test_plan` (~141 tokens)

Test plan for a build

The AI test plan of a build: up to 15 tasks ordered by risk, each with steps and the fact it comes from (a new permission, a minimum OS change, a readiness finding, the release notes), and which tasks the team ticked as done. Pass generate: true to write a new plan when there is none or the build changed; that uses 1 AI action of the account (Developer role). focus narrows it, for example "payments".

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `focus` (string): Optional area to focus on, with generate
- `generate` (boolean)

### `github_build_run` (~166 tokens)

GitHub build runs and why one failed

iOS and Android builds AppForShare started on the workspace's GitHub Actions. Without run: the recent runs, newest first, with their result. With run (an id from that list): that run, and for a failed one the AI explanation of the likely cause and the fix steps, written from the failed job's log with secrets taken out (shown when AppForShare already made one). Pass explain: true to make one when there is none (1 AI action of the account, Developer role); it never changes code or the repository. Pro and Team.

Input parameters:

- `explain` (boolean): Make the AI explanation of a failed run when there is none (1 AI action)
- `limit` (integer)
- `run` (integer): Run id from the list

### `list_feedback` (~162 tokens)

Tester feedback

Feedback testers sent from install pages and the in-app link, and on Team the TestFlight screenshot and crash feedback read from App Store Connect: bug reports, suggestions and other notes, newest first, with the source (page, app or testflight), the device, OS, build (and the TestFlight build) and how many screenshots or recordings came with it (open them in the dashboard link), and on Team the reply thread (team replies and tester answers). Read only.

Input parameters:

- `blockers` (boolean): Only reports marked as release blockers
- `build` (string): Optional build id or install link slug
- `source` (string): Only reports from the install page, the in-app link, or TestFlight (Team)
- `status` (string)

### `recent_activity` (~77 tokens)

Workspace activity

What happened in the workspace, newest first: uploads, channel changes, tester feedback, tasks, release checklist ticks, link controls and issues sent to trackers, each with who did it. Optional project id and kind. Read only. Team.

Input parameters:

- `kind` (string)
- `limit` (integer)
- `project` (integer)

### `task_from_feedback` (~65 tokens)

Make a task from tester feedback

Add a task to the project's task board from one feedback report, linked to its build. Once per report. Ask the person first and pass confirm: true. Team, Developer role.

Input parameters:

- `confirm` (boolean, required)
- `id` (integer, required): Feedback id from list_feedback

### `send_feedback_to_tracker` (~93 tokens)

Send tester feedback to Linear or Jira

Create an issue in the workspace's connected Linear or Jira from one feedback report, with its text, device facts and screenshots. A report is sent once; the answer has the issue key and link. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `confirm` (boolean, required)
- `id` (integer, required): Feedback id from list_feedback
- `tracker` (string, required)

### `resolve_feedback` (~74 tokens)

Mark tester feedback resolved

Mark a feedback report as resolved (for example after the fix is in a new build), or open it again with reopen: true. Ask the person first and pass confirm: true. Developer role.

Input parameters:

- `confirm` (boolean, required)
- `id` (integer, required): Feedback id from list_feedback
- `reopen` (boolean)

### `reply_to_feedback` (~153 tokens)

Reply to tester feedback

Reply to one feedback report. The reply is kept in the report's thread and the tester gets one email in the language of their install page, with the reply and a link to answer once on the install page. Only for reports where the tester left an email address (not TestFlight reports); up to 20 messages per report and 5 replies per report a day. Write the reply the person asked for, plain text up to 2000 characters, and show it to them first; then pass confirm: true. Team, Developer role.

Input parameters:

- `confirm` (boolean, required)
- `id` (integer, required): Feedback id from list_feedback
- `text` (string, required): The reply, as the person approved it

### `release_checklist` (~105 tokens)

Release checklist of a build

The workspace release checklist with what is ticked on this build, its named approvals (who approves each approval step, approved, rejected with a note, or pending), the open release blockers of its project, and whether the gated channel (Live by default) would take it. Read only: approvals are given only by the approver signed in to the dashboard, never by an AI tool. Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `release_overview` (~214 tokens)

Release page of a version

One version of an app in one answer, like the release page: its iOS and Android builds with channels and store readiness, the release checklist and approvals of the newest build per platform, open release blockers from tester feedback, App Store and TestFlight state, Google Play tracks with rollout percentage, Android vitals (crash rate and ANR rate per version code from Google Play, Team, read only and never acted on), and a timeline of who did what. Give the version (like 2.4.0) and the app as its bundle id or package name, or a project id. Without a version it lists the versions. Read only. Team (Pro gets it without the checklist).

Input parameters:

- `app` (string): Bundle id (iOS, macOS) or package name (Android, Windows MSIX)
- `project` (integer): Project id from list_projects
- `version` (string): Version as in the build, like 2.4.0. Leave out to list versions.

### `tick_release_step` (~131 tokens)

Tick a release checklist step

Tick (or untick with done: false) one step of the release checklist on a build, by its key from release_checklist. Only tick what the person says was really done. Approval steps (those with an approver) cannot be ticked or approved here; the approver answers them in the dashboard. Ask the person first and pass confirm: true. Team, Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `done` (boolean)
- `key` (string, required): Step key from release_checklist

### `promote_build` (~135 tokens)

Put a build into a channel

Make a build the newest in a channel (for example beta or live) so the channel link and QR code open it. Using an older build rolls the link back; apps already installed are not changed. On Team the gated channel (Live by default) refuses a build until its release checklist is ticked and no release blocker is open; see release_checklist. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `channel` (string, required): Channel name, created on first use
- `confirm` (boolean, required)

### `set_link_controls` (~266 tokens)

Pause or limit an install link

Change the controls of one build's install link: pause or resume it, set a start time before which it takes no installs (testers see when it opens and can ask for one email then; ISO date time, null opens it now), a stop date after which it takes no installs (ISO date time, null removes it), or an install limit (null removes it). The start must be before the stop date. Leave out what should stay as it is. Builds already installed are not affected. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `maxInstalls` (integer|null): Install limit, or null for none
- `paused` (boolean): true pauses the link, false turns it back on
- `startAt` (string|null): Opens for installs at this ISO 8601 date time, for example 2026-12-01T09:00:00Z, or null to open now
- `stopAt` (string|null): ISO 8601 date time, for example 2026-12-31T23:59:59Z, or null for no stop date

### `retire_build` (~176 tokens)

Retire a test build

Mark one build as retired ("use a newer build"), for example when it crashes on start: its install link takes no installs, its page sends testers to the newest build of the same app and platform, channels skip it (a channel falls back to the build before), and the update check answers retired: true and minBuild for it. Optional reason (up to 200 characters) is shown to testers. undo: true brings it back. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `reason` (string): Shown to testers, for example Crashes on login, use 2.5 (122)
- `undo` (boolean): true brings a retired build back

### `list_build_links` (~81 tokens)

List extra share links of a build

The extra share links of one build: label, URL, install count, whether a password is set, stop date, install cap and state (LIVE, or why it takes no installs), with the plan limit (Pro 3, Team 20 per build). Read only.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `add_build_link` (~253 tokens)

Add an extra share link to a build

Make another install link for one build, for example one per client, with its own label, optional password (4 to 128 characters), optional start time and stop date (ISO date times, start before stop) and optional install cap. It opens the same install page with its own count; the build's pause, stop date and cap still apply. Returns the new URL. Ask the person first and pass confirm: true. Pro (3 per build) and Team (20 per build), Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `expiresAt` (string): Stop date, ISO 8601 date time, for example 2026-12-31T23:59:59Z
- `label` (string, required): Name for the owner, for example Client A (testers do not see it)
- `maxInstalls` (integer): Install cap for this link
- `password` (string): Password for this link only
- `startAt` (string): Opens for installs at this ISO 8601 date time, for example 2026-12-01T09:00:00Z

### `remove_build_link` (~80 tokens)

Remove an extra share link

Turn off one extra share link (by its slug from list_build_links). Its page says the link was turned off; the build and its other links keep working. This cannot be undone. Ask the person first and pass confirm: true. Developer role.

Input parameters:

- `confirm` (boolean, required)
- `link` (string, required): Slug of the extra link

### `list_access_codes` (~104 tokens)

List access codes of a build or extra link

The per tester access codes of a build's own page (build id or slug) or of one extra link (its slug): label, devices used of the allowed count, state (ACTIVE, USED or REVOKED) and when it was made. The codes themselves are never shown again after they are made. Up to 25 per page. Team. Read only.

Input parameters:

- `target` (string, required): Build id, build slug, or the slug of an extra link

### `create_access_code` (~181 tokens)

Create a per tester access code

Make a one off access code for a build's own page or for one extra link, with a label (the client or person it is for) and a device count (1 to 50, default 1). A tester types it on the install page instead of the shared password; each install takes one device off the code. Returns the code once: give it to the person, it cannot be shown again. Ask the person first and pass confirm: true. Team, Owner or Admin role.

Input parameters:

- `confirm` (boolean, required)
- `label` (string, required): Who it is for, for example Ana at Client A (testers do not see it)
- `maxInstalls` (integer): Devices the code may install on (default 1)
- `target` (string, required): Build id, build slug, or the slug of an extra link

### `revoke_access_code` (~83 tokens)

Revoke an access code

Turn off one access code (by its id from list_access_codes). It stops opening the page at once; installs already made stay, and the shared password and other codes keep working. This cannot be undone. Ask the person first and pass confirm: true. Owner or Admin role.

Input parameters:

- `confirm` (boolean, required)
- `id` (integer, required): Access code id

### `set_channel_address` (~167 tokens)

Pick a channel address

Give a channel its own address, for example /c/acme-beta: 3 to 40 lower case letters, digits and hyphens, unique on AppForShare. The old address keeps redirecting for 30 days and the in-app update check on it keeps working; old addresses are never given to anyone else. Name the app by bundle id (app) or project id. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `app` (string): Bundle id or package name of the app
- `channel` (string, required): Channel name such as beta
- `confirm` (boolean, required)
- `project` (integer): Project id, instead of app
- `slug` (string, required): New address, for example acme-beta

### `set_testflight_link` (~173 tokens)

TestFlight link on a channel

Add the TestFlight public link (https://testflight.apple.com/join/...) to a channel such as beta, so iPhone and iPad visitors of the channel link go to TestFlight while Android visitors still get the newest APK, with one link and QR code. Pass url: null to remove it. Name the app by bundle id (app) or project id. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `app` (string): Bundle id or package name of the app
- `channel` (string, required): Channel name such as beta, created on first use
- `confirm` (boolean, required)
- `project` (integer): Project id, instead of app
- `url` (string|null, required): TestFlight public link, or null to remove it

### `channel_followers` (~140 tokens)

Channel followers

How many people follow a channel by email ("Email me new builds" on its page): confirmed and pending counts, the plan cap and masked addresses (jo***@example.com), newest first. Followers confirm by email first and get one email per new build, at most one every 6 hours. Read only: removing a follower is in the dashboard or the CLI. Name the app by bundle id (app) or project id. Pro and Team.

Input parameters:

- `app` (string): Bundle id or package name of the app
- `channel` (string, required): Channel name such as beta
- `project` (integer): Project id, instead of app

### `delete_build` (~68 tokens)

Delete a build

Delete a build. Its install link stops working at once; it can be restored from the dashboard for 7 days. Ask the person first and pass confirm: true. Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)

### `restore_build` (~101 tokens)

Restore a deleted build

Bring back a build that was deleted in the last 7 days: its install link works again with the same address. Without a build, lists the builds that can still be restored. Builds removed by AppForShare staff cannot be restored here. Ask the person first and pass confirm: true. Developer role.

Input parameters:

- `build` (string): Build id or slug of the deleted build; leave out to list what can be restored
- `confirm` (boolean)

### `resign_build` (~293 tokens)

Re-sign an iOS build with a new profile

Re-sign an iOS build with a new provisioning profile, for example after new test iPhones were added to the ad hoc profile, so testers can install without a new build from Xcode or CI. AppForShare signs a copy with the workspace's signing certificate (an Admin adds the .p12 once in Settings) and saves it as a NEW build ("re-signed from build X", same release notes, new SHA-256); the original build and its sign-offs stay as they were. Bundle ID, version and build number never change. Profiles come from the connected App Store Connect key: pass profile names or ids, or leave out for the best active ad hoc, development or enterprise profile of the app. App Store profiles are refused. Without confirm: the check only (profiles, certificate, devices added or dropped, problems). With confirm: true (ask the person first) the re-sign is queued; follow it with build_info (resign.lastResign). Developer role. Pro and Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean)
- `mergeEntitlements` (boolean): Keep the app's own entitlements where the profile allows them (default: entitlements from the profile)
- `profiles` (array): Names or ids of profiles on the connected Apple account (optional; leave out for the best one for the app)

### `cleanup_preview` (~210 tokens)

Preview a clean up of old builds

Which builds of a project an automatic clean up would move to the 7 day restore list right now, the storage it would free, and which old builds it keeps on purpose (newest build of each platform, a channel's current build, builds in a client delivery, builds sent to TestFlight or Google Play in the last 90 days, builds marked keep). Uses the project's saved rule, or keep (newest N per platform, 5 to 200) and olderDays (30, 60, 90 or 180) if given; with both, a build goes only when it breaks both. Read only: nothing is deleted. The rule is set on the project's Testing page; a person runs a clean up with the CLI (appforshare cleanup). Pro and Team.

Input parameters:

- `keep` (integer): Keep the newest N builds per platform
- `olderDays` (integer): Remove builds older than this many days
- `project` (integer, required): Project id from list_projects

### `list_webhooks` (~138 tokens)

List webhooks and recent deliveries

Slack, Microsoft Teams, Google Chat, Discord, Telegram, Webex and generic webhooks of the workspace: name, kind, events, project, on or off, failures, last error, and with webhook (an id) its last 30 deliveries (event, delivered or failed, HTTP status, error). Never returns a webhook URL or signing secret. Adding or changing webhooks is done in the dashboard; a person can resend a delivery with the CLI (appforshare webhooks redeliver). Read only. Pro and Team, Owner or Admin.

Input parameters:

- `webhook` (integer): Webhook id: also return its recent deliveries

### `create_upload_link` (~189 tokens)

Make a one time upload link

Make a link where the person drops an .ipa, .apk or .aab (on Pro and Team also a desktop build: .dmg, .pkg, zipped .app, .msix, .msixbundle, .appx, .appxbundle or .msi) in a browser, for chat assistants that cannot read files on their computer. The link works once, for 30 minutes, on any device, without signing in; the build goes into this workspace as the person who connected, with the plan's limits. Give the person the url, then call check_upload with the ticket for the install link and store readiness. Optional release notes and a channel. Pro and Team, Developer role.

Input parameters:

- `channel` (string): Put the build into this channel (such as beta) when it is ready
- `notes` (string): Release notes shown to testers

### `upload_from_url` (~207 tokens)

Upload a build from a URL

Upload an .ipa, .apk or .aab (or a desktop build: .dmg, .pkg, zipped .app, .msix, .msixbundle, .appx, .appxbundle, .msi) that is at a public https URL, such as a GitHub release asset or a signed CI artifact link: AppForShare checks the size first, then downloads it into this workspace. Links that need a sign in, plain http, and private or local addresses are refused. Returns a ticket; call check_upload with it for progress, the install link and store readiness. Optional release notes and a channel. Pro and Team, Developer role.

Input parameters:

- `channel` (string): Put the build into this channel (such as beta) when it is ready
- `notes` (string): Release notes shown to testers
- `url` (string, required): https URL of the build file (.ipa, .apk, .aab or a desktop build)

### `check_upload` (~85 tokens)

Result of an upload link or URL upload

State of an upload started with create_upload_link or upload_from_url in this workspace: waiting (link not used yet), expired, uploading (with bytes received), processing, ready (install link, and the store readiness check with a fix for each finding) or failed (with the reason). Read only.

Input parameters:

- `ticket` (string, required): Ticket from create_upload_link or upload_from_url

### `email_build_link` (~96 tokens)

Email the install link

Email one build's install link to up to 5 addresses (one plain mail each, no tracking; an address that already got this build is skipped). Not for private projects: add testers there. Ask the person first and pass confirm: true. Developer role. Pro and Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `emails` (array, required)

### `release_status` (~73 tokens)

App Store and Google Play release status

Release status of the apps shared from connected App Store Connect and Google Play accounts: App Store versions and review state, recent TestFlight builds, Google Play tracks and rollout, plus recent changes. Read only. Pro and Team.

Input parameters:

- `app` (string): Optional bundle id, package name or app name to narrow the result

### `list_reviews` (~81 tokens)

Store reviews

Customer reviews of the shared App Store and Google Play apps from the reviews inbox. Read only: replies are written and posted by a person in the dashboard. Pro and Team.

Input parameters:

- `app` (integer): App id from release_status
- `page` (integer)
- `rating` (integer)
- `view` (string): open = needs a reply

### `list_testers` (~62 tokens)

List testers

Testers of the workspace with their projects and groups, optionally only those of one project (id) or one group (name). Read only. Team.

Input parameters:

- `group` (string): Tester group name
- `project` (integer): Project id from list_projects

### `list_tester_groups` (~31 tokens)

List tester groups

Tester groups of the workspace with member counts and the projects each group can install. Read only. Team.

### `add_testers` (~98 tokens)

Add testers

Add email addresses as testers, optionally to a project (id) and to tester groups (names). New testers get an invite email unless notify is false. Ask the person first and pass confirm: true. Team, Developer role.

Input parameters:

- `confirm` (boolean, required)
- `emails` (array, required)
- `groups` (array): Tester group names
- `notify` (boolean)
- `project` (integer): Project id from list_projects

### `remove_testers` (~76 tokens)

Remove testers

With a project id: take away the access given by hand to that project (access through a group stays). Without: remove the testers from the workspace. Ask the person first and pass confirm: true. Team, Developer role.

Input parameters:

- `confirm` (boolean, required)
- `emails` (array, required)
- `project` (integer)

### `share_build_with_testers` (~94 tokens)

Share a build with groups and testers

Give tester groups (names) and testers (emails) the project of an uploaded build and email them its install link. Ask the person first and pass confirm: true. Team, Developer role.

Input parameters:

- `build` (string, required): Build id or the slug of its install link
- `confirm` (boolean, required)
- `groups` (array)
- `notify` (boolean)
- `testers` (array)

### `release_defaults` (~113 tokens)

Saved release defaults of store apps

Saved release defaults of the shared App Store and Google Play apps: What's New per language, phased release on or off (App Store), and the Google Play track and rollout percent used when promoting. They only fill in forms; nothing is sent to a store from them. Without app, every shared app. Read only. Pro and Team.

Input parameters:

- `app` (string): Bundle id, package name or app id from release_status (optional)
- `store` (string): Only when the same bundle id is on both stores

### `set_release_defaults` (~180 tokens)

Save release defaults of a store app

Save the release defaults of one shared store app: whatsNew (list of { language, text }, replaces the saved list; App Store up to 4000 characters, Google Play 500), phased (App Store, true or false), playTrack and playPercent (Google Play; percent 100 = everyone, null = draft). Fields left out keep their value; null clears one. Only saved in AppForShare, never sent to a store. Ask the person first and pass confirm: true. Pro and Team, Developer role.

Input parameters:

- `app` (string, required): Bundle id, package name or app id
- `confirm` (boolean, required)
- `phased` (boolean|null)
- `playPercent` (number|null)
- `playTrack` (string|null)
- `store` (string)
- `whatsNew` (array)

### `get_store_pages` (~194 tokens)

Store pages of store apps

Store pages of the shared App Store and Google Play apps: the privacy policy, support and account deletion page addresses, status (draft, live, lapsing = the plan no longer covers it and it goes down on downAt, down), unpublished changes, what is still missing before publishing, and the facts read from the newest build (permissions in plain words, iOS reasons, recognised SDKs). The pages are written from the owner's answers; they are not legal advice and do not make an app compliant or approved by a store. Editing, the AI draft and publishing happen in the dashboard or the CLI, never from here. Without app, every shared app. Read only. Pro (one app) and Team (every app).

Input parameters:

- `app` (string): Bundle id, package name, app id or page address code (optional)
- `store` (string): Only when the same bundle id is on both stores

### `rollout_plan` (~104 tokens)

Scheduled Google Play rollout plans

Scheduled staged rollout plans of one shared Google Play app: release, steps (percent and hours after the step before), which steps are done, next step time, status (ACTIVE, PAUSED, HALTED by a safeguard, STOPPED, DONE) and why. Plans are set, paused, resumed and stopped by a person in the dashboard or the CLI, never from here. Read only. Team.

Input parameters:

- `app` (string, required): Package name or app id from release_status

### `store_upload_status` (~196 tokens)

Store sends of a build (TestFlight, Google Play)

Whether a build can be sent to TestFlight (App Store signed .ipa) or a Google Play track (the kept .aab) and why not, the shared store app it would go to, and every send so far with its status (queued, sending, processing at Apple, finishing = waiting for Apple to process the build before the send options, sent, draft on Play production, failed) and the store answer. Each send lists the options the Admin picked (TestFlight What to Test, TestFlight groups and beta review on Team; Google Play release name, in-app update priority, changes not sent for review) and what happened to each. Sending and picking options is done by an Admin in the dashboard or with the CLI (appforshare store-upload, upload --store-upload), never from here. Read only. Pro and Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

### `intune_status` (~194 tokens)

Microsoft Intune sends of a build

Whether a build can be sent to the workspace's Microsoft Intune as a line of business app (an enterprise or ad hoc signed .ipa, or an APK; App Store or development signed .ipa files and .aab uploads cannot) and why not, the status of the Intune connection (OK, ERROR with the reason in plain words, or not connected; never the client secret), and every send so far: new app or new version, Intune app name and id, status (queued, sending, sent, failed) and the result. AppForShare only hands the file to Intune; assignment to groups stays in Intune. Sending is done by an Admin in the dashboard or with the CLI (appforshare store-upload <build> --to intune --yes), never from here. Read only. Team.

Input parameters:

- `build` (string, required): Build id or the slug of its install link

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73
- 2026-11-12: 72
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 71
- 2026-11-08: 71
- 2026-11-07: 55
- 2026-11-06: 70
- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 69

## Common questions

### What is the AppForShare MCP server?

AppForShare is an MCP server listed in the public MCP registry as io.appforshare/appforshare. Share iOS and Android test builds: upload, install links, testers, store readiness and releases. This page covers its npm package (appforshare-mcp).

### Is the AppForShare MCP server safe to use?

AppForShare scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 AppForShare MCP server expose?

AppForShare exposes 57 tools: upload_build, check_local_build, whoami, list_projects, list_builds, and 52 more. Their descriptions and schemas cost roughly 7,717 tokens of context every time the server is loaded.

### Is the AppForShare MCP server still maintained?

AppForShare is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the AppForShare MCP server under?

AppForShare declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the AppForShare MCP server?

VerifyMCP ran 16 checks on AppForShare, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/appforshare-mcp
- Socket report: https://socket.dev/npm/package/appforshare-mcp
- Repository: https://github.com/appforshare/appforshare-mcp
- Website: https://appforshare.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-appforshare-appforshare/appforshare-mcp
