# Achromat Machine Operational Memory (npm · @achromat-ai/mcp-server)

Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool.

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `achromat.ai`: 65/100, [markdown](https://verifymcp.io/servers/ai-achromat-mcp-server/achromat.md), [page](https://verifymcp.io/servers/ai-achromat-mcp-server/achromat)
- npm · `@achromat-ai/mcp-server`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server.md), [page](https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@achromat-ai/mcp-server`
- Version: `0.1.4`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 205 tokens (~205/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Achromat Machine Operational Memory MCP server?

Achromat Machine Operational Memory runs locally as an npm package, launched with npx -y @achromat-ai/mcp-server. 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 ai-achromat-mcp-server -- npx -y @achromat-ai/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "ai-achromat-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@achromat-ai/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-achromat-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@achromat-ai/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ai-achromat-mcp-server -- npx -y @achromat-ai/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-achromat-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@achromat-ai/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-achromat-mcp-server --command npx --arg -y --arg @achromat-ai/mcp-server
```

### Hermes

```yaml
mcp_servers:
  ai-achromat-mcp-server:
    command: "npx"
    args: ["-y", "@achromat-ai/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "ai-achromat-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@achromat-ai/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-achromat-mcp-server -t stdio -c npx -a -y @achromat-ai/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "ai-achromat-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@achromat-ai/mcp-server"
      ]
    }
  }
}
```

## 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-05 (score 75, +1)

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

### 2026-11-04 (score 74, 0)

- [security regression] Stability: 0.50 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.3 → 0.1.4

### 2026-11-03 (score 74, +1)

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

### 2026-11-01 (score 73, +1)

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

### 2026-10-31 (score 72, +21)

- [security regression] Known CVEs: unverified → fail
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-10-30 (score 51, −20)

- [security regression] Known CVEs: fail → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-10-28 (score 71, +1)

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

### 2026-10-26 (score 70, +1)

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

## MCP tools (1)

### `achromat_register_identity` (~205 tokens)

Create and register an Achromat identity

Achromat needs a private key on this machine before it can answer anything, and none exists yet. This tool creates one: it generates an Ed25519 key pair, completes a short proof of work (about a second), registers the public key with Achromat Machine Operational Memory, and saves the private key to a file that only this user can read. ASK THE USER FIRST and wait for a yes, because it writes a private key file on their machine and creates an identity on the service. Explain that the key never leaves the machine, that only the public half is sent, and that the file cannot be recovered if lost. Then call this tool with user_confirmed set to true. Afterwards achromat_recall and achromat_calibrate become available.

Input parameters:

- `user_confirmed` (boolean, required): Set to true ONLY after the user has said yes to creating an identity. If they have not been asked, ask first and do not call this tool.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 51
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72

## Common questions

### What is the Achromat Machine Operational Memory MCP server?

Achromat Machine Operational Memory is an MCP server listed in the public MCP registry as ai.achromat/mcp-server. Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool. This page covers its npm package (@achromat-ai/mcp-server).

### Is the Achromat Machine Operational Memory MCP server safe to use?

Achromat Machine Operational Memory scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Achromat Machine Operational Memory MCP server expose?

Achromat Machine Operational Memory exposes 1 tool: achromat_register_identity. Their descriptions and schemas cost roughly 205 tokens of context every time the server is loaded.

### Is the Achromat Machine Operational Memory MCP server still maintained?

Achromat Machine Operational Memory 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.

### What licence is the Achromat Machine Operational Memory MCP server under?

Achromat Machine Operational Memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Achromat Machine Operational Memory MCP server?

VerifyMCP ran 16 checks on Achromat Machine Operational Memory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@achromat-ai/mcp-server
- Socket report: https://socket.dev/npm/package/@achromat-ai/mcp-server
- Repository: https://github.com/achromat-ai/achromat-mcp-server
- Website: https://achromat.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat-ai-mcp-server