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

com.mcparmory/launchdarkly

OCI · GHCR.IO/MCPARMORY/LAUNCHDARKLY:1.0.4 · 2 COMPONENTS · SCANNED AUG 3

Manage feature flags, segments, projects, environments, and team members

Available components

oci · ghcr.io/mcparmory/launchdarkly:1.0.4 6 pypi · mcparmory-launchdarkly 18
0 this week 6 Trust /100
Trust breakdown (6 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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • CVE data not yet available for this package.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency-health data not yet available.Unverified
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/mcparmory/launchdarkly:1.0.4

# add to Claude Code
claude mcp add com-mcparmory-launchdarkly -- docker run --rm -i ghcr.io/mcparmory/launchdarkly:1.0.4
# add to Codex CLI
codex mcp add com-mcparmory-launchdarkly -- docker run --rm -i ghcr.io/mcparmory/launchdarkly:1.0.4
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-launchdarkly": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/launchdarkly:1.0.4"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-launchdarkly:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/mcparmory/launchdarkly:1.0.4"]
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-launchdarkly": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/launchdarkly:1.0.4"
      ]
    }
  }
}
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.

  • 1 Aug 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +2
    • Provenance: unverified → fail ▼ security
    • License: unverified → fail ▼ functional
    • Maintenance: unverified → pass ▲ functional
  • 27 Jul 26 6

    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 3 Aug 2026 · Analysed oci/ghcr.io/mcparmory/launchdarkly:1.0.4

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.