Runs a Beacon audit against a remote MCP server and prints a summary of passed, failed, and skipped checks. Beacon verifies spec compliance, tool and resource metadata, and readiness for ChatGPT and Claude.ai.Documentation Index
Fetch the complete documentation index at: https://docs.alpic.ai/llms.txt
Use this file to discover all available pages before exploring further.
End-to-end widget rendering checks are skipped from the CLI because they take several minutes per platform. Run the
full audit — including live browser widget tests — from the Beacon tab in the Alpic dashboard.
Usage
Audit a server by URL (standalone mode, no project association):Extended Usage
Output the full report as JSON (useful for CI or further processing):Options
| Flag | Description | Default |
|---|---|---|
--url | The HTTPS URL of the MCP server to audit (standalone mode, no project association) | |
--json | Output the full report as JSON | false |
--team-id | Team ID (only with --url for standalone audits) | |
--project-id | Project ID to audit | |
--environment-id | Environment ID to audit (defaults to production) | |
--non-interactive | Skip all confirmation prompts | false |
Exit codes
alpic audit exits with code 1 when at least one error-severity check fails, and 0 otherwise. Warnings and skipped checks do not fail the command, so you can gate CI on blocking issues while still surfacing lower-severity findings in the output.
Authentication is required. Run
alpic login or set ALPIC_API_KEY before running an audit.If the current directory is linked to an Alpic project, the audit automatically associates with that project. Use
--non-interactive to skip the confirmation prompt.Beacon only supports unauthenticated MCP servers today. If the target returns
HTTP 401, Beacon reports that auth is
required and skips the remaining checks.