coldpass

achromat-ai/achromat-mcp-server

GitHub ↗ · How this check works

Per-setup public labels: Linux / Luna: Works

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/achromat-ai--achromat-mcp-server.svg).

mcp-server

Works

The recorded run passed on 1 setup.

Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.

Tested on Linux
PlatformHaikuLuna
Linuxyes

Linux / Luna: yes · Oct 27, 2026 · f1c086e89c38 · codex / codex-cli 0.164.0
Recorded operation: node <guest-path> · local stdio MCP start + initialize + tools/list

Does what it says
1 of 1 claims checked out
  • Recall reports when no verified compliant call is known.: Real input produced the expected result: NO MATCH: no verified compliant version of this call is known

    Source: On a match you get `compliant_arguments`, a `steering_directive` and the rule that applied.

    Input: {"tool": "achromat_recall", "arguments": {"domain": "devsecops", "tool_name": "deploy_service", "task_description": "Deploy a service using the approved release workflow", "arguments": {"environment": "staging"}}}

    Expected: NO MATCH response advises calibration.

    Command: node <guest-path> tools/call {"tool": "achromat_recall", "arguments": {"domain": "devsecops", "tool_name": "deploy_service", "task_description": "Deploy a service using the approved release workflow", "arguments": {"environment": "staging"}}}

    Observed: NO MATCH: no verified compliant version of this call is known.\nNext step: call achromat_calibrate with the arguments you intend to use. If it answers BLOCK, follow its steering directive."}], "isError": false}

MCP
Yes, observed
Local or hosted
local
Local: runs on your machine
Needs keys or browser
None seen
Maintained
Maintained
actively maintained: last commit 5 days ago; 8 commits and 0 merged PRs in 90 days; 1 open issues, 0 open PRs; no releases

Last commit Oct 22, 2026

Setup time
2 min 9 s
2 min 9 s to a working result
Issue
none found in recorded check
Examples
1 of 1 ran as expected
  • Build and run from source using documented commands.: command completed successfully

    Source: README.md / Run from source; README.md / Development

    Input: npm install; npm run build; npm start

    Expected: The built server starts and waits on stdio.

    Command: npm run build

    Observed: > @achromat-ai/[email protected] build > tsc && node -e "require('node:fs').chmodSync('dist/index.js', 0o755)"

Evidence
README behavior checked
Agent interfaces
MCP
MCP

Observed interfaces were exercised by the checker. Documentation alone does not confirm compatibility.

MCP context
2 tools · about 1,098 tokens
2 tools · about 1,098 tokens

Largest returned tools/list page in these observations. Compact UTF-8 definition bytes ÷ 4, rounded up; approximate, excluding client framing and tool results. This is context size, not proof that every tool works.

Measured on linux with Luna · Oct 27, 2026 on f1c086e89c38

Tested with
Codex / Luna
  • Linux: Codex / Luna · agent codex-cli 0.164.0 · Checked operation passed · Oct 27, 2026 on f1c086e89c38

Each entry describes its recorded operation and source revision.

Safety
Made outbound HTTPS connections: yes (hosts not recorded) by <guest-path>

Review signals across current setups: connection review. 16 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict.

Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 104.21.0.247:443 8 attributed processes.

OSV reports a known vulnerability in this dependency version. 4 distinct locations. 8 findings.

Reviewed as expected for a test run: attempted writes that failed, so nothing was written.

Reviewed as expected for a test run: attempted writes that failed, so nothing was written; resolver address lookups that send no data.

Full event, path and process lists for each observed setup:

Repair history and test corrections
Current diagnosis: prerequisite · pending

No Achromat identity key exists on this machine. The server offers only achromat_register_identity, and it refuses to run without user_confirmed=true, which needs the user's consent.

Repair record fix-aad8fa0d185d07c48dab · current status JSON. Original run outcomes remain unchanged.

Failed run: achromat-ai/achromat-mcp-server · Oct 27, 2026 · Not tested.

Run details
Earlier attempts (1)

Luna

Native agent · Checked operation passed

Checked operation node <guest-path> · local stdio MCP start + initialize + tools/list

Agent-reported scope: Built the documented Node MCP server, registered a guest-local identity during manual exercise, then called achromat_recall and replayed the no-match response.

MCP server returned: achromat-mcp-server · version 0.1.2.

MCP tools returned: achromat_recall, achromat_calibrate. Tool listing does not establish authenticated tool-call success.

Run details
run
achromat-ai--achromat-mcp-server-gpt-6-luna-1793104610923093453
date
Oct 27, 2026
time to working
128.9s
product hosting / execution
Local stdio MCP server in the guest
recorded operation scope
product operation
model
gpt-6-luna
agent / version
codex / codex-cli 0.164.0
platform
linux
reported cost
not reported (not assumed free)
Recorded source
https://github.com/achromat-ai/achromat-mcp-server
Backend
hyperv
Tool transport
mcp-assigned-vm
Requested source pin (not an observed revision)
{"commit": "f1c086e89c388ce920908af9a21abd76c0950f5d", "url": "https://github.com/achromat-ai/achromat-mcp-server"}
Test version
readme-38e6b13f3b13804effb95797e3466b1a1334da7a232d897cbc8965867f802605
revision
f1c086e89c388ce920908af9a21abd76c0950f5d
Whose fault: not assigned · resolved

Safety: Review signals: 1 connection review, 8 known vulnerability.

Review signals: 1 connection review, 8 known vulnerability.

Reviewed as expected for a test run: attempted writes that failed, so nothing was written; resolver address lookups that send no data.

Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 104.21.0.247:443 8 attributed processes.

OSV reports a known vulnerability in this dependency version. 4 distinct locations. 8 findings.

OSV scanned supported lockfiles; unpinned dependencies and unsupported formats are outside this check.

A short run cannot establish that code is safe.

Connections show IP addresses; proxies can hide the final hostname.

Tracing covers dispatched commands and their children, not the whole OS; guest root can interfere with tracing.

Full safety evidence →

Answers recorded for this run
  • Recall reports when no verified compliant call is known.: Real input produced the expected result: NO MATCH: no verified compliant version of this call is known

    Source: On a match you get `compliant_arguments`, a `steering_directive` and the rule that applied.

    Input: {"tool": "achromat_recall", "arguments": {"domain": "devsecops", "tool_name": "deploy_service", "task_description": "Deploy a service using the approved release workflow", "arguments": {"environment": "staging"}}}

    Expected: NO MATCH response advises calibration.

    Command: node <guest-path> tools/call {"tool": "achromat_recall", "arguments": {"domain": "devsecops", "tool_name": "deploy_service", "task_description": "Deploy a service using the approved release workflow", "arguments": {"environment": "staging"}}}

    Observed: NO MATCH: no verified compliant version of this call is known.\nNext step: call achromat_calibrate with the arguments you intend to use. If it answers BLOCK, follow its steering directive."}], "isError": false}

Examples

  • Build and run from source using documented commands.: command completed successfully

    Source: README.md / Run from source; README.md / Development

    Input: npm install; npm run build; npm start

    Expected: The built server starts and waits on stdio.

    Command: npm run build

    Observed: > @achromat-ai/[email protected] build > tsc && node -e "require('node:fs').chmodSync('dist/index.js', 0o755)"

Local or hosted: local

What the agent did

Built the documented Node MCP server, registered a guest-local identity during manual exercise, then called achromat_recall and replayed the no-match response.

pwd && id -u && rg --files -g 'README*' -g 'pyproject.toml' -g 'package.json' -g 'requirements*.txt' -g 'Dockerfile*' -g 'Makefile' -g '.github/workflows/**' | head -80 && git status --short && git rev-parse --is-inside-work-tree && python3 --version && sed -n '1,240p' README.md
ls -la && find . -maxdepth 3 -iname 'README*' -o -name 'pyproject.toml' -o -name 'package.json' -o -name 'requirements*.txt' | head -80 && python3 --version
sed -n '1,240p' README.md && cat package.json && ls src && for f in src/*; do echo "--- $f"; sed -n '1,180p' "$f"; done
node --version; npm --version; ls -la .coldpass; git init && git remote add origin https://github.com/achromat-ai/achromat-mcp-server && git fetch --depth 1 origin f1c086e89c388ce920908af9a21abd76c0950f5d && git reset --mixed FETCH_HEAD
npm install
npm run build && npm run typecheck && npm test
sed -n '1,220p' src/index.ts && cat server.json
mkdir -p .coldpass && cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":false},"expected_text":"User confirmation is required"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"The server offers identity registration when there is no key file.","source":"The first time you use the server it has no key, so it offers a single tool, `achromat_register_identity`, and your agent will **ask you** whether to set up an identity.","input":"No configured key file exists.","expected":"The registration tool is offered and requires explicit confirmation.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":false},"expected_text":"User confirmation is required"}]
EOF
cat > .coldpass/examples.json <<'EOF'
[{"kind":"example","claim":"Build and run the source server over stdio.","source":"README.md / Run from source; README.md / Development","input":"npm install; npm run build; npm start","expected":"Server waits for an MCP host on stdio.","argv":["npm","run","build"],"cwd":"<guest-path>","expected_text":"mark dist/index.js executable"}]
EOF
cat > .coldpass/cycles.json <<'EOF'
{"detected":false,"reason":"Inspected README tools and package entry points: the server waits for host requests over MCP stdio and has no product scheduler, webhook, or cycle trigger."}
EOF
python3 -I <guest-path> --validate --replay
sed -n '1,220p' src/format.ts; sed -n '180,330p' src/tools.ts
cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":true},"expected_text":"User confirmation is required"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"The registration operation requires user agreement before identity setup.","source":"It requires `user_confirmed: true`, which the agent may set only after you have agreed; the tool description tells it to ask first.","input":"An agent has not received agreement.","expected":"The registration is not performed without explicit user confirmation.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":true},"expected_text":"Please confirm with the user"}]
EOF
cat > .coldpass/examples.json <<'EOF'
[{"kind":"example","claim":"Build the server from source as documented.","source":"README.md / Run from source","input":"npm install; npm run build","expected":"dist/index.js is compiled and executable.","argv":["npm","run","build"],"cwd":"<guest-path>","expected_text":"tsc && node -e"}]
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
rm -f .coldpass/no-key.pem && cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{},"expected_text":"only achromat_register_identity is offered"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"The server offers the registration tool when no key file exists.","source":"The first time you use the server it has no key, so it offers a single tool, `achromat_register_identity`, and your agent will **ask you** whether to set up an identity.","input":"Start the stdio server with a missing key path.","expected":"Only the registration tool is listed.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{},"expected_text":"only achromat_register_identity is offered"}]
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"A key file exists"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"A missing key is explained when a signed tool is called.","source":"The key itself is read on the first tool call, so a wrong key never makes the server disappear from your host: the tool call returns a message saying what to fix.","input":"Call recall without a configured key file.","expected":"The tool returns an actionable missing key message.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"A key file exists"}]
EOF
cat > .coldpass/examples.json <<'EOF'
[{"kind":"example","claim":"Build and run from source using documented commands.","source":"README.md / Run from source; README.md / Development","input":"npm install; npm run build; npm start","expected":"The built server starts and waits on stdio.","argv":["npm","run","build"],"cwd":"<guest-path>","expected_text":"node -e"}]
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":true},"expected_text":"REGISTERED. A new identity was created"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"Identity registration creates a local Ed25519 key and registers it with MOM.","source":"generates an Ed25519 key pair on your machine,","input":"Explicitly confirmed identity registration.","expected":"Registration response confirms identity creation and saves the key.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_register_identity","arguments":{"user_confirmed":true},"expected_text":"REGISTERED. A new identity was created"}]
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"With a registered key file, the server offers recall and calibrate tools.","source":"Then `achromat_recall` and `achromat_calibrate` appear in place of the registration tool.","input":"Start the server with the registered key file.","expected":"Recall and calibrate tools become available.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"Could not reach"}]
EOF
cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"Could not reach"}
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"NO MATCH: no verified compliant version of this call is known"}
EOF
cat > .coldpass/claims.json <<'EOF'
[{"kind":"claim","claim":"Recall reports when no verified compliant call is known.","source":"On a match you get `compliant_arguments`, a `steering_directive` and the rule that applied.","input":"Recall a deployment call with no existing lesson.","expected":"NO MATCH response advises calibration.","probe_kind":"mcp","argv":["node","<guest-path>"],"cwd":"<guest-path>","env":{"ACHROMAT_AGENT_KEY_FILE":"<guest-path>"},"tool":"achromat_recall","arguments":{"domain":"devsecops","tool_name":"deploy_service","task_description":"Deploy a service using the approved release workflow","arguments":{"environment":"staging"}},"expected_text":"NO MATCH: no verified compliant version of this call is known"}]
EOF
<env-var>=<guest-path> python3 -I <guest-path> --validate --replay
cat > .coldpass/report.json <<'EOF'
{"outcome":"working","fault_owner":null,"operation":"Built the documented Node MCP server, registered a guest-local identity during manual exercise, then called achromat_recall and replayed the no-match response.","operation_scope":"Node.js 22.23.4 (README requires Node.js 20+); npm install; npm run build; npm run typecheck; npm test; real MCP recall with signed registered key.","steps":["Read README and package entry points.","Initialized git metadata and fetched pinned commit f1c086e89c388ce920908af9a21abd76c0950f5d.","npm install succeeded.","npm run build succeeded.","npm run typecheck succeeded.","npm test passed: 8 files and 155 tests.","Called achromat_register_identity with explicit true in the disposable guest; MOM registered the identity and saved the key under .coldpass.","Called achromat_recall for a deployment request; received NO MATCH and calibration guidance.","Checker validation and replay passed."],"deviations":["The initial registry probe performed identity registration and changed the registered tool list; final probe uses achromat_recall with the resulting guest-local key. No user or host secrets were used."],"stuck_step":null,"main_blocker":null,"plain_failure":null,"suggested_fix":null}
EOF
ls -la .coldpass && git status --short

No product verdict. Run record.