Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Couchbase-Ecosystem/couchbase-guru

PYPI · COUCHBASE-GURU · 2 COMPONENTS · SCANNED SEP 20

Search the Couchbase documentation from your MCP client via a hosted documentation agent.

+3 this week 81 Trust /100
Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 103 tokens (~103/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 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
  • 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Install

How do I install the io.github.Couchbase-Ecosystem/couchbase-guru MCP server?

io.github.Couchbase-Ecosystem/couchbase-guru runs locally as a PyPI package, launched with uvx couchbase-guru. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · couchbase-guru

# add to Claude Code
claude mcp add couchbase-ecosystem-couchbase-guru -- uvx couchbase-guru
// .cursor/mcp.json
{
  "mcpServers": {
    "couchbase-ecosystem-couchbase-guru": {
      "command": "uvx",
      "args": [
        "couchbase-guru"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "couchbase-ecosystem-couchbase-guru": {
      "command": "uvx",
      "args": [
        "couchbase-guru"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add couchbase-ecosystem-couchbase-guru -- uvx couchbase-guru
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "couchbase-ecosystem-couchbase-guru": {
      "type": "local",
      "command": [
        "uvx",
        "couchbase-guru"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add couchbase-ecosystem-couchbase-guru --command uvx --arg couchbase-guru
# ~/.hermes/config.yaml
mcp_servers:
  couchbase-ecosystem-couchbase-guru:
    command: "uvx"
    args: ["couchbase-guru"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "couchbase-ecosystem-couchbase-guru": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "couchbase-guru"
      ]
    }
  }
}
# add to Vellum
assistant mcp add couchbase-ecosystem-couchbase-guru -t stdio -c uvx -a couchbase-guru
// mcp.json
{
  "mcpServers": {
    "couchbase-ecosystem-couchbase-guru": {
      "command": "uvx",
      "args": [
        "couchbase-guru"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +4
    • Stability: unverified → 0.27 functional
Diagnostics

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 pypi/couchbase-guru@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 pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 23 packages
Packages resolved 23
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~103 tokens

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 →

Tool Tokens
ask_couchbase_docs ~103

Search Couchbase documentation to answer questions about any Couchbase product, feature, SDK, service, tutorials or examples. Use this tool for all Couchbase how-to, conceptual, and reference questions. Not for direct cluster operations.

NameTypeReqDescription
questionstringyesA complete, self-contained question about Couchbase products, SDKs, or services. Must include necessary context like product name, version, or programming language since the agent called by this tool…
NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.Couchbase-Ecosystem/couchbase-guru MCP server?

io.github.Couchbase-Ecosystem/couchbase-guru is an MCP server listed in the public MCP registry as io.github.Couchbase-Ecosystem/couchbase-guru. Search the Couchbase documentation from your MCP client via a hosted documentation agent. This page covers its PyPI package (couchbase-guru).

Is the io.github.Couchbase-Ecosystem/couchbase-guru MCP server safe to use?

io.github.Couchbase-Ecosystem/couchbase-guru scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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/couchbase-guru MCP server expose?

io.github.Couchbase-Ecosystem/couchbase-guru exposes 1 tool: ask_couchbase_docs. Their descriptions and schemas cost roughly 103 tokens of context every time the server is loaded.

Is the io.github.Couchbase-Ecosystem/couchbase-guru MCP server still maintained?

io.github.Couchbase-Ecosystem/couchbase-guru is still listed as active 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.