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.

Logo.dev MCP

OCI · GHCR.IO/PVLIESDONK/LOGODEV-MCP:V1.1.0 · 2 COMPONENTS

Look up company logos and brand data via the logo.dev API.

Available components

oci · ghcr.io/pvliesdonk/logodev-mcp:v1.1.0 0 pypi · logodev-mcp 34
0 this week 0 Trust /100

Last scanned (10 hours ago)

Scores higher than 0% of OCI servers

Category Design and Media

Recent critical change

CVE-2026-75803 affects this package (5 Nov 2026). See the changelog before you install this server.

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pvliesdonk/logodev-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 129 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

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.

  • 5 Nov 26 0
    • CVE-2026-75803 affects this package: none ▼ critical
    • CVE-2026-57433 affects this package: none ▼ critical
    • CVE-2026-63073 affects this package: none ▼ critical
    • CVE-2026-8924 affects this package: none ▼ critical
    • CVE-2026-8927 affects this package: none ▼ critical
    • CVE-2026-13221 affects this package: none ▼ critical
    • CVE-2026-111497 affects this package: none ▼ critical
    • CVE-2026-5450 affects this package: none ▼ critical
    • CVE-2026-42496 affects this package: none ▼ critical
    • CVE-2026-12087 affects this package: none ▼ critical
    • CVE-2026-8376 affects this package: none ▼ critical
  • 4 Nov 26 0
    • CVE-2026-12087 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-111497 affects this package: high ▼ critical
  • 3 Nov 26 0
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-111497 affects this package: high ▼ critical
    • CVE-2026-12087 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
  • 2 Nov 26 0
    • CVE-2026-12087 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
    • CVE-2026-111497 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
  • 1 Nov 26 0
    • CVE-2026-111497 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-12087 affects this package: high ▼ critical
  • 31 Oct 26 0
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-111497 affects this package: high ▼ critical
    • CVE-2026-12087 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
  • 30 Oct 26 0
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-96760 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-111497 affects this package: high ▼ critical
    • CVE-2026-12087 affects this package: high ▼ critical
  • 29 Oct 26 0
    • CVE-2026-8376 affects this package: high ▼ critical
    • CVE-2026-57433 affects this package: high ▼ critical
    • CVE-2026-96760 affects this package: high ▼ critical
    • CVE-2026-42496 affects this package: high ▼ critical
    • CVE-2026-8927 affects this package: high ▼ critical
    • CVE-2026-8924 affects this package: high ▼ critical
    • CVE-2026-12087 affects this package: high ▼ critical
    • CVE-2026-75803 affects this package: high ▼ critical
    • CVE-2026-5450 affects this package: high ▼ critical
    • CVE-2026-13221 affects this package: high ▼ critical
    • CVE-2026-63073 affects this package: high ▼ critical
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 5 Nov 2026 · Analysed oci/ghcr.io/pvliesdonk/logodev-mcp:v1.1.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 oci
Reason Verified
Discovered via OCI referrers API
Source repo pvliesdonk/logodev-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pvliesdonk/logodev-mcp/.github/workflows/release.yml@refs/heads/main
Rekor log index 1991051563
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:dbce35608a9f6454c8a40aedea8d76d15c2d1aaaee53b5323c87b84fc1239b60

Background: How many MCP packages publish verified provenance →

Vulnerabilities 272 findings
ID CVE Severity Vector Fix available
DEBIAN-CVE-2011-3374 CVE-2011-3374 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-109518 CVE-2026-109518 none yes
DEBIAN-CVE-2022-0563 CVE-2022-0563 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2025-14104 CVE-2025-14104 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H yes
DEBIAN-CVE-2026-13595 CVE-2026-13595 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H yes
DEBIAN-CVE-2026-27456 CVE-2026-27456 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N yes
DEBIAN-CVE-2026-3184 CVE-2026-3184 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-53612 CVE-2026-53612 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H yes
DEBIAN-CVE-2026-53613 CVE-2026-53613 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H yes
DEBIAN-CVE-2026-53614 CVE-2026-53614 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H yes
DEBIAN-CVE-2026-53615 CVE-2026-53615 high CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H yes
DEBIAN-CVE-2026-76642 CVE-2026-76642 none no
DEBIAN-CVE-2026-78408 CVE-2026-78408 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H no
DEBIAN-CVE-2026-78409 CVE-2026-78409 high CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2026-78410 CVE-2026-78410 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2017-18018 CVE-2017-18018 medium CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N no
DEBIAN-CVE-2025-5278 CVE-2025-5278 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L no
DEBIAN-CVE-2026-56391 CVE-2026-56391 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H no
DEBIAN-CVE-2026-56392 CVE-2026-56392 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H no
DEBIAN-CVE-2026-102473 CVE-2026-102473 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-102474 CVE-2026-102474 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N no
DEBIAN-CVE-2026-53910 CVE-2026-53910 none no
GHSA-45c3-73f7-pv4m CVE-2026-114605 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-7xgj-8392-5q4r medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
DEBIAN-CVE-2026-102010 CVE-2026-102010 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H no
DEBIAN-CVE-2026-114690 CVE-2026-114690 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-114691 CVE-2026-114691 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-115455 CVE-2026-115455 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H no
DEBIAN-CVE-2026-95619 CVE-2026-95619 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H no
DEBIAN-CVE-2018-1000021 CVE-2018-1000021 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2022-24975 CVE-2022-24975 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N no
DEBIAN-CVE-2024-52005 CVE-2024-52005 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2026-41991 CVE-2026-41991 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
DEBIAN-CVE-2026-41992 CVE-2026-41992 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-9pg5-8c7x-5hfx CVE-2026-119284 medium yes
GHSA-jpxq-7h8p-2q76 CVE-2026-119283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
DEBIAN-CVE-2026-54369 CVE-2026-54369 none no
DEBIAN-CVE-2026-54370 CVE-2026-54370 none no
DEBIAN-CVE-2026-54371 CVE-2026-54371 none no
DEBIAN-CVE-2026-111497 CVE-2026-111497 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
DEBIAN-CVE-2026-42250 CVE-2026-42250 none no
DEBIAN-CVE-2010-4756 CVE-2010-4756 none no
DEBIAN-CVE-2018-20796 CVE-2018-20796 high CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2019-1010022 CVE-2019-1010022 critical CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2019-1010023 CVE-2019-1010023 high CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H no
DEBIAN-CVE-2019-1010024 CVE-2019-1010024 medium CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N no
DEBIAN-CVE-2019-1010025 CVE-2019-1010025 medium CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N no
DEBIAN-CVE-2019-9192 CVE-2019-9192 high CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H no
DEBIAN-CVE-2026-18374 CVE-2026-18374 medium CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L no
DEBIAN-CVE-2026-19499 CVE-2026-19499 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H no

Showing 50 of 272 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

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. 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 →

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

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/pvliesdonk/logodev-mcp:v1.1.0

# install command
$ docker pull ghcr.io/pvliesdonk/logodev-mcp:v1.1.0
Common questions

What is the Logo.dev MCP server?

Logo.dev MCP is listed in the public MCP registry as io.github.pvliesdonk/logodev-mcp. Look up company logos and brand data via the logo.dev API. This page covers its container image (ghcr.io/pvliesdonk/logodev-mcp:v1.1.0).

Is the Logo.dev MCP server still maintained?

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

Logo.dev MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.