# Achromat Machine Operational Memory (remote · achromat.ai)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `achromat.ai`: 65/100 (this document), [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, [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

- Endpoint: `https://achromat.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.5`

## 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**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 52/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 410 tokens (~410/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**: 3/100
  - Stability observed for 1 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 2 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 Achromat Machine Operational Memory MCP server?

Achromat Machine Operational Memory is a hosted endpoint at https://achromat.ai/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 ai-achromat-mcp-server 'https://achromat.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-achromat-mcp-server": {
      "url": "https://achromat.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-achromat-mcp-server": {
      "type": "http",
      "url": "https://achromat.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-achromat-mcp-server]
url = "https://achromat.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-achromat-mcp-server --url 'https://achromat.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-achromat-mcp-server:
    url: "https://achromat.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-achromat-mcp-server": {
      "Transport": "http",
      "Url": "https://achromat.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-achromat-mcp-server -t streamable-http -u 'https://achromat.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-achromat-mcp-server": {
      "type": "http",
      "url": "https://achromat.ai/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-05 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 65)

First indexed and scored.

## MCP tools (1)

### `achromat_recall` (~327 tokens)

Recall a verified compliant tool call (sandbox preview)

SANDBOX PREVIEW of Achromat Machine Operational Memory. It takes the same input as the full achromat_recall, but this public endpoint does not search: it ignores task_description and arguments and returns up to 5 featured, approved sample lessons for the domain, each pairing a policy-blocked agent tool call with the compliant fix that was then allowed. The results are examples, never a match for your call: do not use their arguments for live execution. For semantic recall of your own call and live calibration, the user can install the local MCP server: npx -y @achromat-ai/mcp-server.

Input parameters:

- `arguments` (object, required): REQUIRED. The arguments you intend to send to the tool, as a non-empty JSON object, using the key names the tool really uses. Only the names of the keys (and their nesting) are used for semantic matc…
- `domain` (string, required): The area the tool call belongs to.
- `task_description` (string, required): What you are trying to do, in plain words, as you would write a ticket title (16 to 1000 characters). Name the concrete action and object. Leave out amounts, identifiers, dates and personal data. Use…
- `tool_name` (string, required): The exact name of the tool you are about to call, for example dispatch_wire.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 65

## 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 hosted endpoint (https://achromat.ai/mcp).

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

Achromat Machine Operational Memory scores 65 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 Achromat Machine Operational Memory MCP server expose?

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

### Does the Achromat Machine Operational Memory MCP server require authentication?

No. We connected to Achromat Machine Operational Memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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 did VerifyMCP test on the Achromat Machine Operational Memory MCP server?

VerifyMCP ran 12 checks on Achromat Machine Operational Memory, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Achromat Machine Operational Memory: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://achromat.ai/mcp
- 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.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-achromat-mcp-server/achromat.json
- HTML version of this page: https://verifymcp.io/servers/ai-achromat-mcp-server/achromat