io.github.CloudCorpRecords/docbase
NPM · @RENETURCIOS/DOCBASE · 2 COMPONENTS
MongoDB tools: query, aggregate, index, and administer collections and databases.
Available components
Last scanned (21 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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1332 tokens (~60/item across 22 items; 22 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 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete-many" 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 22 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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 31 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 4 Nov 2026 · Analysed npm/@reneturcios/docbase@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 →
aggregate ~78
Run an aggregation pipeline against a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to run the aggregation pipeline against. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| pipeline | array | yes | Aggregation pipeline stages, each an object such as a $match or $group stage, applied in order. |
No output schema declared.
No examples provided.
collection-indexes ~46
List indexes for a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose indexes to list. |
| database | string | yes | Name of the MongoDB database containing the collection. |
No output schema declared.
No examples provided.
collection-schema ~46
Describe the schema for a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose schema to describe. |
| database | string | yes | Name of the MongoDB database containing the collection. |
No output schema declared.
No examples provided.
collection-storage-size ~49
Get the storage size of a collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose storage size to report. |
| database | string | yes | Name of the MongoDB database containing the collection. |
No output schema declared.
No examples provided.
connect ~46
Connect to a MongoDB instance
| Name | Type | Req | Description |
|---|---|---|---|
| connectionString | string | – | MongoDB connection string (mongodb:// or mongodb+srv://) to connect with; overrides the configured connection for this call. |
No output schema declared.
No examples provided.
count ~61
Count documents in a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose documents to count. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| query | object | – | Query filter document selecting the documents to count. |
No output schema declared.
No examples provided.
create-collection ~52
Create a new collection in a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the new collection to create. |
| database | string | yes | Name of the MongoDB database in which to create the collection. |
No output schema declared.
No examples provided.
create-index ~87
Create an index on a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to create the index on. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| keys | object | yes | Index keys document mapping each field to its index direction or type (for example 1, -1, or "text"); must name at least one field. |
No output schema declared.
No examples provided.
db-stats ~34
Get statistics for a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database whose statistics to return. |
No output schema declared.
No examples provided.
delete-many ~67
Delete documents from a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose documents to delete. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| filter | object | yes | Filter document selecting the documents to delete; all matching documents are deleted. |
No output schema declared.
No examples provided.
drop-collection ~47
Drop a collection from a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to drop. |
| database | string | yes | Name of the MongoDB database containing the collection. |
No output schema declared.
No examples provided.
drop-database ~30
Drop a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database to drop. |
No output schema declared.
No examples provided.
drop-index ~66
Drop an index from a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to drop the index from. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| indexName | string | yes | Name of the index to drop from the collection. |
No output schema declared.
No examples provided.
explain ~98
Get the execution plan for a MongoDB query
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection the explained operation runs against. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| method | array | – | Array naming the operation method to explain; the first entry is used and find is used when this is omitted. |
| methodArgs | object | – | Arguments document for the explained method, merged into the operation being explained. |
No output schema declared.
No examples provided.
export ~81
Export a MongoDB collection to a file
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to export. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| exportTitle | string | – | Title for the export; the collection name is used when this is omitted. |
| filter | object | – | Filter document selecting the documents to export. |
No output schema declared.
No examples provided.
find ~122
Run a find query against a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to query. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| filter | object | – | MongoDB query filter document matching the documents to return. |
| limit | number | – | Maximum number of documents to return; must be positive. |
| projection | object | – | Projection document controlling which fields are returned in each document. |
| sort | object | – | Sort document mapping each field to its sort direction (1 for ascending, -1 for descending). |
No output schema declared.
No examples provided.
insert-many ~65
Insert documents into a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection to insert the documents into. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| documents | array | yes | Documents to insert; a non-empty array of objects. |
No output schema declared.
No examples provided.
list-collections ~34
List collections in a MongoDB database
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | yes | Name of the MongoDB database whose collections to list. |
No output schema declared.
No examples provided.
list-databases ~20
List all databases in the connected MongoDB instance
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mongodb-logs ~54
Retrieve MongoDB log entries
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of log lines to return; must be positive. |
| type | string | – | Log type or component to retrieve; global is used when this is omitted. |
No output schema declared.
No examples provided.
rename-collection ~63
Rename a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Current name of the collection to rename. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| newName | string | yes | New name for the collection, within the same database. |
No output schema declared.
No examples provided.
update-many ~86
Update documents in a MongoDB collection
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Name of the collection whose documents to update. |
| database | string | yes | Name of the MongoDB database containing the collection. |
| filter | object | yes | Filter document selecting the documents to update. |
| update | object | yes | Update document to apply to the matching documents, for example using update operators such as $set. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/docbase MCP server?
io.github.CloudCorpRecords/docbase runs locally as an npm package, launched with npx -y @reneturcios/docbase. 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/docbase
claude mcp add cloudcorprecords-docbase -- npx -y @reneturcios/docbase
What is the io.github.CloudCorpRecords/docbase MCP server?
io.github.CloudCorpRecords/docbase is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/docbase. MongoDB tools: query, aggregate, index, and administer collections and databases. This page covers its npm package (@reneturcios/docbase).
Is the io.github.CloudCorpRecords/docbase MCP server safe to use?
io.github.CloudCorpRecords/docbase scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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/docbase MCP server expose?
io.github.CloudCorpRecords/docbase exposes 22 tools: connect, list-databases, list-collections, collection-schema, collection-indexes, and 17 more. Their descriptions and schemas cost roughly 1,332 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/docbase MCP server still maintained?
io.github.CloudCorpRecords/docbase is still listed as active in the MCP registry. We last reached this channel on 4 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/docbase MCP server under?
io.github.CloudCorpRecords/docbase declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.