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

Create a digital twin lens page, add knowledge to it, and poll its ingestion status.

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

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/twinlens`
- 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-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**: 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 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 465 tokens (~155/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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/twinlens MCP server?

io.github.CloudCorpRecords/twinlens runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/twinlens: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-twinlens -- docker run --rm -i ghcr.io/cloudcorprecords/twinlens:0.1.0 mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-twinlens": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/twinlens: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-05 (score 42, +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-03 (score 41, +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-02 (score 40)

First indexed and scored.

## MCP tools (3)

### `create_digital_twin_lens` (~330 tokens)

Create a digital twin lens — a public AI page that answers questions from the owner's own material, with citations — from a profile the user approved in the conversation. Etiquette: summarize the proposed profile and get the user's explicit confirmation before calling this tool, and only include information the user provided or confirmed in the conversation; never fill the profile with guesses. All fields are optional; send only what the user confirmed.

Input parameters:

- `accentColor` (string): Hex color like #4f46e5
- `audience` (string): Who the lens is meant to help
- `bio` (string): Short biography built from user-confirmed information
- `boundaries` (array): Things the lens should not claim or discuss
- `context` (string): Extra grounding context for how the lens should answer
- `displayName` (string): Public name shown on the lens
- `expertise` (array): Confirmed domains and skills
- `facts` (array): Standalone user-approved facts that seed the lens knowledge base
- `locale` (string): BCP-47 language tag for the lens copy, e.g. en or nl
- `sourceSummary` (string): What the assistant used to assemble the profile
- `suggestedPrompts` (array): Starter questions shown to visitors
- `tagline` (string): One-line summary of who the lens represents
- `tone` (string): Tone for the lens copy
- `topicName` (string): Name of the Mindola space that holds the seeded facts
- `vibeWords` (array): Short adjectives that describe the profile

### `add_lens_knowledge` (~77 tokens)

Add knowledge items to an unclaimed lens by its share token. Each item runs through the ingest pipeline in the background; poll get_lens_status for progress. Claimed lenses are rejected.

Input parameters:

- `items` (array, required): The knowledge items to add
- `lens_token` (string, required): The share token of an unclaimed lens

### `get_lens_status` (~58 tokens)

Report whether a lens is claimed and how knowledge ingestion is progressing for it, by its share token. Read-only; use it to poll after add_lens_knowledge.

Input parameters:

- `lens_token` (string, required): The share token of the lens

## Diagnostics

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

## Score history

- 2026-11-05: 42
- 2026-11-04: 41
- 2026-11-03: 41
- 2026-11-02: 40

## Common questions

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

io.github.CloudCorpRecords/twinlens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/twinlens. Create a digital twin lens page, add knowledge to it, and poll its ingestion status. This page covers its container image (ghcr.io/cloudcorprecords/twinlens).

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

io.github.CloudCorpRecords/twinlens scores 42 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/twinlens MCP server expose?

io.github.CloudCorpRecords/twinlens exposes 3 tools: create_digital_twin_lens, add_lens_knowledge, get_lens_status. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/twinlens 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 io.github.CloudCorpRecords/twinlens MCP server under?

io.github.CloudCorpRecords/twinlens 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/twinlens MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/twinlens, 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/twinlens: 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/twinlens
- Repository: https://github.com/CloudCorpRecords/twinlens
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-twinlens/ghcr-io-cloudcorprecords-twinlens.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-twinlens/ghcr-io-cloudcorprecords-twinlens/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-twinlens/ghcr-io-cloudcorprecords-twinlens.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-twinlens/ghcr-io-cloudcorprecords-twinlens