# `io.github.pablo-ramossanchez/arquestra-audit` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/io.github.pablo-ramossanchez/arquestra-audit
- JSON: https://anlyon.dev/api/v1/servers/io.github.pablo-ramossanchez/arquestra-audit
- Version: 0.8.1 (active)
- Publisher: io.github.pablo-ramossanchez (GitHub account)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/pablo-ramossanchez/arquestra-audit-mcp
- Metadata from the official MCP Registry, synced 2026-11-03T14:18:29.475Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Arquestra Audit
Audit a data file before publishing: one light per figure. Your data never reaches the server.
```

Scanned 2026-11-03T14:18:34.997Z over streamable-http.

**5 tools: 3 change things and 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 3 | ask |
| Only reads | read | 2 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged untrusted-input or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__arquestra-audit__prepare_script` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `start_audit` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "start_audit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "start_audit" says "start": a word for a change.
```

- **warn** Annotations that disagree with the tool in `measure_in_app` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "measure_in_app" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.
```


## Changes things (3)

Creates or changes something that can be changed back. Claude Code: ask.

### `example_audits`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

Description, as the server wrote it:

```untrusted-server-text
Published example audits, such as the AI Project Radar, and how the audit works. With no arguments: the overview and the list of examples. With a name: one example, result by result (level filters by light). With a name and an id: one result with every reason and what to change. They are not the person's data.
```

### `measure_in_app`

- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Opens the audit panel in the chat. Without a spec, the panel receives the person's file, reads it in their browser and returns a profile of it: per column its kind, empty cells, distinct values, the values of categories with their counts, the range of numbers and dates, and the first rows. With a confirmed spec, the panel measures that same file in the browser with measure.py and shows one light per result. The file is not sent to this server.
```

### `start_audit`

- The name "start_audit" says "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Proposes how to read a data file for an audit, from its column names (optionally a type and one example value each) and the results the person wants to publish. Returns a proposed spec (the role of each column, each result written as a claim), how claims are written, the catalog of checks and the points the person has to confirm. It receives no rows.
```

## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `prepare_script`

- The description's first verb is "return": a word for reading.
- Tag private-data: The description's first sentence says "return" and "file": it reads files.

Description, as the server wrote it:

```untrusted-server-text
Returns measure.py with a confirmed spec written in: a fixed Python script (standard library, no network, fixed seeds) that counts what each check needs from a data file and prints those counts with its own fingerprint and no rows. Reads .csv or .json. If the spec has errors, returns the errors instead.
```

### `show_audit`

- The name "show_audit" says "show": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Turns the output of measure.py into one light per result (red, amber or green, with its reasons), after checking that the output comes from the unchanged script and from the given spec. Shows the lights in the chat and returns them, with a link to the same view on arquestra.dev that carries only codes. Stores nothing.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `arquestra-audit`:

```json
{
  "permissions": {
    "allow": [
      "mcp__arquestra-audit__prepare_script",
      "mcp__arquestra-audit__show_audit"
    ],
    "ask": [
      "mcp__arquestra-audit__start_audit",
      "mcp__arquestra-audit__measure_in_app",
      "mcp__arquestra-audit__example_audits"
    ],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__arquestra-audit__prepare_script`: private-data