Achromat Machine Operational Memory
REMOTE · ACHROMAT.AI · 2 COMPONENTS
Recall and calibrate policy-compliant tool-call arguments before execution. Does not run the tool.
Available components
Last scanned (6 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Memory and Knowledge
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://achromat.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=achromat.ai | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 9dc508b4af8b7aae138cae69be90e288 |
| SANs: achromat.ai, *.achromat.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of achromat.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| achromat.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; script-src 'self'; style-src 'self'; img-src 'self' data:; font-src 'self'; connect-src 'self'; manifest-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://achromat.ai/mcp | Verified | 200 | |
| http (plaintext) | http://achromat.ai/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
achromat_recall Recall a verified compliant tool call (sandbox preview) ~327
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | 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 | yes | The area the tool call belongs to. |
| task_description | string | yes | 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 | yes | The exact name of the tool you are about to call, for example dispatch_wire. |
No output schema declared.
No examples provided.
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.
remote · achromat.ai
claude mcp add --transport http ai-achromat-mcp-server 'https://achromat.ai/mcp'
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.