AppCrane
NPM · APPCRANE-MCP · SCANNED SEP 25
Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
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 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13973 tokens (~245/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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "appcrane_deploy" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 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
How do I install the AppCrane MCP server?
AppCrane runs locally as an npm package, launched with npx -y appcrane-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 · appcrane-mcp
claude mcp add gitayg-appcrane -- npx -y appcrane-mcp
{
"mcpServers": {
"gitayg-appcrane": {
"command": "npx",
"args": [
"-y",
"appcrane-mcp"
]
}
}
} {
"servers": {
"gitayg-appcrane": {
"command": "npx",
"args": [
"-y",
"appcrane-mcp"
]
}
}
} codex mcp add gitayg-appcrane -- npx -y appcrane-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gitayg-appcrane": {
"type": "local",
"command": [
"npx",
"-y",
"appcrane-mcp"
],
"enabled": true
}
}
} openclaw mcp add gitayg-appcrane --command npx --arg -y --arg appcrane-mcp
mcp_servers:
gitayg-appcrane:
command: "npx"
args: ["-y", "appcrane-mcp"] {
"McpServers": {
"gitayg-appcrane": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"appcrane-mcp"
]
}
}
} assistant mcp add gitayg-appcrane -t stdio -c npx -a -y appcrane-mcp
{
"mcpServers": {
"gitayg-appcrane": {
"command": "npx",
"args": [
"-y",
"appcrane-mcp"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +4
- Stability: unverified → 0.23 ▲ functional
- 8 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Sept 26 51
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 25 Sept 2026 · Analysed npm/appcrane-mcp@1.0.0
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
appcrane_stage_assemble ~172
Join the parts pushed with appcrane_stage_chunk into one staged file and return its token. Hand that token to appcrane_deploy_artifact to deploy it — that pair is a complete, MCP-native deploy for an app with no repo, and it does not touch GitHub. Pass sha256 of the WHOLE original file to have the reassembled bytes verified before the token is issued; without it you are trusting that every part arrived intact.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | Name for the assembled file. For a deploy it must end in .zip, .tar.gz or .tgz. |
| session | string | yes | The session id used for the parts. |
| sha256 | string | – | Optional hex SHA-256 of the whole original file, verified before the token is issued. |
No output schema declared.
No examples provided.
appcrane_stage_chunk ~277
Upload one part of a SMALL file to AppCrane over MCP. For anything bigger than a few KB use appcrane_stage_from_url instead — the bytes here are emitted by the model, so they cost output tokens per character and fail on a single typo. Capped at 8 parts for that reason. Split the file into parts small enough for a tool call (~256KB of base64 each is comfortable), send each with the same `session` and `of`, then call appcrane_stage_assemble. Parts may be sent in any order and re-sent to replace a corrupted one; the reply lists which parts are still missing. Use encoding="base64" for anything binary. Pass sha256 of THIS part to have it verified on arrival.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | This part's bytes, encoded per `encoding`. |
| encoding | string | – | Defaults to utf-8. Use base64 for binary. |
| of | integer | yes | Total number of parts. Identical across every part of a session. |
| part | integer | yes | 1-based part number. |
| session | string | yes | Opaque id grouping the parts of one file. Any unique string; reuse it for every part. |
| sha256 | string | – | Optional hex SHA-256 of this part, verified on arrival. |
No output schema declared.
No examples provided.
appcrane_stage_from_url ~245
Stage a file by having AppCrane DOWNLOAD it, and return its token. THE CHEAPEST WAY to get a large artifact in: the bytes go host-to-host and never pass through your context, so a 600KB bundle costs the same handful of tokens as a 6KB one. Prefer this over appcrane_stage_chunk for anything bigger than a small text file. Give it a URL your build already produces — a GitHub release asset, an S3/R2 presigned URL, any https link the server can reach. Pass sha256 to have the downloaded bytes verified before a token is issued. Then deploy with appcrane_deploy_artifact. https only; redirects are not followed; private and link-local addresses are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Name to stage it under. For a deploy it must end in .zip, .tar.gz or .tgz. Defaults to the last path segment. |
| sha256 | string | – | Optional hex SHA-256 of the file, verified before the token is issued. |
| url | string | yes | Direct https URL to the file. Must not redirect — give the final URL. |
No output schema declared.
No examples provided.
appcrane_top_apps ~118
Top apps by distinct active users in a lookback window. Useful for "which apps are getting the most use this week" or "what should I deprecate" type questions. Sourced from app_visits which is recorded on every Caddy forward_auth (one row per user/app/day). Returns rows ordered by user count descending. Admin only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window. Default 7, max 90. |
| top | integer | – | How many rows. Default 10, max 50. |
No output schema declared.
No examples provided.
appcrane_top_users ~112
Top users by distinct apps opened in a lookback window. Surfaces who the heaviest cross-app users are — handy for finding power users to interview, or spotting churn risk (a user who used 10 apps last month and 0 this week). Sourced from app_visits. Active users only. Admin only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window. Default 7, max 90. |
| top | integer | – | How many rows. Default 10, max 50. |
No output schema declared.
No examples provided.
appcrane_update_app ~682
Patch fields on an existing app. Use this to fix a missing github_url after the fact, change branch, rotate the github_token, retag with category/visibility, point an image app at a new image_ref, or adjust resource limits — anything you would otherwise need direct DB access for. Only includes fields you pass; omitted fields are left alone. To clear a string field pass an empty string. Returns the same shape as appcrane_get_app.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_bypass_paths | array | – | v2.7.27: array of path prefixes (e.g. ["/ws/local-runner"]) that bypass SSO forward_auth on this app. Requests under these prefixes reach the container with NO X-AppCrane-* identity headers — the app… |
| branch | string | – | – |
| category | string | – | – |
| container_port | integer | – | Port the image listens on inside the container. Omit only if the image really listens on 3000 (what an AppCrane-built image does); a third-party image usually does not — odoo is 8069, nginx is 80. Ge… |
| description | string | – | – |
| domain | string | – | – |
| frame_ancestors | string | – | – |
| github_token | string | – | PAT for private clones. Stored encrypted (AES-256-GCM). Omit to leave the existing token alone; pass empty string to clear it; pass a value to rotate. |
| github_url | string | – | github.com URL of the source repo. Pass empty string to clear. |
| health_path | string | – | HTTP path AppCrane health-checks. Omit only if the image serves /api/health (the AppCrane-built default). A stock image will not, and a health check against a 404 marks a working app unhealthy. Pass… |
| image_ref | string | – | Prebuilt container image to run instead of building from source, e.g. "odoo:19" or "ghcr.io/owner/app@sha256:<64 hex>". Sets source_type='image'. The reference MUST name a version: a bare name ("odoo… |
| image_retention | integer | – | – |
| max_cpu_percent | number | – | Per-container CPU cap (0-100). |
| max_ram_mb | number | – | Per-container memory cap. |
| name | string | – | – |
| public_access | integer | – | – |
| slug | string | yes | App slug to update. |
| source_type | string | – | – |
| visibility | string | – | – |
No output schema declared.
No examples provided.
appcrane_wait_deploy ~140
Block until a deployment reaches a terminal state (live / failed / rolled_back), then return its final status. Use after appcrane_deploy instead of polling appcrane_get_logs in a loop. Returns immediately if the deployment is already terminal. Defaults to 180s timeout, hard-capped at 600s. On timeout, returns { status: "pending", timed_out: true } so the caller can decide whether to keep waiting.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_id | number | yes | Deployment id from appcrane_deploy |
| timeout_sec | number | – | How long to wait. Default 180s, max 600s. |
No output schema declared.
No examples provided.
What is the AppCrane MCP server?
AppCrane is an MCP server listed in the public MCP registry as io.github.gitayg/appcrane. Deploy and manage apps on your own AppCrane instance, the self-hosted PaaS for AI-built apps. This page covers its npm package (appcrane-mcp).
Is the AppCrane MCP server safe to use?
AppCrane scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 AppCrane MCP server expose?
AppCrane exposes 57 tools: appcrane_list_apps, appcrane_get_app, appcrane_top_apps, appcrane_top_users, appcrane_get_health, and 52 more. Their descriptions and schemas cost roughly 13,973 tokens of context every time the server is loaded.
Is the AppCrane MCP server still maintained?
AppCrane is still listed as active in the MCP registry. We last reached this channel on 25 September 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 AppCrane MCP server under?
AppCrane declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.