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.

CyanMycelium MCP Broker

NPM · @CYANMYCELIUM/MCP-BROKER

One host and one port for many MCP servers: browsers, devices, simulators and stdio tools.

0 this week 78 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of npm servers

Category Cloud Infrastructure

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 Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 5 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pandaGaume/mcp-broker). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).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 Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 362 tokens (~72/item across 5 items; 5 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

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.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 18 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 17 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 15 Nov 26 78

    First indexed and scored.

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 22 Nov 2026 · Analysed npm/@cyanmycelium/mcp-broker@1.12.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pandaGaume/mcp-broker
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pandaGaume/mcp-broker/.github/workflows/release-node.yml@refs/tags/node-v1.12.0
Rekor log index 3897123538
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:cead7d693ff58562874ab514e4867b136aa9c0e11dbb529728adae28f0feae43a7d572b1892e98e575597eefd376e4de12d7f0876cbdf3d69f6aedc57

Background: How many MCP packages publish verified provenance →

Dependencies 24 packages
Packages resolved 24
Stale 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~362 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
_broker-broker_diagnose ~92

[_broker] Returns the broker's live state plus the problems it can detect about its own wiring, each with the symptom, the evidence, and a concrete fix. Call this first when something does not work: it correlates the counters for you and names the cause.

NameTypeReqDescription
slotstring–Narrow the report to one provider slot (case-sensitive). Omit to diagnose the whole broker.

No output schema declared.

No examples provided.

_broker-broker_guide ~118

[_broker] Returns the broker's own integration documentation as Markdown: how to publish a provider, how to reach a slot as a client, how to configure an MCP host, how to deploy, and a symptom-to-fix troubleshooting page. Read this instead of looking for a README. Call with no argument for the index.

NameTypeReqDescription
topicstring–Which page to return: index, publish-provider, connect-client, host-config, deploy, or troubleshooting. Omit for the index, which says which page to read next.

No output schema declared.

No examples provided.

_broker-broker_info ~36

[_broker] Returns the broker's name, version, uptime, host, port, TLS status, and configured URL paths.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

_broker-provider_status ~45

[_broker] Returns the status of one provider slot identified by name. Errors if the slot does not exist.

NameTypeReqDescription
namestringyesExact provider name (case-sensitive).

No output schema declared.

No examples provided.

_broker-providers_list ~71

[_broker] Returns every provider slot known to the broker (connected and disconnected), with transport kind, `_all` membership, when the provider attached, client count, and pending request count. The counts are the slot's callers, not the provider: a connected provider nobody is calling reads all zeros.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the CyanMycelium MCP Broker server?

CyanMycelium MCP Broker runs locally as an npm package, launched with npx -y @cyanmycelium/mcp-broker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @cyanmycelium/mcp-broker

# add to Claude Code
claude mcp add pandagaume-mcp-broker -- npx -y @cyanmycelium/mcp-broker
Common questions

What is the CyanMycelium MCP Broker server?

CyanMycelium MCP Broker is listed in the public MCP registry as io.github.pandaGaume/mcp-broker. One host and one port for many MCP servers: browsers, devices, simulators and stdio tools. This page covers its npm package (@cyanmycelium/mcp-broker).

Is the CyanMycelium MCP Broker server safe to use?

CyanMycelium MCP Broker scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 CyanMycelium MCP Broker server expose?

CyanMycelium MCP Broker exposes 5 tools: _broker-broker_info, _broker-providers_list, _broker-provider_status, _broker-broker_guide, _broker-broker_diagnose. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.

Is the CyanMycelium MCP Broker server still maintained?

CyanMycelium MCP Broker is still listed as active in the MCP registry. We last reached this channel on 22 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 CyanMycelium MCP Broker server under?

CyanMycelium MCP Broker 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.

What did VerifyMCP test on the CyanMycelium MCP Broker server?

VerifyMCP ran 15 checks on CyanMycelium MCP Broker, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about CyanMycelium MCP Broker: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.