# AppLedger (pypi · appledger)

Plain-English security checks for AI-built apps (Trivy + Opengrep), with fix requests for agents

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- pypi · `appledger`: 81/100 (this document), [markdown](https://verifymcp.io/servers/net-appledger-appledger/appledger.md), [page](https://verifymcp.io/servers/net-appledger-appledger/appledger)

## Channel facts

- Registry: `pypi`
- Package: `appledger`
- Version: `0.2.5`
- 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-10-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to contentasoftware/appledger).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 881 tokens (~176/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (20% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 AppLedger MCP server?

AppLedger runs locally as a PyPI package, launched with uvx appledger. 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 net-appledger-appledger -- uvx appledger
```

### Cursor

```json
{
  "mcpServers": {
    "net-appledger-appledger": {
      "command": "uvx",
      "args": [
        "appledger"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-appledger-appledger": {
      "command": "uvx",
      "args": [
        "appledger"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add net-appledger-appledger -- uvx appledger
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-appledger-appledger": {
      "type": "local",
      "command": [
        "uvx",
        "appledger"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-appledger-appledger --command uvx --arg appledger
```

### Hermes

```yaml
mcp_servers:
  net-appledger-appledger:
    command: "uvx"
    args: ["appledger"]
```

### Netclaw

```json
{
  "McpServers": {
    "net-appledger-appledger": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "appledger"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-appledger-appledger -t stdio -c uvx -a appledger
```

### Other

```json
{
  "mcpServers": {
    "net-appledger-appledger": {
      "command": "uvx",
      "args": [
        "appledger"
      ]
    }
  }
}
```

## 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-10-21 (score 81, +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-10-19 (score 80, +1)

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

### 2026-10-17 (score 79, +1)

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

### 2026-10-15 (score 78, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 20

### 2026-10-14 (score 49, 0)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 20
- [functional] Package version: 0.2.2 → 0.2.5
- [functional] Package version: 0.2.2 → 0.2.4
- [functional] Package version: 0.2.2 → 0.2.3

### 2026-10-12 (score 49)

First indexed and scored.

## MCP tools (5)

### `check_app` (~341 tokens)

Scan an app folder with independent security scanners and explain the findings in plain language.

Hosted mode sends the project's files over HTTPS to the AppLedger scanning service, where they are
scanned with Trivy and Opengrep and deleted right after. Only files git would commit are sent; secrets
files (.env, keys, certificates, local settings), dependencies, media and files over 1 MB never are.
The first check of a folder returns needs_confirmation and an upload_preview instead of uploading:
show the preview to the user and ask. Only after they agree, call again with confirm_upload=true;
later checks of that folder don't ask again. Results are written to <path>/.appledger (report.html,
fix-prompt.md, findings.json). Returns the score (0-100), grade, who may use the app right now, and
every finding with why it matters and what to do. A hosted check from a computer that isn't connected
to a dashboard also returns save_link: a link (valid 24 hours, works once) that saves this result to a
free AppLedger ledger. Offer it to the user once, in one line.

Args:
    path: absolute path to the app's folder.
    app_name: a friendly name for the app, shown in the report.
    confirm_upload: true only after the user agreed to send this folder's files to appledger.net.
    save_to_dashboard: false to keep this check out of the user's AppLedger dashboard.

Input parameters:

- `app_name`
- `confirm_upload` (boolean)
- `path` (string, required)
- `save_to_dashboard` (boolean)

### `preview_upload` (~113 tokens)

List the files a hosted check of this folder would send to appledger.net, and what stays behind.

Nothing is sent. In a git repository only files git tracks or would commit count; elsewhere the
folder's .gitignore files decide. Secrets files, media, files over 1 MB, dependencies and build output
are always left out. Also lists secrets files git would commit, which the check reports as problems.

Args:
    path: absolute path to the app's folder.

Input parameters:

- `path` (string, required)

### `get_fix_prompt` (~90 tokens)

Return the fix request written by the last check_app run for this app folder.

The fix request lists every problem in order, where it is, and the expected fix, plus rules such
as never putting keys in code and never removing features to silence a warning.

Args:
    path: absolute path to the app's folder (the same path given to check_app).

Input parameters:

- `path` (string, required)

Output parameters:

- `result` (string)

### `connect_dashboard` (~95 tokens)

Save a connection key so future checks from this computer appear in the user's AppLedger dashboard.

The user creates the key (it starts with al_) at https://appledger.net/app/ under "Connect a computer".
The key is stored in ~/.appledger/key. Only call this with a key the user gave you.

Args:
    key: the connection key, starting with al_.

Input parameters:

- `key` (string, required)

### `scanner_status` (~42 tokens)

Show whether the AppLedger scanning service is reachable (or, in local mode, which scanners are
installed on this computer), and how to fix anything that is missing.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/net-appledger-appledger/appledger#diagnostics

## Score history

- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49

## Common questions

### What is the AppLedger MCP server?

AppLedger is an MCP server listed in the public MCP registry as net.appledger/appledger. Plain-English security checks for AI-built apps (Trivy + Opengrep), with fix requests for agents. This page covers its PyPI package (appledger).

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

AppLedger scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. 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 AppLedger MCP server expose?

AppLedger exposes 5 tools: check_app, preview_upload, get_fix_prompt, connect_dashboard, scanner_status. Their descriptions and schemas cost roughly 681 tokens of context every time the server is loaded.

### Is the AppLedger MCP server still maintained?

AppLedger is still listed as active in the MCP registry. We last reached this channel on 22 October 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 AppLedger MCP server under?

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

## Links

- PyPI project: https://pypi.org/project/appledger/
- Socket report: https://socket.dev/pypi/package/appledger
- Repository: https://github.com/contentasoftware/appledger
- Website: https://appledger.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-appledger-appledger/appledger.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-appledger-appledger/appledger.json
- HTML version of this page: https://verifymcp.io/servers/net-appledger-appledger/appledger