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.JoaoBerne/cli-bridge-mcp

PYPI · CLI-BRIDGE-MCP · SCANNED SEP 20

Other AI CLIs (Gemini, GPT, Claude, opencode, Ollama) as a council — ban-safe, no API keys.

Available components

0 this week 75 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 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 (Apache-2.0).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 632 tokens (~126/item across 5 items; 2 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability check failed: the tool surface changed between 0.1.5 and 0.3.0: 4 tool removals, 0 breaking changes, 0 additions. See how to fix → Fail
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.JoaoBerne/cli-bridge-mcp server?

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

pypi · cli-bridge-mcp

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

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.

  • 18 Sept 26 −3

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 13.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.

  • 13 Sept 26 +16
    • Malware scan: unverified → pass security
  • 12 Sept 26 −25
    • Malware scan: pass → unverified security
    • Stability: 0.80 → fail security
    • Schema quality: 1152 → 632 functional
    • Schema quality: excellent → good functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • Package version: 0.1.5 → 0.3.0 functional
  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
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/cli-bridge-mcp@0.3.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 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~134 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
doctor ~75

Health check: which CLIs are installed, which is the host, paid lanes, defaults, current cost profile. Pass deep=true to also probe each lane with a tiny live call (checks auth/quota — uses a bit of free quota; skips paid lanes).

NameTypeReqDescription
deepbooleanLive-probe each free lane's auth.

No output schema declared.

No examples provided.

setup ~59

Show the cost-profile choice (saver/balanced/max) to walk the user through configuring how cli-bridge spends paid credits/quota. Call this on first use if the profile isn't set, ASK the user, then tell them how to set it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.JoaoBerne/cli-bridge-mcp server?

io.github.JoaoBerne/cli-bridge-mcp is listed in the public MCP registry as io.github.JoaoBerne/cli-bridge-mcp. Other AI CLIs (Gemini, GPT, Claude, opencode, Ollama) as a council, ban-safe, no API keys. This page covers its PyPI package (cli-bridge-mcp).

Is the io.github.JoaoBerne/cli-bridge-mcp server safe to use?

io.github.JoaoBerne/cli-bridge-mcp scores 75 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.JoaoBerne/cli-bridge-mcp server expose?

io.github.JoaoBerne/cli-bridge-mcp exposes 2 tools: doctor, setup. Their descriptions and schemas cost roughly 134 tokens of context every time the server is loaded.

Is the io.github.JoaoBerne/cli-bridge-mcp server still maintained?

io.github.JoaoBerne/cli-bridge-mcp 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.

What licence is the io.github.JoaoBerne/cli-bridge-mcp server under?

io.github.JoaoBerne/cli-bridge-mcp 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.