Commerce Evidence Toolkit MCP server

Commerce Evidence Toolkit

Three local, read-only checks for agents working with product data. The package wraps the same versioned comparison rules published in the Agentic Commerce Field Guide.

Version 0.1.0 · MIT licensed. Download the versioned release, or run the source as described below. Registry availability is separate from a GitHub release; consult the live registry for its current state.

What it does

The checks do not fetch references, authenticate evidence, contact a merchant, change a feed, place orders or send telemetry. A match is not provider acceptance, live product truth, physical fit or compatibility. This is a selected local review contract, not a complete provider schema validator. Hold results are evidence decisions, not protocol failures.

Install the versioned bundle

Download commerce-evidence-toolkit-0.1.0.mcpb and SHA256SUMS from the v0.1.0 release. Check the archive against its published SHA-256 checksum. The bundle contains the server and production dependencies; Node.js 22 or later is required.

Use your compatible client's MCPB import flow, or extract the archive to a directory and configure the absolute path to its server/index.mjs using the JSON example below. MCPB support varies by client. Protocol tests do not establish certification by any desktop app.

A Node package archive is also included in the release. Installing that archive requires npm to install its dependencies. It has not been published to npm.

Run from source

Requires Node.js 22 or later and npm. Dependency installation uses the network; the three comparison operations run locally after installation.

npm ci --ignore-scripts
npm test
node server/index.mjs

The final command starts an MCP server over standard input/output. It waits for a compatible client; it is not a browser URL. Do not print debug messages to stdout, which carries the protocol.

For a compatible client that accepts an MCP JSON configuration, replace the path below with the absolute location of your checkout:

{
  "mcpServers": {
    "commerce-evidence": {
      "command": "node",
      "args": ["/absolute/path/agentic-commerce-field-guide/server/index.mjs"]
    }
  }
}

Client configuration locations differ. This example declares the transport and executable; it does not claim every assistant automatically installs or invokes the server.

Try a complete input

The files in examples/ are complete tool arguments, not bare internal records. The three starter examples below are fictional and use frozen times where relevant.

Shortened. The full README is on GitHub.