> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staging.alpic.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# audit

> Run a Beacon audit on an MCP server

Runs a [Beacon](/testing/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.

<Note>
  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.
</Note>

## Usage

Audit a server by URL (standalone mode, no project association):

```bash theme={null}
alpic audit --url https://my-server.example.com/mcp
```

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):

```bash theme={null}
alpic audit --url https://my-server.example.com/mcp --json
```

Skip confirmation prompts:

```bash theme={null}
alpic audit --url https://my-server.example.com/mcp --non-interactive
```

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

<Note>Authentication is required. Run `alpic login` or set `ALPIC_API_KEY` before running an audit.</Note>

<Note>
  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.
</Note>

<Note>
  Beacon only supports unauthenticated MCP servers today. If the target returns `HTTP 401`, Beacon reports that auth is
  required and skips the remaining checks.
</Note>