io.github.CloudCorpRecords/chatvault
OCI · GHCR.IO/CLOUDCORPRECORDS/CHATVAULT · 2 COMPONENTS
Search and read your local AI chat-history corpus: full-text search, transcripts, inventory.
Available components
Last scanned (1 hour ago)
Scores higher than 47% of OCI servers
Category Memory and Knowledge
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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 625 tokens (~69/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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 9 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 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.
- 4 Nov 26 41
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/chatvault@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 →
conversation_inventory ~101
Paginated, read-only inventory of every conversation as compact metadata: id, platform, title, and a versioned content fingerprint. Call with no arguments to start a scan, then pass each page's nextCursor back as cursor until a page comes back without one. Pages hold up to 100 items.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | An opaque scan cursor from a previous page's nextCursor |
| limit | integer | – | Page size, at most 100 |
No output schema declared.
No examples provided.
corpus_status ~22
Report when the corpus last received data and how many conversations it holds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_conversation ~51
Fetch the full transcript of one conversation by its id (the id field from search results). The response carries contentFingerprint, the current fingerprint of the returned transcript.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The conversation id |
No output schema declared.
No examples provided.
get_conversation_image ~80
Read a retained local raster image using the message and image index returned by get_conversation. No private provider URL fetching or OCR.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | The conversation id from search results |
| image_index | integer | yes | Index of the image within the message |
| message_index | integer | yes | Index of the message within the conversation |
No output schema declared.
No examples provided.
list_conversations ~48
List conversations by chronology, including oldest-first for questions about the user's earliest chat.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of conversations to return |
| order | string | – | Chronology direction |
No output schema declared.
No examples provided.
list_recent ~35
List the most recently updated conversations with title, summary, and platform.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of conversations to return |
No output schema declared.
No examples provided.
save_conversation ~83
Add or update a conversation in the corpus, so MCP is also an ingestion route.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Stable conversation id; omit to have one assigned |
| messages | array | yes | The conversation messages in order |
| platform | string | yes | The platform the conversation came from, e.g. claude |
| title | string | yes | The conversation title |
No output schema declared.
No examples provided.
save_memory ~49
Record a durable fact (a decision, preference, or correction) worth carrying into later chats. Stored turned off until the user reviews and enables it.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The fact to record |
No output schema declared.
No examples provided.
search_conversations ~156
Full-text search across every past conversation. Returns ranked matches with highlighted snippets. Supports platform, title, date_from/date_to filters and a match_mode (any / all / phrase).
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Only conversations updated on or after this date (ISO 8601) |
| date_to | string | – | Only conversations updated on or before this date (ISO 8601) |
| match_mode | string | – | How query terms combine: any, all, or phrase |
| platform | string | – | Restrict to one platform, e.g. claude or chatgpt |
| query | string | yes | The full-text search query |
| title | string | – | Restrict to conversations whose title contains this text |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/chatvault MCP server?
io.github.CloudCorpRecords/chatvault runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/chatvault: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/chatvault
claude mcp add cloudcorprecords-chatvault -- docker run --rm -i ghcr.io/cloudcorprecords/chatvault:0.1.0
What is the io.github.CloudCorpRecords/chatvault MCP server?
io.github.CloudCorpRecords/chatvault is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/chatvault. Search and read your local AI chat-history corpus: full-text search, transcripts, inventory. This page covers its container image (ghcr.io/cloudcorprecords/chatvault).
Is the io.github.CloudCorpRecords/chatvault MCP server safe to use?
io.github.CloudCorpRecords/chatvault scores 41 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/chatvault MCP server expose?
io.github.CloudCorpRecords/chatvault exposes 9 tools: search_conversations, get_conversation_image, get_conversation, list_conversations, list_recent, and 4 more. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/chatvault MCP server still maintained?
io.github.CloudCorpRecords/chatvault 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/chatvault MCP server under?
io.github.CloudCorpRecords/chatvault declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.