Skip to main content
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.
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):
Runs the audit against the specified MCP server URL and prints a summary report with passed, failed, and skipped checks.

​
Extended Usage

Output the full report as JSON (useful for CI or further processing):
Skip confirmation prompts:

​
Options

​
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.