Noticer Expected Result Checks

Noticer: check the expected result before the next action

MCPB 0.4 UV commercial preview, version 0.3.2-dev.20261016. Linux and macOS/POSIX only. Windows is explicitly unsupported; macOS execution remains untested. This commercial connector is separate from the legacy operator-provisioned integration. The existing 0.1.0 owner API connector does not provide this commercial flow.

Setup

Use an MCPB 0.4 host with UV support. The host resolves pinned mcp1.29.0 and cryptography50.0.0 dependencies; none are bundled. Fresh UV dependency resolution and runtime checks use this exact pinned dependency set; GUI host installation is a separate check.

No pre-existing config or credentials are required to connect and list tools. Leave the optional advanced configuration field empty. Initialization makes no remote call and creates no buyer state.

Ask the agent to show the setup notice, then explicitly approve noticer_initialize_local. On POSIX this creates an owner-only state directory with a0600 random local custody key and config. The canonical service origin and independently verified public signing key are pinned; no trust-on-first-use or key substitution from receipts/discovery occurs. Default location is XDG_STATE_HOME/noticer or ~/.local/state/noticer on Linux, and ~/Library/Application Support/Noticer on macOS. Native Windows setup is refused. A repeated setup reuses state; partial files and symlinks are never overwritten or re-keyed.

Encryption and its local key are protected by the same OS-user boundary. They do not protect against compromise of that OS user. Keep private backups separately; never paste credentials into chat.

Optionally consent to finding an already installed trusted Link CLI during local setup. This only discovers and validates its resolved executable; it never runs it, installs it, signs in, changes wallets or requests a payment. An existing authorized wallet is required before the separate payment tool can work.

Next review the service /start terms and explicitly approve commerce enrollment. Local setup is not enrollment or payment consent. Existing advanced users can still select their own private config using origin, private_directory, custody_key_file and trusted_public_key_file, with optional tenant_key_file, expected_build_sha and link_cli_path. Advanced configuration preserves its explicitly chosen trust; the default flow enforces the bundled public pin.

Headless Linux with uv (tested) does not need a GUI host. The same commands are in AGENT_GUIDE.md › Linux with uv. macOS runtime is untested; native Windows is unsupported.

Linux with uv (tested), no GUI host needed

Requires uv, curl, unzip, sha256sum and Python 3.10+. The install directory must be writable, because uv creates .venv inside it on first run.

VER=0.3.2-dev.20261016

DIR="$HOME/.local/share/noticer-mcp/$VER" mkdir -p "$DIR" && cd "$DIR" curl -fsSLO "https://github.com/zensteagarden/noticer-open/releases/download/noticer-commercial-mcp-v$VER/noticer-commercial-mcp-$VER.mcpb"

A bundle cannot contain its own hash: read it from the published Registry record.

SHA=$(curl -fsSL "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.zensteagarden%2Fnoticer/versions/$VER" | python3 -c 'import sys,json; print(json.load(sys.stdin)"server"0)') echo "$SHA noticer-commercial-mcp-$VER.mcpb" | sha256sum -c - unzip -q "noticer-commercial-mcp-$VER.mcpb"

Optional smoke test (starts the server, lists its tools and exits; creates no state and makes no Noticer request):

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"}' \ | NOTICER_COMMERCIAL_CONFIG_FILE= uv run --frozen --quiet --directory "$DIR" sales_mcp.py 2>/dev/null \ | python3 -c 'import sys,json for line in sys.stdin: m=json.loads(line) if m.get("id")==1: print("initialized:", m"result") if m.get("id")==2: print(len(m"result"), "tools:", ", ".join(t["name"] for t in m"result"))'

You should see 10 tools: noticer_commercial_setup, ….

MCP host config (mcpServers JSON for Claude Desktop/Cursor-style hosts)

Replace /home/YOU with your absolute home directory, since hosts don't expand $HOME:

{

"mcpServers": { "noticer": { "command": "uv", "args": ["run", "--frozen", "--quiet", "--directory", "/home/YOU/.local/share/noticer-mcp/0.3.2-dev.20261016", "sales_mcp.py"], "env": { "NOTICER_COMMERCIAL_CONFIG_FILE": "" } } } }

Then ask your agent to call noticer_commercial_setup.

Ten tools

Discovery, consent-gated local setup, enrollment, account, prepare, run, status, challenge, Link payment, and verified receipt. Scope is an explicitly authorized public HTTPS JSON predicate and a different known-good control on the same host. Confirm exact frozen scope before run. Five eligible initial checks; exact entitlement is server-controlled. Later eligible receipt access is one USD1 payment with separate owner/Link approval. Poll at most every three seconds.

Payment tools can cause a real charge when enabled and approved. SPT/capability stay private process memory and encrypted custody; returned approval URL goes to app.link.com. Denied/expired requests stop. Unknown create without an ID holds. Unknown submitted payment permits only existing-attempt read recovery, never reauthorization or resubmission. Receipt access is not evidence of success until two byte-identical packages pass pinned Ed25519/scope/package verification. No downstream action is performed.

Verification and source scope

No real buyer enrollment, wallet grant, payment, or provider request was used for the offline acceptance tests. This is no live customer acceptance claim. Apache2.0 covers this distributed buyer connector and standalone verifier, consistent with the existing public connector and owner-approved client-only scope. LICENSE/NOTICE are retained from the public repository. Nothing here licenses or contains the private Noticer platform, engine, seller billing backend, database, customer evidence, or production keys.

Source checkout

For source installation use INSTALL.md and install_local.py. Run the local suite with python -m unittest discover -s tests -v. No private server fixtures are included. Package entry is sales_mcp.py; manifest.json declares the UV stdio launch. The repository’s existing Node verifier remains separate and unchanged.

See AGENT_GUIDE.md for call triggers, exact supported scope, examples, outputs and consent limits. This revision changes discovery descriptions, not verification/payment behavior or pricing.