AppForShare
NPM · APPFORSHARE-MCP · 2 COMPONENTS
Share iOS and Android test builds: upload, install links, testers, store readiness and releases.
Available components
Last scanned (12 hours ago)
Scores higher than 53% of npm servers
Category CI/CD and DevOps
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% 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
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 58 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 17 Nov 26 +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.
- 15 Nov 26 +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.
- 13 Nov 26 +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.
- 12 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Nov 26 0
- Schema quality: 6808 → 7800 ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Package version: 1.0.10 → 1.0.11 functional
- 10 Nov 26 +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.
- 9 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Schema quality: 5261 → 6808 ▼ functional
- Capabilities: pass → unverified ▼ functional
- 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 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 21 Nov 2026 · Analysed npm/appforshare-mcp@1.0.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
store_upload_status Store sends of a build (TestFlight, Google Play) ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| build | string | yes | Build id or the slug of its install link |
No output schema declared.
No examples provided.
task_from_feedback Make a task from tester feedback ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | – |
| id | integer | yes | Feedback id from list_feedback |
No output schema declared.
No examples provided.
test_plan Test plan for a build ~141
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".
| Name | Type | Req | Description |
|---|---|---|---|
| build | string | yes | Build id or the slug of its install link |
| focus | string | – | Optional area to focus on, with generate |
| generate | boolean | – | – |
No output schema declared.
No examples provided.
tick_release_step Tick a release checklist step ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| build | string | yes | Build id or the slug of its install link |
| confirm | boolean | yes | – |
| done | boolean | – | – |
| key | string | yes | Step key from release_checklist |
No output schema declared.
No examples provided.
upload_build Upload a build ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Path to the build file (.ipa, .apk, .aab, or a desktop build on Pro and Team) |
No output schema declared.
No examples provided.
upload_from_url Upload a build from a URL ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Put the build into this channel (such as beta) when it is ready |
| notes | string | – | Release notes shown to testers |
| url | string | yes | https URL of the build file (.ipa, .apk, .aab or a desktop build) |
No output schema declared.
No examples provided.
whoami Who am I ~45
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · appforshare-mcp
claude mcp add io-appforshare-appforshare -- npx -y appforshare-mcp
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.