io.github.CloudCorpRecords/embedbase
NPM · @RENETURCIOS/EMBEDBASE · 2 COMPONENTS
Vector collections and document search backed by a Chroma HTTP service.
Available components
Last scanned (2 hours ago)
Scores higher than 31% of npm servers
Category Databases
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 836 tokens (~69/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "chroma_delete_collection" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 48
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 npm/@reneturcios/embedbase@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 | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
chroma_add_documents ~93
Add documents with optional metadata and ids to a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to add documents to. |
| documents | array | yes | Document texts to add to the collection. |
| ids | array | – | Ids for the documents, aligned by position with documents; generated when omitted. |
| metadatas | array | – | Metadata objects for each document, aligned by position with documents. |
No output schema declared.
No examples provided.
chroma_create_collection ~67
Create a new collection with optional metadata and embedding function.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to create. |
| embedding_function_name | string | – | Name of the embedding function to use for the collection. |
| metadata | object | – | Metadata to associate with the collection. |
No output schema declared.
No examples provided.
chroma_delete_collection ~33
Delete a collection and all of its records.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to delete. |
No output schema declared.
No examples provided.
chroma_delete_documents ~64
Delete documents from a collection by ids or filter.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to delete documents from. |
| ids | array | – | Ids of the documents to delete. |
| where | object | – | Metadata filter selecting which documents to delete. |
No output schema declared.
No examples provided.
chroma_get_collection_count ~37
Get the number of records stored in a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to count records in. |
No output schema declared.
No examples provided.
chroma_get_collection_info ~36
Get metadata and configuration details for a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to get information for. |
No output schema declared.
No examples provided.
chroma_get_documents ~116
Retrieve documents from a collection by ids or filter.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to retrieve documents from. |
| ids | array | – | Ids of the documents to retrieve. |
| include | array | – | Fields to include in the results, such as documents, metadatas, or embeddings. |
| limit | integer | – | Maximum number of documents to return. |
| offset | integer | – | Number of documents to skip before returning results. |
| where | object | – | Metadata filter selecting which documents to retrieve. |
No output schema declared.
No examples provided.
chroma_list_collections ~48
List collections in the database with optional pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of collections to return. |
| offset | integer | – | Number of collections to skip before returning results. |
No output schema declared.
No examples provided.
chroma_modify_collection ~62
Rename a collection or replace its metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to modify. |
| new_metadata | object | – | New metadata to replace the collection's existing metadata. |
| new_name | string | – | New name for the collection. |
No output schema declared.
No examples provided.
chroma_peek_collection ~48
Return a preview of documents stored in a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to preview. |
| limit | integer | – | Maximum number of documents to preview. |
No output schema declared.
No examples provided.
chroma_query_documents ~127
Query a collection for documents nearest to the given query texts.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection to query. |
| include | array | – | Fields to include in the results, such as documents, metadatas, embeddings, or distances. |
| n_results | integer | – | Maximum number of results to return for each query text. |
| query_texts | array | yes | Query texts to find the nearest documents for. |
| where | object | – | Metadata filter to apply to the query. |
| where_document | object | – | Document-content filter to apply to the query. |
No output schema declared.
No examples provided.
chroma_update_documents ~105
Update documents, metadata, or embeddings for existing ids in a collection.
| Name | Type | Req | Description |
|---|---|---|---|
| collection_name | string | yes | Name of the collection containing the documents to update. |
| documents | array | – | Replacement document texts, aligned by position with ids. |
| embeddings | array | – | Replacement embedding vectors, aligned by position with ids. |
| ids | array | yes | Ids of the documents to update. |
| metadatas | array | – | Replacement metadata objects, aligned by position with ids. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/embedbase MCP server?
io.github.CloudCorpRecords/embedbase runs locally as an npm package, launched with npx -y @reneturcios/embedbase. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/embedbase
claude mcp add cloudcorprecords-embedbase -- npx -y @reneturcios/embedbase
What is the io.github.CloudCorpRecords/embedbase MCP server?
io.github.CloudCorpRecords/embedbase is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/embedbase. Vector collections and document search backed by a Chroma HTTP service. This page covers its npm package (@reneturcios/embedbase).
Is the io.github.CloudCorpRecords/embedbase MCP server safe to use?
io.github.CloudCorpRecords/embedbase scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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/embedbase MCP server expose?
io.github.CloudCorpRecords/embedbase exposes 12 tools: chroma_list_collections, chroma_create_collection, chroma_peek_collection, chroma_get_collection_info, chroma_get_collection_count, and 7 more. Their descriptions and schemas cost roughly 836 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/embedbase MCP server still maintained?
io.github.CloudCorpRecords/embedbase 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/embedbase MCP server under?
io.github.CloudCorpRecords/embedbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.