# io.github.CloudCorpRecords/trustbeacon (oci · ghcr.io/cloudcorprecords/trustbeacon)

Behavioral trust scores, attestation checks and preflight verdicts for MCP servers.

- Trust score: 44/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/trustbeacon`: 71/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-trustbeacon/reneturcios-trustbeacon.md), [page](https://verifymcp.io/servers/cloudcorprecords-trustbeacon/reneturcios-trustbeacon)
- oci · `ghcr.io/cloudcorprecords/trustbeacon`: 44/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon.md), [page](https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/trustbeacon`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1508 tokens (~116/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/trustbeacon MCP server?

io.github.CloudCorpRecords/trustbeacon runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/trustbeacon:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-trustbeacon -- docker run --rm -i ghcr.io/cloudcorprecords/trustbeacon:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-trustbeacon": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trustbeacon:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-trustbeacon": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trustbeacon:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-trustbeacon -- docker run --rm -i ghcr.io/cloudcorprecords/trustbeacon:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-trustbeacon": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trustbeacon:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-trustbeacon:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/trustbeacon:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-trustbeacon": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trustbeacon:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-trustbeacon": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/trustbeacon:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 44, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 43, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 41)

First indexed and scored.

## MCP tools (13)

### `check_trust` (~103 tokens)

Get the trust score and reliability metrics for any MCP server. Use this BEFORE calling an unknown MCP server to assess if it's reliable. Returns trust_score (0-100), latency stats, uptime, success rate, and how many agents have used it. Scores above 70 indicate reliable servers. Scores below 30 indicate risky servers.

Input parameters:

- `server_url` (string, required): The URL of the MCP server to check (e.g., https://example.workers.dev/mcp)

### `clawhub_skill_trust` (~129 tokens)

Check the supply-chain trust of a ClawHub (OpenClaw) skill BEFORE installing or invoking it. After the Feb-2026 ClawHavoc supply-chain attack, third-party skills can carry malware. Returns a PASS/UNCERTAIN/FAIL badge and 0-100 score aggregating ClawHub's published security scan (VirusTotal + model), moderation verdict, and provenance. Malicious/suspicious/blocked => FAIL; unscanned => UNCERTAIN.

Input parameters:

- `skill` (string, required): The ClawHub skill slug, e.g. 'calendar'

### `verify_before_call` (~219 tokens)

Run a signed pre-invocation verification immediately before an agent sends money, credentials, private data, or write access to an MCP server. The first 3 verifications per agent are free. After that, authenticate the MCP HTTP request with Authorization: Bearer do_<api_key> for Stripe metering ($0.01/call), or call once without payment to receive x402 instructions and retry with payment_tx. Returns PASS/UNCERTAIN/FAIL/UNRATED, evidence freshness, recommendation, and a signed diligence receipt.

Input parameters:

- `agent_id` (string): Stable, non-secret agent identifier used to count the 3 introductory calls. If omitted, Dominion derives a privacy-preserving hash from network metadata.
- `payment_tx` (string): Optional Base transaction hash proving the x402 USDC payment after a payment_required response
- `reason` (string): Optional reason for verification, e.g. money, credentials, private_data, write_access
- `server_url` (string, required): The MCP server URL or tracked server name to verify

### `verify_attestation` (~101 tokens)

Cryptographically verify a Dominion signed attestation (JWS) — e.g. a trust-verdict receipt, gateway attestation, or MCP Verified badge. Stateless: checks the Ed25519 signature against Dominion's published public key (no trust in this server required). Use this to confirm a receipt another party gave you is authentic and untampered.

Input parameters:

- `jws` (string, required): The Dominion attestation as a JWS compact string (header.payload.signature)

### `preflight_check` (~159 tokens)

Run a PRE-FLIGHT due-diligence check on an MCP server BEFORE your agent invokes it. Returns a verdict (PASS/UNCERTAIN/FAIL/UNRATED) plus a SIGNED, timestamped diligence receipt you keep as proof you performed a trust check — the standard of care after the ClawHavoc/Miasma supply-chain attacks. Call this before connecting to or invoking any unfamiliar MCP server.

Input parameters:

- `registry` (string): Optional: set to 'clawhub' to vet an OpenClaw/ClawHub skill instead of an MCP server
- `target` (string, required): The MCP server URL/name — or a ClawHub skill slug (with registry:'clawhub') — to vet before invoking

### `report_interaction` (~186 tokens)

Report the outcome of calling an MCP server. Call this AFTER you use any MCP server to contribute to the trust network. Your report helps other agents make better decisions. This is free and takes <1ms.

Input parameters:

- `error_message` (string): If failed: brief error description
- `error_type` (string): If failed: timeout, auth_error, invalid_response, server_error, rate_limited, schema_mismatch
- `http_status` (integer): HTTP status code returned (200, 429, 500, etc.)
- `latency_ms` (number): How long the call took in milliseconds
- `server_url` (string, required): The URL of the MCP server you called
- `success` (boolean, required): Did the call succeed? true = worked as expected, false = error or unexpected result
- `tool_name` (string): Which tool you called on the server

### `get_leaderboard` (~92 tokens)

Get the top-rated MCP servers, optionally filtered by category. Use this to discover the most reliable MCP servers in the ecosystem. Categories include: weather, finance, code, data, search, compliance, transport, productivity, communication.

Input parameters:

- `category` (string): Filter by category (optional). Leave empty for overall leaderboard.
- `limit` (integer): Number of results (default 10, max 50)

### `get_baselines` (~80 tokens)

Get behavioral baselines for a tool category. Shows what 'normal' looks like — average latency, success rates, typical call patterns. Use this to evaluate whether a specific server's performance is within normal range for its category.

Input parameters:

- `category` (string, required): The tool category to get baselines for (e.g., weather, finance, code, data)

### `check_anomaly` (~100 tokens)

Check if observed behavior from an MCP server is anomalous compared to baselines. Use this when a server seems slow, unreliable, or returns unexpected results. Returns whether the behavior deviates significantly from normal patterns.

Input parameters:

- `observed_latency_ms` (number): The latency you observed
- `observed_success_rate` (number): Success rate you've observed (0.0 to 1.0)
- `server_url` (string, required): The MCP server URL to check

### `register_server` (~118 tokens)

Register a new MCP server in the observatory. Server owners can register their servers to start building a trust score. Registration is free.

Input parameters:

- `category` (string): Primary category: weather, finance, code, data, search, compliance, transport, productivity, communication, other
- `description` (string): What the server does
- `github_url` (string): GitHub repository URL (optional, improves static score)
- `name` (string, required): Human-readable name of the server
- `server_url` (string, required): The MCP server URL

### `get_server_history` (~51 tokens)

Get daily trust score and performance history for a server over the last 30 days. Use this to see trends — is the server improving or degrading?

Input parameters:

- `server_url` (string, required): The MCP server URL

### `observatory_stats` (~44 tokens)

Get overall statistics about the Dominion Observatory — total servers tracked, total interactions recorded, coverage by category, and data freshness. Use this to understand the scope of the trust network.

### `get_compliance_report` (~126 tokens)

Export a compliance-ready audit trail of all recorded interactions. Formatted for EU AI Act Article 12 and Singapore IMDA Agentic AI Governance Framework. Filter by server, agent, or date range. Essential for enterprises that need to prove their AI agents are behaving correctly.

Input parameters:

- `agent_id` (string): Filter by agent ID (optional)
- `end_date` (string): End date in YYYY-MM-DD format (optional)
- `server_url` (string): Filter by server URL (optional)
- `start_date` (string): Start date in YYYY-MM-DD format (optional)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon#diagnostics

## Score history

- 2026-11-21: 44
- 2026-11-20: 43
- 2026-11-19: 43
- 2026-11-18: 42
- 2026-11-17: 42
- 2026-11-16: 41

## Common questions

### What is the io.github.CloudCorpRecords/trustbeacon MCP server?

io.github.CloudCorpRecords/trustbeacon is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/trustbeacon. Behavioral trust scores, attestation checks and preflight verdicts for MCP servers. This page covers its container image (ghcr.io/cloudcorprecords/trustbeacon).

### Is the io.github.CloudCorpRecords/trustbeacon MCP server safe to use?

io.github.CloudCorpRecords/trustbeacon scores 44 out of 100 on VerifyMCP. 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 io.github.CloudCorpRecords/trustbeacon MCP server expose?

io.github.CloudCorpRecords/trustbeacon exposes 13 tools: check_trust, clawhub_skill_trust, verify_before_call, verify_attestation, preflight_check, and 8 more. Their descriptions and schemas cost roughly 1,508 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/trustbeacon MCP server still maintained?

io.github.CloudCorpRecords/trustbeacon is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/trustbeacon MCP server under?

io.github.CloudCorpRecords/trustbeacon declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/trustbeacon MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/trustbeacon, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/trustbeacon: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/trustbeacon
- Repository: https://github.com/CloudCorpRecords/trustbeacon
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-trustbeacon/ghcr-io-cloudcorprecords-trustbeacon
