GaugeMesh MCP server

GaugeMesh

One endpoint for MCP capabilities and model routes—without losing identity, authority, budgets, deadlines, side-effect semantics, or causal evidence between protocols.

GaugeMesh is a local-first Rust developer preview. It is deliberately narrower than a general AI gateway: every adapter must preserve declared invariants or reject the operation before a side effect. Route selection is fixed-point, deterministic, and explainable. The base deployment is one binary with memory or SQLite; it needs no hosted control plane, Redis, PostgreSQL, Docker, or Kubernetes.

Install without Rust from the checksummed, attested GitHub Release or run the multi-architecture GHCR image. Crates.io is not a GaugeMesh distribution channel. The real stdio MCP server is gaugemesh mcp-stdio; its Official MCP Registry metadata is checked in as server.json.

The source tree also provides opt-in bounded durable Runs: caller-authored plans over the existing Tasks, verified file outcomes, explicit resume/cancel, and offline evidence verification. See that contract for the local Unix boundary and the external installed-binary qualification commands.

Two explicit first-use paths are available from release source:

observable worker effects, restart/refusal cases and offline verification.

• A neutral recoverable Run, with

using the same public interface. Its original formulas stay outside the binary; standards catalog metadata is not an authorized rule implementation or approval.

• An optional educational section-mechanics review,

Run the local proof

From a release archive:

gaugemesh demo

From source with Rust 1.88 or newer:

cargo run --locked --release -- demo

No account, credential, provider, network target, database, container, or existing MCP server is used. The command writes no file to the caller directory.

Actual output from the 0.1.0 release binary:

GaugeMesh demo

[ok] 2 MCP sources connected
[ok] 1 model route connected
[ok] colliding tool names isolated by capability identity: true
[ok] 2 capabilities leased
[ok] route selected under cost, deadline, and policy bounds
[ok] deterministic failure reproduced
[ok] recovery bounded to one attempt
[ok] duplicate effects: 0
[ok] invariants preserved or strengthened: 23/23
[ok] cleanup complete: no owned child or listener remains

Route: local-model -> docs-a__search
Decision: sha256:169a6315aa69eb7fa3e3b5aae70ede14d4c9ec71c0281d217fd84201414567f1
Evidence: sha256:9a9cdc8b673bab79ae96cf5aba5b7895d6e6e5f425407d1bd64da8701a1314e6

What the demo proves

authorization identity.

• Two upstreams can expose the same native search name without sharing an

expiry, scope, budgets, side-effect permission, and manifest digest.

• A lease binds an exact principal, tenant, task, schema, capability set,

breaker.

• Hard route constraints run before an integer action score and stable tie

semantic loss.

• One injected failure consumes the single retry budget; it cannot amplify.
• The checked translation preserved or strengthened 23 invariants with zero

owned child process or listener.

• The read-only case observed zero duplicate effects and completed with no

The demo is deterministic fixture evidence, not a production-duration soak or security certification.

Inspect the route planner and its versioned decision contract independently. The final command uses a built-in fixture in which every candidate violates a hard constraint, so the output is a digest-bound denied decision rather than an unsafe fallback:

gaugemesh route explain
gaugemesh route explain --decision-contract
gaugemesh route explain --deny-all
gaugemesh route schema
gaugemesh route validate decision.json

Architecture

Shortened. The full README is on GitHub.