# Auditon security assessments (remote · auditon.co)

Read-only access to your Auditon vulnerability scans: findings, endpoints, reports and changes.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `auditon.co`: 83/100 (this document), [markdown](https://verifymcp.io/servers/co-auditon-assessments/auditon.md), [page](https://verifymcp.io/servers/co-auditon-assessments/auditon)

## Channel facts

- Endpoint: `https://auditon.co/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 541 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Auditon security assessments MCP server?

Auditon security assessments is a hosted endpoint at https://auditon.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http co-auditon-assessments 'https://auditon.co/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.co-auditon-assessments]
url = "https://auditon.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-auditon-assessments": {
      "type": "remote",
      "url": "https://auditon.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-auditon-assessments --url 'https://auditon.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-auditon-assessments:
    url: "https://auditon.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-auditon-assessments": {
      "Transport": "http",
      "Url": "https://auditon.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-auditon-assessments -t streamable-http -u 'https://auditon.co/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `list_endpoints` (~29 tokens)

List endpoints

Hosts assessed in this workspace, with open findings by severity and the most recent scan. Start here.

### `list_scans` (~63 tokens)

List scans

Scans, newest first: type, status, rating and coverage. With an endpoint, rating, findings and coverage are for that endpoint only.

Input parameters:

- `endpoint` (string): Endpoint hostname or IP, as returned by list_endpoints
- `limit` (integer)

### `get_report` (~106 tokens)

Get scan report

One scan as structured data: rating, coverage gaps, findings, items requiring verification, accepted risks, dismissed false positives and passed controls. Read "interpretation" before drawing conclusions. Set detail=true for descriptions and remediation.

Input parameters:

- `detail` (boolean): Include description, impact, remediation, references and evidence for each finding
- `endpoint` (string): Limit the report to one endpoint
- `scan_id` (string, required): scan_id (or source_id) as returned by list_scans

### `list_findings` (~102 tokens)

List findings

Current findings across all scans, most severe first. Defaults to open findings; potential (unconfirmed) matches are included and marked by assurance.

Input parameters:

- `endpoint` (string): Endpoint hostname or IP, as returned by list_endpoints
- `limit` (integer)
- `min_severity` (string): Lowest severity to include
- `since` (string): Only findings last observed on or after this date (YYYY-MM-DD)
- `state` (string)

### `get_finding` (~50 tokens)

Get finding

Full detail for one finding: description, impact, remediation, references, evidence, analyst decision and its history across scans.

Input parameters:

- `finding_id` (string, required): finding_id from list_findings or get_report

### `compare_scans` (~92 tokens)

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. Without scan ids, compares the endpoint's two most recent scans.

Input parameters:

- `endpoint` (string, required): Endpoint hostname or IP, as returned by list_endpoints
- `from_scan` (string): Earlier scan
- `to_scan` (string): Later scan

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-auditon-assessments/auditon#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75

## Common questions

### What is the Auditon security assessments MCP server?

Auditon security assessments is an MCP server listed in the public MCP registry as co.auditon/assessments. Read-only access to your Auditon vulnerability scans: findings, endpoints, reports and changes. This page covers its hosted endpoint (https://auditon.co/mcp).

### Is the Auditon security assessments MCP server safe to use?

Auditon security assessments scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Auditon security assessments MCP server expose?

Auditon security assessments exposes 6 tools: list_endpoints, list_scans, get_report, list_findings, get_finding, compare_scans. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.

### Does the Auditon security assessments MCP server require authentication?

Yes. Auditon security assessments asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Auditon security assessments MCP server still maintained?

Auditon security assessments is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://auditon.co/mcp
- Authorisation metadata: https://auditon.co/.well-known/oauth-protected-resource/mcp
- Website: https://auditon.co/mcp-security-scan-results.html
- Changelog RSS feed: https://verifymcp.io/servers/co-auditon-assessments/auditon.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-auditon-assessments/auditon.json
- HTML version of this page: https://verifymcp.io/servers/co-auditon-assessments/auditon