CanopiiCanopiiAll serversEnterprise →

insights-mcp MCP Server Security Report

io.github.RedHatInsights/insights-mcp

Model Context Protocol server for Red Hat Lightspeed - advisor, image builder, inventory, and more

Security Trust Score
Grade A · Strong posture
Tier 1 · Public sourceHigh confidence · 98%latest v1.0.49+d7befcf8 Repository Publisher-verified
Declared MCP capabilities
ResourcesPrompts

Run it securely

Host io.github.RedHatInsights/insights-mcp in a governed environment — SSO in front, every tool call attributed and audited.

Are you the maintainer?

Verify with GitHub to get alerted whenever RedHatInsights/insights-mcp changes score — and claim the badge for your README.

Claim this server

The short answer

Is insights-mcp safe to use?
insights-mcp scores 90/100 (grade A) on the Canopii Trust Index — strong posture. It passes 16 of the 21 security controls that apply to it, with no confirmed security failures.
How reliable is the security score for insights-mcp?
We could evaluate 98% of the controls that apply to insights-mcp. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.
How was insights-mcp scored?
Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.
Reputation24stars38forks10open issues2d agolast commit1yage

Security controlslatest scored version v1.0.49+d7befcf8

Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    Tool Definition Integrityguardtool definitions stable; no risky changes in version history

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Application Security Checks

  • Warn
    No SSRF sinksguard1 occurrence

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

    src/insights_mcp/server.py:450

    Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

  • Warn
    No known-vulnerable dependencies1 of 202 runtime deps vulnerable; worst high

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

    [email protected] — GHSA-9xwg-3r6f-jcx2[email protected] — GHSA-gm37-52c6-37mw[email protected] — PYSEC-2026-3609[email protected] — PYSEC-2026-3654

    Fix: Upgrade the flagged dependencies past their fixed versions.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No path traversalguardno sinks found

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Dependencies pinned (lockfile)lockfile present

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseApache-2.0

    A clear license is required for legal enterprise use.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

  • N/A
    No install/post-install scriptsguardno published package

    install hooks run arbitrary code on every consumer at install time.

  • N/A
    Package name not typosquattingguardno published package

    Names mimicking popular packages are a common malware delivery vector.

  • N/A
    Published with provenanceno published package

    Build provenance attests the artifact was built from the claimed source by CI.

  • N/A
    Established maintainerno published package

    Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

  • Pass
    Execution Sandboxingcontainerized

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Embed this score

Add the live badge to your README — it updates automatically on every rescan.

Canopii Trust Score badge preview
markdown[![Canopii Trust Score](https://index.canopii.dev/api/badge/io.github.RedHatInsights/insights-mcp)](https://index.canopii.dev/server/io.github.RedHatInsights/insights-mcp)
html<a href="https://index.canopii.dev/server/io.github.RedHatInsights/insights-mcp"><img src="https://index.canopii.dev/api/badge/io.github.RedHatInsights/insights-mcp" alt="Canopii Trust Score" /></a>

Versions

VersionScoreStatus
v1.0.49+d7befcf8latest90Ascored
v1.0.46+2e72e60890Ascored
v1.0.40+ae6d60e590Ascored
v1.0.35+be1364ff90Ascored
v1.0.34+fe787c6c90Ascored
v1.0.29+53432d2990Ascored
v1.0.27+1eb0165b90Ascored
v1.0.25+20fa1c8e90Ascored
v1.0.23+d09d1fbe90Ascored
v1.0.22+1e95590e90Ascored
v1.0.17+12f0925d90Ascored
v1.0.16+0d75b17e90Ascored
v1.0.15+dd81bb4a90Ascored
v1.0.14+16e5d23290Ascored
v1.0.13+05c1435e90Ascored
v1.0.7+6cd7310990Ascored

Wondering how this compares? The MCP Security Index tracks grade distribution, committed secrets, and missing authentication across the whole ecosystem, refreshed monthly.