Appo MCP Server

@appolabs/appo-mcp npm v2.3.0 Source verified

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

Local MCP server for the Appo app platform: create, publish and manage native iOS/Android apps from your AI assistant.

Trust grade
A
100/100
Last scanned get badge →
Trust
A · 100/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
Minimal
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 = 100/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 − 0 = 100. 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:

✓ No adoption-risk deductions — minimal blast radius, verified enough, and fully inspected.

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 34

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

  • Best Practicesno sensitive capability
  • check_permissionsno sensitive capability
  • configure_appno sensitive capability
  • create_appno sensitive capability
  • debug_assistantno sensitive capability
  • diagnose_issueno sensitive capability
  • featureno sensitive capability
  • frameworkno sensitive capability
  • generate_componentno sensitive capability
  • generate_hookno sensitive capability
Show 24 more tools ↓
  • generate_universal_linksno sensitive capability
  • get_app_overviewno sensitive capability
  • get_build_statusno sensitive capability
  • get_fix_recipeno sensitive capability
  • get_rejectionno sensitive capability
  • integrate_featureno sensitive capability
  • issueno sensitive capability
  • list_appsno sensitive capability
  • logsno sensitive capability
  • preview_appno sensitive capability
  • projectTypeno sensitive capability
  • publish_appno sensitive capability
  • requirementsno sensitive capability
  • scaffold_featureno sensitive capability
  • SDK Overviewno sensitive capability
  • send_pushno sensitive capability
  • set_iconno sensitive capability
  • set_permissionsno sensitive capability
  • setup_wizardno sensitive capability
  • trigger_resubmissionno sensitive capability
  • Troubleshootingno sensitive capability
  • Universal Linksno sensitive capability
  • unpublish_appno sensitive capability
  • validate_setupno sensitive capability

What this scan could not see

Versions 5

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
v2.3.0 latest A 100/100 0 1.13.0 2026-09-07
v2.2.1 A 100/100 0 1.12.1 2026-08-22
v2.2.0 A 100/100 0 1.12.1 2026-08-16
v2.1.2 A 100/100 0 1.12.1 2026-08-15
v2.0.1 A 99/100 0 1.12.1 2026-08-14

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 · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/appolabs-appo-mcp/badge.svg)](https://mcptrustchecker.com/registry/appolabs-appo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/appolabs-appo-mcp"><img src="https://mcptrustchecker.com/registry/appolabs-appo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/appolabs-appo-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 @appolabs/appo-mcp --online

Use the free API → How scoring works

More in Developer Tools