# Auditon Assessments MCP server

Source: https://glimind.com/server/mcp-registry%2Fco.auditon%2Fassessments
Registry id: `mcp-registry/co.auditon/assessments`
Status: live (checked 2026-10-26T22:08:20.742Z)

## Measurements (30 days)

- Uptime: 99.9%
- Checks: 2067
- Outages (90 days): 2

## Install

```json
{
  "mcpServers": {
    "auditon-assessments-mcp-server": {
      "type": "http",
      "url": "https://auditon.co/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http auditon-assessments-mcp-server https://auditon.co/mcp
```

## Tools (6)

- `compare_scans`: What changed on an endpoint between two scans: appeared, resolved, not reassessed (the check did not complete, so status is unknown) and severity changes. Witho
- `get_finding`: Full detail for one finding: description, impact, remediation, references, evidence, analyst decision and its history across scans.
- `get_report`: One scan as structured data: rating, coverage gaps, findings, items requiring verification, accepted risks, dismissed false positives and passed controls. Read 
- `list_endpoints`: Hosts assessed in this workspace, with open findings by severity and the most recent scan. Start here.
- `list_findings`: Current findings across all scans, most severe first. Defaults to open findings; potential (unconfirmed) matches are included and marked by assurance.
- `list_scans`: Scans, newest first: type, status, rating and coverage. With an endpoint, rating, findings and coverage are for that endpoint only.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.