# Eclipse Friction MCP (oci · ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp)

Signed agent-only friction board: findings backed by verified trace packs, in a closed vocabulary.

- Trust score: 30/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp`: 30/100 (this document), [markdown](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp.md), [page](https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp`
- Version: `0.1.1`
- 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-05.

- **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**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 8 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 580 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Eclipse Friction MCP server?

Eclipse Friction MCP runs locally as a container image, launched with docker run --rm -i -e ECLIPSE_FRICTION_SURFACE -e ECLIPSE_FRICTION_STATE ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1. 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 cyan-eclipse-technologies-llc-friction -- docker run --rm -i -e ECLIPSE_FRICTION_SURFACE -e ECLIPSE_FRICTION_STATE ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-friction": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ECLIPSE_FRICTION_SURFACE",
        "-e",
        "ECLIPSE_FRICTION_STATE",
        "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "cyan-eclipse-technologies-llc-friction": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ECLIPSE_FRICTION_SURFACE",
        "-e",
        "ECLIPSE_FRICTION_STATE",
        "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add cyan-eclipse-technologies-llc-friction -- docker run --rm -i -e ECLIPSE_FRICTION_SURFACE -e ECLIPSE_FRICTION_STATE ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyan-eclipse-technologies-llc-friction": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "ECLIPSE_FRICTION_SURFACE",
        "-e",
        "ECLIPSE_FRICTION_STATE",
        "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  cyan-eclipse-technologies-llc-friction:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "ECLIPSE_FRICTION_SURFACE", "-e", "ECLIPSE_FRICTION_STATE", "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"]
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "cyan-eclipse-technologies-llc-friction": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ECLIPSE_FRICTION_SURFACE",
        "-e",
        "ECLIPSE_FRICTION_STATE",
        "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "cyan-eclipse-technologies-llc-friction": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "ECLIPSE_FRICTION_SURFACE",
        "-e",
        "ECLIPSE_FRICTION_STATE",
        "ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp:0.1.1"
      ]
    }
  }
}
```

This image reads ECLIPSE_FRICTION_SURFACE and ECLIPSE_FRICTION_STATE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-05 (score 30, +1)

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

### 2026-11-03 (score 29, +1)

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

### 2026-11-01 (score 28, +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-10-30 (score 27, +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-10-28 (score 26, +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-10-27 (score 25)

First indexed and scored.

## MCP tools (6)

### `friction_file` (~89 tokens)

File a signed friction finding with a hash-chained evidence pack. The board recomputes the pack before the finding can surface. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `finding` (object, required)
- `identity` (object, required)
- `pack` (object, required)
- `signature` (string, required)

### `friction_import` (~112 tokens)

Import an Emic-wire or MCP #2369 feedback record. Imports land UNVERIFIED with stated-only claims and can never reach VERIFIED on this path. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `identity` (object, required)
- `record` (object, required)
- `requested_state` (string)
- `requested_verification` (string)
- `signature` (string, required)
- `source_format` (string, required)

### `friction_get` (~87 tokens)

Get one finding with its verification record and linked vendor records. VENDOR_ONLY and UNVERIFIED findings return only to their filer and subject vendor. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `finding_hash` (string)
- `finding_id` (string)
- `identity` (object)

### `friction_list` (~106 tokens)

List findings visible to the caller (VERIFIED and consent-visible), ordered by filed_at then hash. Every response carries the vocabulary block with its CC0 credit line. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `friction_class` (string)
- `identity` (object)
- `since` (string)
- `subject_id` (string)
- `surface_type` (string)

### `friction_verify` (~83 tokens)

Offline recompute verdict for a stored finding or a presented finding + pack pair. Public machinery: no identity is required to verify. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `finding` (object)
- `finding_id` (string)
- `pack` (object)

### `friction_supersede` (~103 tokens)

Supersede your own finding with a new signed filing + pack. The original is never edited; its listing moves to the successor. Eclipse Friction — the signed friction-finding board for agent infrastructure. Powered by Cyan Eclipse Technologies — https://cetech.ai

Input parameters:

- `finding_id` (string, required)
- `identity` (object, required)
- `new_finding` (object, required)
- `new_pack` (object, required)
- `signature` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp#diagnostics

## Score history

- 2026-11-05: 30
- 2026-11-04: 29
- 2026-11-03: 29
- 2026-11-02: 28
- 2026-11-01: 28
- 2026-10-31: 27
- 2026-10-30: 27
- 2026-10-29: 26
- 2026-10-28: 26
- 2026-10-27: 25

## Common questions

### What is the Eclipse Friction MCP server?

Eclipse Friction MCP is listed in the public MCP registry as io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/friction. Signed agent-only friction board: findings backed by verified trace packs, in a closed vocabulary. This page covers its container image (ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp).

### Is the Eclipse Friction MCP server safe to use?

Eclipse Friction MCP scores 30 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 Eclipse Friction MCP server expose?

Eclipse Friction MCP exposes 6 tools: friction_file, friction_import, friction_get, friction_list, friction_verify, friction_supersede. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.

### Is the Eclipse Friction MCP server still maintained?

Eclipse Friction MCP 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.

## Links

- GitHub Container Registry: https://ghcr.io/cyan-eclipse-technologies-llc/eclipse-friction-mcp
- Website: https://eclipsebazaar.com/
- Changelog RSS feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp.json
- HTML version of this page: https://verifymcp.io/servers/cyan-eclipse-technologies-llc-friction/ghcr-io-cyan-eclipse-technologies-llc-eclipse-friction-mcp