Public preview Simulated payments · Fixed registry snapshot

PROTOCOL WORKBENCH

Measure before
you ship.

Catch changes to tool schemas, Agent Cards, and payment terms before they reach your agents.

Protocol inspector

Paste a capture or start with an example.

Runs in your browser

Evidence

catalog-tools.json EXAMPLE

Paste a tools/list result, its JSON-RPC response, or an array of tools.

Measurement

MEASURING
—Input tokens
—Compact tokens
—Capture size

Execution cost model

Estimate the monthly cost of including this capture in an agent’s context.

Usage assumptions

EDITABLE SCENARIO
Include output and API fees

Use the input rate you actually pay. If your client already compacts or caches input, modeled savings can differ.

Original monthly estimate—
With compact JSON—
Modeled monthly savings—

Release Guard Kit

Set one release policy for MCP, A2A, and x402 in your existing CI job.

Catch regressions on every pull request

  • Gate on token budgets, schema changes, and changes to x402 amounts or recipients.
  • Run the self-contained Node CLI with a starter policy and GitHub Actions workflow.
  • Get Markdown summaries for reviewers and JSON for automation.
See an example report
$19 USD · one-time download

Checking checkout availability…

Registry Change Brief

Check which published MCP versions or declared transports changed before updating an integration.

Official registry source

Read before you pay

Preview coverage and observed changes for free. The full brief adds version timelines, transport differences, and links back to the original records.

    Checking the latest brief…

    0.01 USDCper brief · x402
    GET /v1/catalog
    GET /v1/registry/brief

    Registry snapshot

    Recent active listings from the official MCP Registry.

    Official MCP RegistrySelect Refresh view to load the snapshot.

      Automate release checks

      Save a known-good baseline and run the same measurement in CI.

      Use the local CLI

      Capture the candidate in your existing test job. Set a compact-token budget and fail on changes when you need review.

      Download sample capture
      node src/cli.mjs baseline mcp known-good.json > baseline.json
      node src/cli.mjs audit mcp candidate.json \
        --baseline baseline.json --max-tokens 1000 --fail-on-change

      Run from the AgentCaliper project. The audit returns JSON and a CI-friendly exit code.

      What the measurements cover

      Token counts

      Counts use o200k_base on the supplied or decoded JSON. Compacting removes whitespace outside strings and keeps numeric spellings. Model wrappers, caching, and tool selection can change what a provider bills.

      Release comparisons

      Baselines store hashes, counts, and item labels. Comparisons identify changed definitions and selected contract fields. Export a baseline for each service and access profile you measure.

      Protocol evidence

      Findings cover selected structural checks. They describe the supplied capture. A live service, verified signatures, security, and payment settlement require separate evidence.