Noticer Expected Result Checks MCP server

Noticer

Your automation says it succeeded. Noticer checks.

Start here

• Check the expected result before the next action: see the commercial agent guide for when to call Noticer, its exact supported scope, outputs and consent steps. This POSIX-only client checks an explicitly authorized public HTTPS JSON predicate with a separate known-good control. It connects without an existing config file, then asks for consent before local setup and commerce enrollment. Five eligible checks are free; later eligible receipt access costs USD 1 with separate approval through the caller’s existing Link wallet.
• Existing operator-provisioned integrations: MCP 0.1.0 remains the legacy owner-API connector. Its installation guide requires assigned API access; it does not provide the new self-service commerce flow.
• Try the offline verifier: follow the Node.js quick start below. It checks supplied evidence packets locally without an account, API key or network access.

The 0.3.1 commercial release includes clearer agent-facing instructions and tool descriptions. Follow the agent guide for installation.

The commercial client has passed fresh Linux/UV installation, offline protocol checks, and mocked end-to-end payment tests. No real buyer payment is claimed. macOS runtime testing remains outstanding; native Windows is unsupported. Keep credentials out of chat and review the frozen scope before running a check. A verified receipt never executes a downstream action.

Current commercial MCP Registry listing · Setup help

Offline public verifier

Noticer starts one step earlier than most automation tools: what are you actually trying to have happen?

The public project helps turn a human intention into an explicit Success Contract, then independently verifies disclosed evidence under small deterministic rules. The model or agent may help clarify the goal; it does not author the verifier's verdict.

Understand before acting. Observe before believing.

The user defines success. Automation attempts it. Noticer reports what the evidence can establish.

This repository is the public, Apache-2.0 verifier and protocol. It does not include Noticer's private service, private discovery/learning mechanics, billing, customer data or deployment secrets.

See the whole idea in about a minute

Use Node.js 24 and run:

node examples/guided-first-run.mjs --demo

The demo does four things:

1. states a human intention;
2. freezes a small Success Contract and its limits;
3. rejects a synthetic false-green packet where the automation said success but the evidence does not match;
4. accepts a disclosed exact-text packet while still explaining what that ALLOW does not prove.

No account, API key, model, payment, database or network access is required. There are no npm dependencies.

Let Noticer guide your own check

node examples/guided-first-run.mjs

It asks four short questions and reflects the Success Contract back before you confirm it. Confirmation clarifies the check; it does not authorize any external action.

Read the intention guide, Success Contract v1, and the agent guide if you want to connect Noticer to ChatGPT, Claude, Cursor or another agent. Keep the agent outside the deterministic verdict path.

Run the verifier directly

The original synthetic packet contains accepted, while its declared expectation is ok:

Shortened. The full README is on GitHub.