Realiza escaneos de seguridad en lenguaje natural sobre aplicaciones construidas con IA y genera solicitudes de corrección para agentes de programación.
También conocido como contentasoftware/appledger
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.2.5
- Último commit
- 14 oct 2026
- Licencia
- MIT
¿Qué es AppLedger MCP?
Realiza escaneos de seguridad en lenguaje natural sobre aplicaciones construidas con IA y genera solicitudes de corrección para agentes de programación.
Resumen generado a partir del README del proyecto
Acerca del MCP server de AppLedger
AppLedger proporciona feedback de seguridad para aplicaciones construidas con herramientas de IA como Claude Code, Cursor y Lovable. Escanea las carpetas de la aplicación utilizando herramientas independientes para identificar vulnerabilidades y traduce los hallazgos técnicos a un lenguaje sencillo. El servicio ayuda a los desarrolladores a entender qué está mal, por qué es importante y cómo solucionarlo. También genera un archivo fix-prompt.md específico que puede entregarse directamente a un agente de programación para resolver los problemas.
Los usuarios pueden elegir entre un modo alojado o un modo local. En el modo alojado, los archivos que Git incluiría en un commit se comprimen y se envían vía HTTPS a appledger.net para su escaneo, mientras que los archivos sensibles como .env o llaves SSH se excluyen estrictamente. El modo local mantiene todo el código en tu máquina utilizando versiones instaladas de Trivy y Opengrep. El sistema utiliza Trivy para encontrar llaves filtradas y librerías desactualizadas, mientras que Opengrep detecta patrones peligrosos como la inyección SQL. Para quienes ya cuentan con un servidor SonarQube, el modo local puede incluir opcionalmente esos escaneos para verificar la calidad del código y los puntos críticos de seguridad.
Qué puedes hacer con él
- 1Generar solicitudes de corrección para IACrea un archivo markdown que contenga un conjunto de instrucciones listo para entregar a un agente de programación para reparar fallos de seguridad.
- 2Auditar código generado por IA en busca de vulnerabilidadesEscanea la carpeta de tu aplicación para encontrar contraseñas filtradas, librerías desactualizadas o patrones peligrosos como la inyección SQL.
- 3Automatizar inspecciones de seguridad periódicasConfigura escaneos automatizados diarios o semanales utilizando programadores del sistema como cron o Windows Task Scheduler.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar AppLedger MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar AppLedger MCP en Claude Code
$ claude mcp add --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger -- uvx appledgerInstalar AppLedger MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Instalar AppLedger MCP en VS Code
.vscode/mcp.json
{
"servers": {
"appledger": {
"type": "stdio",
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Instalar AppLedger MCP en VS Code CLI
$ code --add-mcp '{"name":"appledger","type":"stdio","command":"uvx","args":["appledger"],"env":{"APPLEDGER_KEY":"<YOUR_APPLEDGER_KEY>"}}'Instalar AppLedger MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Instalar AppLedger MCP en Codex
$ codex mcp add appledger --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' -- uvx appledgerInstalar AppLedger MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.appledger] command = "uvx" args = ["appledger"] [mcp_servers.appledger.env] APPLEDGER_KEY = "<YOUR_APPLEDGER_KEY>"
Instalar AppLedger MCP en Gemini CLI
$ gemini mcp add -s user -e 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger uvx -- appledgerInstalar AppLedger MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Configuración
APPLEDGER_KEYSecretoOptional dashboard connection key (al_...). Without it, nothing goes to a dashboard; a hosted check returns a link that saves its result to a free account (the summary is kept up to 24 hours).
APPLEDGER_MODEhosted (default): files Git would commit are sent to appledger.net, scanned and deleted. local: Trivy and Opengrep run on this machine.
| Nombre | Descripción | Tipo |
|---|---|---|
| APPLEDGER_KEY | Optional dashboard connection key (al_...). Without it, nothing goes to a dashboard; a hosted check returns a link that saves its result to a free account (the summary is kept up to 24 hours). | Secreto |
| APPLEDGER_MODE | hosted (default): files Git would commit are sent to appledger.net, scanned and deleted. local: Trivy and Opengrep run on this machine. |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblecontentasoftware/appledger is public and reachablegithub.com/contentasoftware/appledger ↗Aprobado
- El paquete indica este repositorio como su origenappledger names contentasoftware/appledger as sourcepypi.org/project/appledger/ ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)Sigstore attestation for appledgerpypi.org/project/appledger/ ↗Aprobado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-14github.com/contentasoftware/appledger ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from appledgerAprobado
- No hay avisos críticos en el paquete ni en sus dependencias32 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubAppLedger honest check
Honest security feedback, in plain language, for apps people build with AI tools such as Claude Code, Codex, Cursor and Lovable.
AppLedger checks your app folder with independent scanners and explains what they find in everyday words: what is wrong, why it matters, and what to do. It also writes a fix request you can hand straight to the AI tool that built the app, then checks again.
What it checks
| Scanner | Finds |
|---|---|
| Trivy | Leaked passwords and keys, outdated libraries with known security problems, risky container setup |
| Opengrep | Dangerous code patterns: SQL injection, command injection, unsafe data loading, debug mode left on |
| SonarQube (optional, local mode) | Code quality and more security hotspots, if you already run a SonarQube server |
Each run produces, in <your-app>/.appledger/:
report.html: a score, who may use the app right now (only you, your team, the whole company), and every problem in plain wordsfix-prompt.md: a ready-made fix request for your coding agentfindings.json: the same findings for tools and dashboards
Two ways to run
| Mode | What you install | Where your code goes |
|---|---|---|
| Hosted (default) | Only this package | Source files Git would commit are zipped, sent over HTTPS to appledger.net, scanned and deleted right after. Secret files are never sent. You confirm before the first upload of each folder |
Local (--local or APPLEDGER_MODE=local) |
Also Trivy, Opengrep and the Opengrep rules | Stays on your computer. With a connection key, only a summary goes to your dashboard (see below); --no-dashboard skips even that |
What gets uploaded in hosted mode
- Sent: files Git would commit (
git ls-files, including new files that aren't ignored). Outside a Git repository,.gitignoreis still honoured. - Never sent:
.envand.env.*(except.env.example,.env.sample,.env.template),*.pem,*.key,*.p12,*.pfx, SSH keys,.npmrc,.pypirc,.netrc,*credentials*.json,service-account*.json,secrets.*, the folderscert,certs,secrets,.sshand.aws,.claude/settings.local.json, Terraform state, password files, Ansible Vault files, Kubernetes/Helm secret manifests, certificates and similar (full list insrc/appledger/uploadpolicy.py). The server drops such files again as a second safety net. - Skipped: dependencies, build output, media, documents and data files (CSV, spreadsheets, slides, SQL, logs, data dumps) and files over 1 MB.
If a secret file is committed to Git or not ignored, the check reports it as a problem by file name. Its content is never read or sent.
See exactly what would be sent, and what is left out and why, without uploading anything:
python -m appledger path/to/your-app --list-files
The first hosted check of a folder asks you to confirm. In scripts and scheduled runs, pass --yes. If the code belongs to your employer or a client, make sure you're allowed to upload it, or use local mode.
Install
Claude Code plugin (recommended: adds the guided check-my-app skill):
claude plugin marketplace add contentasoftware/appledger
claude plugin install appledger@appledger
In the Claude Code desktop app, add the marketplace contentasoftware/appledger in the plugin settings instead. Start a new session, then ask: "Is my app safe to share?" or "Add this app to AppLedger".
MCP server only (needs uv):
claude mcp add appledger -- uvx --from appledger appledger-mcp
Command line:
pip install appledger
python -m appledger path/to/your-app
Step-by-step guide with troubleshooting: https://appledger.net/docs/
Version 0.2.0 (upload preview, consent, secret-file exclusion, scheduling) is being released to PyPI; until then pip install appledger gets 0.1.x.
Company dashboard
Create a free account at appledger.net to keep every app your people check in one ledger: owner, grade, score trend, who may use it and which AI tool built it. Create a connection key under "Connect a computer", then save it on each computer:
python -m appledger --connect al_your_key
Or tell Claude: "Connect AppLedger with this key: al_…". The key is saved in ~/.appledger/key; APPLEDGER_KEY overrides it and --disconnect removes it.
From then on each check also saves a summary to your dashboard: the app's name, score, grade, problem counts, the list of problems found (level and short title, up to 60; never code or file paths), and the scanners used. Never the code.
Not connected yet? From 0.2.3, a hosted check from a computer without a key ends with a save link, also shown in report.html:
Save this result to a free AppLedger ledger (link works for 24 hours): https://appledger.net/app/claim.php?t=...
Open it, create a free account or log in, and the check is in your ledger; the page then offers a key for that computer. Until the link is used, the service keeps only the check's summary (app name, score, the problems' levels and titles; never code), for up to 24 hours. A link works once; --no-dashboard turns it off.
You can also add an app in the web app with Add app: register it without code, or upload a zip to check it in the browser (the zip is scanned and deleted the same way).
Scheduled checks
python -m appledger path/to/your-app --schedule weekly --yes # or daily
python -m appledger --schedules # list
python -m appledger path/to/your-app --schedule off # stop
Uses Windows Task Scheduler on Windows and cron on macOS and Linux. Hosted scheduled checks need the one-time --yes consent; add --local to schedule local checks instead. --quiet prints one line per check.
Local mode setup
- Trivy:
winget install AquaSecurity.Trivy(Windows) orbrew install trivy(Mac) - Opengrep: download from the releases page and put it on your PATH
- Rules:
git clone --depth 1 https://github.com/opengrep/opengrep-rules.git ~/.appledger/opengrep-rules - Check:
python -m appledger --doctor
Repository layout
| Path | What |
|---|---|
src/appledger/scanner.py |
Scanners, plain-language translation, report and fix request |
src/appledger/client.py |
Picks the files to send (honouring .gitignore) and sends them to the hosted service |
src/appledger/uploadpolicy.py |
The full list of secret files that are never uploaded, used by client and server |
src/appledger/service.py |
Server side: unpacks an upload safely and scans it |
src/appledger/server.py |
Local MCP server used by the plugin |
plugin/ |
Claude Code / Codex plugin with the check-my-app skill |
tests/mcp_smoke.py |
Calls every MCP tool like an agent would |
License
MIT. The Opengrep community rules used by the scanner have their own license (Commons Clause); check it before using them in a paid service.
Preguntas sobre AppLedger MCP
¿Cómo agrego AppLedger MCP a Claude Code?
Ejecuta claude mcp add --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger -- uvx appledger en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego AppLedger MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo puedo usar los hallazgos para corregir mi código?
La herramienta genera un archivo 'fix-prompt.md', que es una solicitud de corrección lista para usar que puedes entregar directamente a tu agente de programación con IA.