# Noticer Expected Result Checks (mcpb · noticer-commercial-mcp-0.3.2-dev.20261016.mcpb) After a handoff, check one public JSON field equals one exact value. Signed receipt. 5 free checks. - Trust score: 40/100 (low) - Change this week: +1 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-23 ## Components - mcpb · `noticer-commercial-mcp-0.3.2-dev.20261016.mcpb`: 40/100 (this document), [markdown](https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp.md), [page](https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp) ## Channel facts - Registry: `mcpb` - Package: `https://github.com/zensteagarden/noticer-open/releases/download/noticer-commercial-mcp-v0.3.2-dev.20261016/noticer-commercial-mcp-0.3.2-dev.20261016.mcpb` - Version: `0.3.2-dev.20261016` - Transport: `stdio` - SHA-256: `cc34e591327b60362923f895b710ccc43264317a01b9dfc0c1dbd3393390d7fb` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-23. - **Supply Chain Security**: 13/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs were checked across the 32 of 32 dependencies we could resolve, so this covers what we could see, not the whole tree. - Install-script risk not yet assessed. - 0 of 32 dependencies flagged as unhealthy. - **Provenance & Transparency**: 48/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (Apache-2.0). - Actively maintained (last published 7 days ago). - Publishes a security disclosure policy (SECURITY.md). - **Schema Quality & AI Usability**: 59/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 1931 tokens (~193/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the Noticer Expected Result Checks MCP server? Noticer Expected Result Checks ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cc34e591327b60362923f895b710ccc43264317a01b9dfc0c1dbd3393390d7fb; the commands to do that are on this page. If it does not match, do not open it. - Download bundle: `https://github.com/zensteagarden/noticer-open/releases/download/noticer-commercial-mcp-v0.3.2-dev.20261016/noticer-commercial-mcp-0.3.2-dev.20261016.mcpb` - SHA-256: `cc34e591327b60362923f895b710ccc43264317a01b9dfc0c1dbd3393390d7fb` ### Verify on macOS / Linux ```bash echo "cc34e591327b60362923f895b710ccc43264317a01b9dfc0c1dbd3393390d7fb noticer-commercial-mcp-0.3.2-dev.20261016.mcpb" | shasum -a 256 -c ``` ### Verify on Windows (PowerShell) ```powershell (Get-FileHash -Algorithm SHA256 .\noticer-commercial-mcp-0.3.2-dev.20261016.mcpb).Hash -eq "cc34e591327b60362923f895b710ccc43264317a01b9dfc0c1dbd3393390d7fb" ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-21 (score 40, 0) - [security regression] Provenance: unverified → fail ### 2026-10-20 (score 40, 0) - [security regression] Provenance: fail → unverified ### 2026-10-17 (score 40, +1) - [functional] Dependency health: partial → 1.00 ### 2026-10-16 (score 39, +25) - [security improvement] Injection markers: unverified → pass - [security] First check of Judged manipulation: pass - [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). - [functional improvement] Tool coverage: unverified → 100 - [functional improvement] MCP protocol: unverified → pass - [functional] First check of Tool coverage: 0 - [functional] First check of Schema quality: fail - [functional] First check of Schema quality: fail - [functional] First check of Destructive annotations: 100 - [functional] First check of Schema quality: good - [functional] First check of Tool coverage: 100 - [functional] Dependency health: 1.00 → partial - [functional] Package version: 0.3.1-dev.20261008 → 0.3.2-dev.20261016 - [functional] Package version: 0.3.1-dev.20261008 → 0.3.1-dev.20261015 ### 2026-10-14 (score 14, 0) - [security] Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. - [security] Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. - [functional] Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. - [functional] Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. - [functional] Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. ### 2026-10-10 (score 14) First indexed and scored. ## MCP tools (10) ### `noticer_commercial_setup` (~108 tokens) Start here when an action you sent or delegated needs its result confirmed, your own tools can't confirm it, and the result is one field in public HTTPS JSON. Shows setup state and the published USD 1 price. Creates nothing. Returns local setup state, canonical terms location and published USD 1 receipt price without creating an account, order or payment. A missing local configuration does not prevent tool discovery. This is setup guidance, not a verified outcome or a guarantee of free eligibility. ### `noticer_commercial_account` (~62 tokens) After enrollment, read how many free checks remain. No charge. Use this to understand eligibility before preparing a public JSON check. Preparation reserves no allowance, and the finalized order entitlement remains authoritative. No payment is made and no credential is returned. ### `noticer_prepare_receipt` (~307 tokens) Describe the destination state to check: the exact public JSON record (claim_id_path) that should show the result of the handed-off action, the expected value, and a known-good control on the same site. Only after owner authorization for public reads. Doesn't observe, charge or reserve an allowance. Only after owner authorization for these public reads. Inputs: a stable check_label and scope with claim_ref; questioned {url, extract, claim_id_path}; control {url, extract}; deadline_seconds; authorized_public_read=true. Both URLs must be public HTTPS JSON on the same host, with distinct paths and no credentials, query or fragment. The claim_ref must occur as a questioned path segment and not in the control path. Use a genuinely known-good control. Dotted paths support equality to a JSON scalar, for example extract '$.status == "shipped"' and claim_id_path '$.id'; this is not general JSONPath or code. deadline_seconds must be an integer from 20 through 120. Server validation is final. Returns the frozen scope, obligation hash, price and confirmation notice. No observation or payment occurs here; free allowance is not reserved. Show those terms and obtain separate explicit run approval. Reuse check_label with the identical scope after interruption; never create a new label to recover ambiguous preparation. No receipt is guaranteed for every failed request. Input parameters: - `check_label` (string, required) - `scope` (object, required) ### `noticer_run_receipt` (~150 tokens) Observe the saved public JSON condition only after approval of the exact frozen scope and confirmation notice. Reads only; it never pays or performs or repeats the original action. Supply its saved obligation_hash. Both booleans must reflect explicit owner approval, including possible free-check consumption; they are caller assertions, not independent proof of consent. Starts observation and returns a check identifier. It never pays or performs the downstream action. Evidence access may later require separate USD 1 approval. Poll status no more frequently than 3 seconds. Input parameters: - `check_label` (string, required) - `confirmed` (boolean, required) - `no_spend_terms_confirmed` (boolean, required) - `obligation_hash` (string, required) ### `noticer_receipt_status` (~103 tokens) Poll (at least 3 s apart). A verdict shown here is unverified; don't continue a workflow on status alone. Wait at least 3 seconds between polls. Any displayed verdict is unverified: do not continue a workflow based on status alone. The response reports entitlement and next-step guidance, not authorization to act. For an uncertain saved payment it can inspect that same attempt; it never submits another payment. Input parameters: - `check_label` (string, required) ### `noticer_get_verified_receipt` (~208 tokens) Verify the signed receipt locally. Only fresh, valid PROVED (control matched) supports continuing. DISPROVED or INCONCLUSIVE means the result isn't confirmed. The signature authenticates the issuer, not source honesty. Use a stable caller-local decision_ref for that intended next action. Verifies two byte-identical retrievals against the independently pinned key, order, saved scope, freshness and package binding. Returns a verified receipt verdict and locally derived decision: fresh valid PROVED/ALLOW may yield continue/0; DISPROVED yields block/20; INCONCLUSIVE yields hold/21 and a blocking server gate. Invalid, stale, mismatched or untrusted evidence is rejected, never converted to continue. Raw evidence and capabilities remain encrypted locally. The local decision is unsigned and does not grant permission or execute a downstream action. A signature authenticates the issuer, not source honesty. Input parameters: - `check_label` (string, required) - `decision_ref` (string, required) ### `noticer_enroll_commerce` (~156 tokens) Enroll once when the owner chooses commercial public-JSON checks and needs commerce-only access. First show https://noticer-mpp-ee54698-production.up.railway.app/start. Obtain host action-time approval for persistent commerce access and acceptance of terms before setting the consent booleans true. New self-service buyers receive five eligible free checks; later eligible receipts cost USD 1 with separate wallet approval. Enrollment itself never charges. Returns account-setup metadata while the credential and recovery secret remain in encrypted local custody. Booleans assert consent, not proof. Input parameters: - `commerce_scope_accepted` (boolean, required) - `owner_authorized` (boolean, required) - `terms_accepted` (boolean, required) ### `noticer_payment_challenge` (~148 tokens) Get exact one-order payment terms only after the owner approves USD 1 for an eligible saved receipt. This prepares a public challenge, never a charge, and needs no wallet. Merchant and network must come from independently verified provider configuration. Returns bound challenge/endpoint metadata; order capability stays private. The separate optional existing-Link payment tool requires wallet approval. Never put SPTs, payment credentials or keys into tool arguments, chat, model output or logs. Input parameters: - `amount` (integer, required) - `check_label` (string, required) - `confirmed` (boolean, required) - `currency` (string, required) - `merchant_account` (string, required) - `network_id` (string, required) ### `noticer_pay_with_existing_link` (~179 tokens) Pay for one eligible saved receipt only after separate exact USD 1 consent using an existing authorized Link wallet. Show the merchant, network, one-time amount and saved challenge first. Present any returned Link approval_url; resume only the SAME check_label/request. Both local consent and the wallet's approval are required. This tool can submit a real payment; approval alone is not settlement and settlement is not verified evidence. Never install software, log in, switch payment methods, or create a replacement request after denial, expiry or an uncertain payment. Credentials remain private subprocess memory; only sanitized status and approval URL are returned. After settlement, use noticer_get_verified_receipt. No downstream action runs. Input parameters: - `amount` (integer, required) - `check_label` (string, required) - `confirmed` (boolean, required) - `currency` (string, required) ### `noticer_initialize_local` (~138 tokens) Set up local private custody after the owner chooses Noticer and explicitly consents to local setup. Creates owner-only POSIX state/config and a random custody key with the canonical origin and independently pinned public signing key; no trust-on-first-use. Returns setup status, never secrets. Does not enroll, contact a server, pay, install software or sign in. Optionally discover an already installed trusted Link CLI only after consent. The key and encrypted records share one OS-user boundary; this does not protect against compromise of that same user. Input parameters: - `enable_existing_link` (boolean) - `owner_authorized` (boolean, required) ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp#diagnostics ## Score history - 2026-10-23: 40 - 2026-10-22: 40 - 2026-10-21: 40 - 2026-10-20: 40 - 2026-10-19: 40 - 2026-10-18: 40 - 2026-10-17: 40 - 2026-10-16: 39 - 2026-10-15: 14 - 2026-10-14: 14 - 2026-10-13: 14 - 2026-10-12: 14 - 2026-10-10: 14 ## Common questions ### What is the Noticer Expected Result Checks MCP server? Noticer Expected Result Checks is an MCP server listed in the public MCP registry as io.github.zensteagarden/noticer. After a handoff, check one public JSON field equals one exact value. Signed receipt. 5 free checks. This page covers its MCPB bundle (https://github.com/zensteagarden/noticer-open/releases/download/noticer-commercial-mcp-v0.3.2-dev.20261016/noticer-comm…). ### Is the Noticer Expected Result Checks MCP server safe to use? Noticer Expected Result Checks scores 40 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 Noticer Expected Result Checks MCP server expose? Noticer Expected Result Checks exposes 10 tools: noticer_commercial_setup, noticer_commercial_account, noticer_prepare_receipt, noticer_run_receipt, noticer_receipt_status, and 5 more. Their descriptions and schemas cost roughly 1,559 tokens of context every time the server is loaded. ### What licence is the Noticer Expected Result Checks MCP server under? Noticer Expected Result Checks declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - Repository: https://github.com/zensteagarden/noticer-open - Website: https://noticer.dev/when-to-use - Changelog RSS feed: https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp.json - HTML version of this page: https://verifymcp.io/servers/zensteagarden-noticer/noticer-commercial-mcp