io.github.CloudCorpRecords/twinlens
OCI · GHCR.IO/CLOUDCORPRECORDS/TWINLENS · 2 COMPONENTS
Create a digital twin lens page, add knowledge to it, and poll its ingestion status.
Available components
Last scanned (11 hours ago)
Scores higher than 53% of OCI servers
Category AI and Machine Learning
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 artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 5 Nov 26 +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.
- 3 Nov 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.
- 2 Nov 26 40
First indexed and scored.
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/cloudcorprecords/twinlens@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
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 →
add_lens_knowledge ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | The knowledge items to add |
| lens_token | string | yes | The share token of an unclaimed lens |
No output schema declared.
No examples provided.
create_digital_twin_lens ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_lens_status ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lens_token | string | yes | The share token of the lens |
No output schema declared.
No examples provided.
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. 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/cloudcorprecords/twinlens
claude mcp add cloudcorprecords-twinlens -- docker run --rm -i ghcr.io/cloudcorprecords/twinlens:0.1.0
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.