shipcheck-mcp
shipcheck-mcp
Servidor MCP que permite a los agentes de codificación de IA ejecutar Shipcheck en repositorios locales de JavaScript y TypeScript.
Shipcheck escanea aplicaciones creadas por IA en busca de riesgos de lanzamiento, como variables de entorno que parecen privadas expuestas, webhooks de Stripe sin firmar, falta de evidencia de reglas de Supabase/Firebase, rutas de depuración, falta de medidas de seguridad en el uso de IA, falta de CI, dependencias sueltas y documentación de lanzamiento escasa.
Página de la herramienta: https://tatelyman.github.io/tate-web-services/shipcheck.html
Registro oficial de MCP: https://registry.modelcontextprotocol.io/v0/servers?search=shipcheck
Repositorio de demostración con alertas de escaneo de código de GitHub: https://github.com/TateLyman/shipcheck-demo-ai-app
Instalación
Ejecutar directamente con npx:
npx --yes shipcheck-mcpRelated MCP server: CodeInspectus
Configuración de MCP
Añade este servidor a un cliente MCP que admita servidores stdio:
{
"mcpServers": {
"shipcheck": {
"command": "npx",
"args": ["--yes", "--package", "shipcheck-mcp", "shipcheck-mcp"]
}
}
}Herramienta
scan_repository
{
"root": ".",
"format": "markdown",
"failOn": "medium",
"strict": true
}Formatos: text, markdown, json o sarif.
Gravedades: info, low, medium o high.
Shipcheck es un análisis estático defensivo, no una prueba de penetración. Ejecútalo solo en repositorios que poseas o que estés autorizado a inspeccionar.
Desarrollo
npm install
npm run checkAvailable Tools
1 toolscan_repositoryScan repository with ShipcheckB
Run Shipcheck on a local JavaScript or TypeScript repo the user owns or is authorized to inspect.
Inputs: root, format, failOn, strict.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no chance of confusion between tools. The single tool has a clear and distinct purpose.
With only one tool, there are no naming inconsistencies. The name 'scan_repository' follows a clear snake_case convention.
A single tool feels thin for most purposes, though for a very specialized server like 'shipcheck' it might be acceptable. It borders on too minimal.
The server only offers one operation (scanning), which may be insufficient for a full workflow. Missing potential tools like listing results or configuration, but the core task is covered.
Maintenance
Related MCP Connectors
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.
Lets coding agents check their own code for leaked secrets, risky dependencies and AI-code mistakes
Security scanner for AI agents: prompt injection, leaked secrets, PII, and SSRF-risk URL detection.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseAqualityBmaintenanceLocal-first, zero-egress security scanner for AI-generated / "vibe-coded" JS/TS. Bundles Opengrep, Gitleaks & Trivy behind one CWE-keyed schema and adds AI-code-specific checks (client-side secret exposure, Supabase RLS, prompt-injection & LLM-output XSS sinks). No account, no telemetry.10358 npm51Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to perform zero-execution, AST-based static analysis of JavaScript/TypeScript codebases, including symbol lookup, dependency tracing, change-impact analysis, dead-code detection, and risk assessment.8MIT