GaugeMesh
OCI · GHCR.IO/ALIENGINEERING-BYTE/GAUGEMESH@SHA256:69F3CCB7C2FDCD9B6897C99EBA22D18BE1384957BB2DBDF760F8273EE2E43189
Route MCP capabilities through deterministic identity, policy, budget, and deadline constraints.
Last scanned (10 hours ago)
Scores higher than 98% of OCI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aliengineering-byte/gaugemesh). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 58 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 242 tokens (~26/item across 9 items; 7 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | aliengineering-byte/gaugemesh |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aliengineering-byte/gaugemesh/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 2753517277 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
docs-a__search ~24
Search the deterministic docs-a fixture
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
docs-b__search ~24
Search the deterministic docs-b fixture
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
gaugemesh_describe ~24
Describe one exact capability
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | – |
No output schema declared.
No examples provided.
gaugemesh_invoke ~42
Invoke a capability inside an exact lease
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | – |
| arguments | object | – | – |
| leaseId | string | yes | – |
No output schema declared.
No examples provided.
gaugemesh_lease ~46
Issue a bounded capability lease with explicit side-effect authority
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | yes | – |
| sideEffects | array | – | – |
| ttlMs | integer | – | – |
No output schema declared.
No examples provided.
gaugemesh_release ~24
Release a capability lease
| Name | Type | Req | Description |
|---|---|---|---|
| leaseId | string | yes | – |
No output schema declared.
No examples provided.
gaugemesh_search ~32
Deterministically search reviewed capabilities
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the GaugeMesh MCP server?
GaugeMesh runs locally as a container image, launched with docker run --rm -i ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189
claude mcp add aliengineering-byte-gaugemesh -- docker run --rm -i ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189
What is the GaugeMesh MCP server?
GaugeMesh is an MCP server listed in the public MCP registry as io.github.aliengineering-byte/gaugemesh. Route MCP capabilities through deterministic identity, policy, budget, and deadline constraints. This page covers its container image (ghcr.io/aliengineering-byte/gaugemesh@sha256:69f3ccb7c2fdcd9b6897c99eba22d18be1384957bb2dbdf760f8273ee2e43189).
Is the GaugeMesh MCP server safe to use?
GaugeMesh scores 60 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 GaugeMesh MCP server expose?
GaugeMesh exposes 7 tools: docs-a__search, docs-b__search, gaugemesh_search, gaugemesh_describe, gaugemesh_lease, and 2 more. Their descriptions and schemas cost roughly 216 tokens of context every time the server is loaded.
Is the GaugeMesh MCP server still maintained?
GaugeMesh is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the GaugeMesh MCP server under?
GaugeMesh 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.