io.github.Couchbase-Ecosystem/mcp-server-couchbase
OCI · DOCKER.IO/COUCHBASEECOSYSTEM/MCP-SERVER-COUCHBASE:0.8.0 · 2 COMPONENTS · SCANNED SEP 20
Couchbase Model Context Protocol Server to interact with Couchbase clusters
Deprecated
This server is marked deprecated in the MCP registry.
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 115 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1408 tokens (~70/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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.
How do I install the io.github.Couchbase-Ecosystem/mcp-server-couchbase server?
io.github.Couchbase-Ecosystem/mcp-server-couchbase runs locally as a container image, launched with docker run --rm -i docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.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 · docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0
claude mcp add couchbase-ecosystem-mcp-server-couchbase -- docker run --rm -i docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0
{
"mcpServers": {
"couchbase-ecosystem-mcp-server-couchbase": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"
]
}
}
} {
"servers": {
"couchbase-ecosystem-mcp-server-couchbase": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"
]
}
}
} codex mcp add couchbase-ecosystem-mcp-server-couchbase -- docker run --rm -i docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"couchbase-ecosystem-mcp-server-couchbase": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"
],
"enabled": true
}
}
} mcp_servers:
couchbase-ecosystem-mcp-server-couchbase:
command: "docker"
args: ["run", "--rm", "-i", "docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"] {
"McpServers": {
"couchbase-ecosystem-mcp-server-couchbase": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"
]
}
}
} {
"mcpServers": {
"couchbase-ecosystem-mcp-server-couchbase": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed oci/docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.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 →
explain_sql_plus_plus_query ~88
Generate and evaluate an EXPLAIN plan for a SQL++ query. It provides information about the execution plan for the query. The EXPLAIN statement is run in the specified scope in the specified bucket. It returns query metadata along with an extracted plan and plan evaluation.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| query | string | yes | – |
| scope_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_buckets_in_cluster ~23
Get the names of all the accessible buckets in the cluster.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_cluster_health_and_services ~122
Get cluster health status and list of all running services. This tool provides health monitoring by: - Getting health status of all running services with latency information (via ping) - Listing all services running on the cluster with their endpoints - Showing connection status and node information for each service If bucket_name is provided, it actively pings services from the perspective of the bucket. Otherwise, it uses cluster-level ping to get the health status of the cluster. Returns: - Cluster health status with service-level connection details and latency measurements
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_collections_in_scope ~40
Get the names of all collections in the given scope and bucket.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| scope_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_document_by_id ~68
Get a document by its ID from the specified scope and collection. If the document is not found, it will raise an exception.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| collection_name | string | yes | – |
| document_id | string | yes | – |
| scope_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_index_advisor_recommendations ~169
Get index recommendations from Couchbase Index Advisor for a given SQL++ query. The Index Advisor analyzes the query and provides recommendations for optimal indexes. This tool works with SELECT, UPDATE, DELETE, or MERGE queries. The queries will be run on the specified scope in the specified bucket. Returns a dictionary with: - current_used_indexes: Array of currently used indexes (if any) - recommended_indexes: Array of recommended secondary indexes (if any) - recommended_covering_indexes: Array of recommended covering indexes (if any) Each index object contains: - index: The CREATE INDEX SQL++ command - statements: Array of statement objects with the query and run count
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| query | string | yes | – |
| scope_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_longest_running_queries ~42
Get the N longest running queries from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_most_frequent_queries ~43
Get the N most frequent queries from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_queries_not_selective ~43
Get queries that are not very selective from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_queries_not_using_covering_index ~46
Get queries that don't use a covering index from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_queries_using_primary_index ~43
Get queries that use a primary index from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_queries_with_large_result_count ~44
Get queries with the largest result counts from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_queries_with_largest_response_sizes ~45
Get queries with the largest response sizes from the system:completed_requests catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of queries to return (default: 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_schema_for_collection ~67
Get the schema for a collection in the specified scope. Returns a dictionary with the collection name and the schema returned by running INFER query on the Couchbase collection.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| collection_name | string | yes | – |
| scope_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_scopes_and_collections_in_bucket ~50
Get the names of all scopes and collections in the bucket. Returns a dictionary with scope names as keys and lists of collection names as values.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_scopes_in_bucket ~30
Get the names of all scopes in the given bucket.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_server_configuration_status ~37
Get the server status and configuration without establishing connection. This tool can be used to verify if the server is running and check the configuration.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_indexes ~205
List indexes in the cluster with optional filtering by bucket, scope, collection, and index name. Filters must be provided hierarchically: scope requires bucket, collection requires both, index requires all three. Set ``return_raw_index_stats=True`` to get the unprocessed source row for each index. Each result contains: name, definition (CREATE INDEX statement), status, isPrimary, bucket, scope, collection, lastScanTime. If a required field is missing, the entry contains warning and raw_index_stats instead. Source depends on cluster version: v8+ queries ``system:indexes`` via the query service (RBAC-scoped — the connected user sees only indexes on keyspaces they can access); older clusters fall back to the admin-level Index Service REST API ``/getIndexStatus``.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | – | – | – |
| collection_name | – | – | – |
| index_name | – | – | – |
| return_raw_index_stats | boolean | – | – |
| scope_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
run_sql_plus_plus_query ~121
Run a SQL++ query on a scope and return the results as a list of JSON objects. The query will be run on the specified scope in the specified bucket. The query should use collection names directly without bucket/scope prefixes, as the scope context is automatically set. Example: query = "SELECT * FROM users WHERE age > 18" # Incorrect: "SELECT * FROM bucket.scope.users WHERE age > 18"
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | string | yes | – |
| query | string | yes | – |
| scope_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
test_cluster_connection ~82
Test the connection to Couchbase cluster and optionally to a bucket. This tool verifies the connection to the Couchbase cluster and bucket by establishing the connection if it is not already established. If bucket name is not provided, it will not try to connect to the bucket specified in the MCP server settings. Returns connection status and basic cluster information.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket_name | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.Couchbase-Ecosystem/mcp-server-couchbase server?
io.github.Couchbase-Ecosystem/mcp-server-couchbase is listed in the public MCP registry as io.github.Couchbase-Ecosystem/mcp-server-couchbase. Couchbase Model Context Protocol Server to interact with Couchbase clusters. This page covers its container image (docker.io/couchbaseecosystem/mcp-server-couchbase:0.8.0).
Is the io.github.Couchbase-Ecosystem/mcp-server-couchbase server safe to use?
io.github.Couchbase-Ecosystem/mcp-server-couchbase scores 46 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.Couchbase-Ecosystem/mcp-server-couchbase server expose?
io.github.Couchbase-Ecosystem/mcp-server-couchbase exposes 20 tools: get_buckets_in_cluster, get_server_configuration_status, test_cluster_connection, get_scopes_and_collections_in_bucket, get_collections_in_scope, and 15 more. Their descriptions and schemas cost roughly 1,408 tokens of context every time the server is loaded.
Is the io.github.Couchbase-Ecosystem/mcp-server-couchbase server still maintained?
io.github.Couchbase-Ecosystem/mcp-server-couchbase is marked deprecated in the MCP registry. We last reached this channel on 20 September 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.Couchbase-Ecosystem/mcp-server-couchbase server under?
io.github.Couchbase-Ecosystem/mcp-server-couchbase declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.