MCP release workspace

A quieter release day.

Capture the contract. Exercise the tools. Give every MCP release a clear decision and a trail your team can follow.

Loading signed GitHub run history…

Connected repository

valor-projects/beaconserve-customer-demo

Waiting for first signed run

This demo uses a synthetic order server. Every entry below comes from a real GitHub Actions run.

Connect your repository

A signed workflow proves repository control. No GitHub personal token is pasted into this app.

Checking your session…

What runs where

Tool execution stays in your GitHub runner. BeaconServe stores catalog snapshots, policy, sanitized test outcomes and approval records.

Do not put credentials or customer data in catalogs or test names. Runtime arguments and actual responses are not uploaded.

—Captured runs

—Latest gate

—Runtime checks passed

Release history

Catalogs and decisions tied to an exact GitHub commit.

View GitHub CI ↗

Release / run	Decision	Compatibility	Runtime	Captured

Release review

Download catalog

Compatibility policy

Tool	Contract path	Rule decision

Actual tool behavior

Results from calls made to the server in CI—not inferred from metadata.

Review & approval

An approval covers this report digest only. It cannot waive failed runtime assertions. Rerun CI after approval; a prior failed run stays in the audit trail.

Report fingerprint & trusted rules

Scope of this beta: MCP stdio with initialize-based protocol versions through 2025-11-25; up to 50 tools and 50 explicit runtime tests. HTTP transports, automatic schema migration and AI-model quality evaluation are not included. No report is a security certification. Fork PRs run local checks without publishing; configure required checks before relying on merge blocking.