Privacy-first security checker for web projects. Zero data uploaded, actionable fixes.
Bastion exposes 19 security check tools via MCP, but lacks critical definition infrastructure. No input schemas are visible in the source code, tools appear to be inferred from check implementations rather than explicitly registered with JSON Schema. Descriptions are present but generic (10-80 chars, well below the 50-200 char LLM-optimized baseline). No parameter documentation, no output schemas, no error handling guidance. The codebase shows check implementations (e.g., packages/cli/src/checks/gitignore.js) but no MCP tool registration layer with proper schemas. This is a domain-specific security scanner retrofitted as an MCP server without proper tool definition infrastructure.
Authentication method detection — checks if the project uses an established auth provider, custom auth implementation, or no auth at all
Insecure code pattern detection — scans for eval(), innerHTML assignment, SQL concatenation, document.write(), child_process.exec injection, Math.random() for security
Supply-chain check for compromised dependencies
Cookie security flags — inspects Set-Cookie headers for HttpOnly, Secure, and SameSite attributes
CORS configuration check — scans source files for permissive CORS configurations, detects wildcard origins, bare cors() calls, and dangerous credentials + wildcard combinations
Dependency vulnerabilities — wraps npm audit, maps to Bastion severity levels
DMARC DNS record — looks up _dmarc.{domain} TXT record to verify email authentication policy
No input schemas visible for any tool. Tools appear inferred from check implementations rather than explicitly registered with JSON Schema.
Descriptions are generic and under 50 characters for most tools (e.g., 'Check for .gitignore file presence'). LLM-optimized descriptions should be 50-200 chars and explain WHAT, WHEN, and WHY.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
Check for .env.example file presence
Check for .gitignore file presence and configuration
Check HTTP security headers
Supply-chain check for npm script configuration
Supply-chain check for npm ci usage
Check for rate limiting configuration
Scan for exposed secrets and credentials in source files
Check for security.txt file in project root
Check for security.txt at /.well-known/security.txt URL
Supply-chain check for self-hosted runner configuration
Server header information disclosure — flags when the Server header reveals specific software and version info
Check SSL/TLS certificate validity and configuration
No parameter documentation visible. Tools accept inputs (e.g., project path, domain) but no descriptions explain what each parameter controls, valid ranges, or formats.
No output schemas documented. LLMs cannot plan downstream calls or extract data without knowing what fields each tool returns.
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next (e.g., 'Domain not found. Try a different domain.').