coldpass

Guard-Core/guard-core-mcp

GitHub ↗ · How this check works

Per-setup public labels: Linux / Haiku: Works

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/Guard-Core--guard-core-mcp.svg).

api-securitydeveloper-toolsfastapipythonsecurity

Works

Only older checks are saved; no current product test.

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

Tested on Linux
PlatformHaikuLuna
Linuxyes

Linux / Haiku 5.5: yes · Oct 18, 2026 · 30953b986807 · claude-code / 2.1.300 (Claude Code)
Recorded operation: <host-path> · local stdio MCP start + initialize + tools/list

MCP
yes, local
Yes, runs locally
Needs keys or browser
None seen
Issue
none found in recorded check

Safety: no observations were recorded for the selected revision. Functional results do not establish a safety result.

Run details

Haiku 5.5

Native agent · Checked operation passed

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

Agent-reported scope: Start the guard-core-mcp stdio server (README 'Install' entry point guard-core-mcp) and list its tools via MCP initialize + tools/list; 9 tools returned: versions, validate_config, config_fields, search_docs, get_doc, check_payload, ecosystem, adapter_setup, wire_agent.

MCP server returned: guard-core · version 1.7.0.

MCP tools returned: versions, validate_config, config_fields, search_docs, get_doc, check_payload, ecosystem, adapter_setup, wire_agent. Tool listing does not establish authenticated tool-call success.

Run details
run
Guard-Core--guard-core-mcp-claude-haiku-5-5-1792346410801822302
date
Oct 18, 2026
time to working
not recorded
product hosting / execution
Local stdio MCP server in the guest
recorded operation scope
product operation
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.006734
Recorded source
https://github.com/Guard-Core/guard-core-mcp
Tool transport
mcp-assigned-vm
Test version
readme-2e7d3cb1b49a8213de0d5c33ce91d6c77432809ec683ffa1501492f502faa935
revision
30953b986807562bfdb02fd36cb83d2da03f3ffa
What the agent did

Start the guard-core-mcp stdio server (README 'Install' entry point guard-core-mcp) and list its tools via MCP initialize + tools/list; 9 tools returned: versions, validate_config, config_fields, search_docs, get_doc, check_payload, ecosystem, adapter_setup, wire_agent.

cd <host-path> && git log -1 --format=%H 2>/dev/null; ls -la; cat README.md 2>/dev/null | head -200
cat <host-path> | head -80; ls <host-path>
cd <host-path> && which uv python3 pip3; python3 --version; cat .python-version; grep -n -A3 '\[project.scripts\]' pyproject.toml; grep -n 'requires-python' pyproject.toml; ls .coldpass 2>/dev/null; sed -n 1,80p Makefile | grep -n -i -E 'install|run|mcp' 
cd <host-path> && sed -n 5,20p Makefile; (python3 -m venv <host-path> 2>&1 || (sudo apt-get install -y python3-venv >/dev/null 2>&1 && python3 -m venv <host-path>)) && <host-path> install -q uv 2>&1 | tail -3; <host-path> --version
cd <host-path> && sudo apt-get update -qq >/dev/null 2>&1; sudo apt-get install -y -qq python3-venv >/dev/null 2>&1; rm -rf <host-path>; python3 -m venv <host-path> && <host-path> install -q uv 2>&1 | tail -3; <host-path> --version
cd <host-path> && export PATH=<host-path> NODE_USE_ENV_PROXY=1 && uv sync 2>&1 | tail -15; echo EXIT=$?; ls .venv/bin | grep guard-core
cd <host-path> && printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' '{"jsonrpc":"2.0","method":"notifications/initialized"}' '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | timeout 60 <host-path> 2>/tmp/mcp_err.txt | python3 -c 'import sys,json
for l in sys.stdin:
    m=json.loads(l)
    if m.get("id")==2: print([t["name"] for t in m["result"]["tools"]])
    elif m.get("id")==1: print("init ok:", m["result"]["serverInfo"])'; echo rc=$?; tail -3 /tmp/mcp_err.txt
cd <host-path> && mkdir -p .coldpass && cat > .coldpass/probe.json <<'EOF'
{"kind":"mcp","argv":["<host-path>"}
EOF
cat > .coldpass/report.json <<'EOF'
{"outcome":"working","operation":"Start the guard-core-mcp stdio server (README 'Install' entry point guard-core-mcp) and list its tools via MCP initialize + tools/list; 9 tools returned: versions, validate_config, config_fields, search_docs, get_doc, check_payload, ecosystem, adapter_setup, wire_agent.","operation_scope":"Covers server start and tools/list only. Does not exercise validate_config/check_payload against a real config; no credentials or browser required.","steps":["uv sync (uv 0.13.1 installed into <host-path> venv via pip; Makefile 'install' target is 'uv sync')","Verified .venv/bin/guard-core-mcp and guard-core-mcp-http entry points exist","Ran guard-core-mcp over stdio: initialize (server guard-core 1.7.0) then tools/list"],"deviations":["README 'Install' shows 'uv add --dev guard-core-mcp' and 'claude mcp add'; not run because they would modify the checkout's pyproject/uv.lock. Used the Makefile 'install' target (uv sync) instead.","uv was not preinstalled; python3-venv was missing, so installed it via apt, then installed uv with pip into a venv at <host-path>"],"stuck_step":null,"main_blocker":null,"suggested_fix":null}
EOF
python3 -m json.tool .coldpass/probe.json >/dev/null && python3 -m json.tool .coldpass/report.json >/dev/null && echo JSON_OK; <env-var>=<host-path> python3 -I <host-path> --validate; echo rc=$?