← Explore all mcp servers

SUPPLY-CHAIN EVIDENCE / SafeDep

SafeDep Pinner MCP

Resolve GitHub references and container tags to immutable identifiers for a dependency-pin review. The inspected handlers return lookup results; they do not edit files or verify signatures, provenance or vulnerability status.

“A Model Context Protocol (MCP) server that can help pin 3rd party dependencies to immutable digests.”

01 / THE REASONING

Why this made the selection.

  • Fills an immutable-identity lookup step complementary to vulnerability scanners: a workflow can record the exact action commit or container digest before testing a dependency change.
  • All registered tool handlers are small enough to inspect, and their credential-loading dependency is pinned in go.mod; file editing remains a separate host action.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md, LICENSE and main.go
  • tools/github.go and tools/docker.go in full
  • go.mod and Dockerfile
  • .vscode/mcp.json, .cursor/mcp.json, lefthook.yml and .github/workflows/container.yml
  • github.com/safedep/dry adapters/github.go at df91d0868e72d0032bf938ec43f2d8e9f6aa7a51
  • MCP transport/authorization documentation through Context7

Our findings

  • main.go registers exactly two tool providers and serves stdio. Their handlers register github_resolve_ref_to_sha, github_get_latest_pinned_version, github_get_versions, docker_resolve_image_to_digest and docker_get_image_versions.
  • GitHub handlers call GetCommit, GetLatestRelease and ListReleases and return text. Container handlers call ListTags or remote.Get and return tags/digests. None of those application handlers writes a workflow, Dockerfile or repository.
  • The exact safedep/dry dependency reads GITHUB_TOKEN, optional GITHUB_CLIENT_ID/GITHUB_CLIENT_SECRET and paired enterprise base/upload URL overrides. Client credentials take precedence over the token; no configured credentials falls back to an unauthenticated client. The server itself does not reduce credential scopes.
  • Container handlers use authn.DefaultKeychain for both tags and digest retrieval. This is ambient credential access, not evidence that a read-only token or a safe registry has been selected.
  • The build uses Go 1.24.1, downloads modules, builds a Linux binary with CGO disabled, installs CA certificates in an Alpine runtime and starts that binary. Base image digests are pinned in Dockerfile, but the runtime declares no non-root user.
  • The publisher's CI builds and pushes a mutable latest image on main/tag events. Its development client configs point to pinner-mcp:local; README client examples point to the registry image. No host directory or Docker socket mount is present in those inspected examples.
  • lefthook.yml contains developer pre-commit lint/secret checks and a pre-push test command, not a consumer installation hook. Those hooks and the release workflow were read, not executed.
  • Apache-2.0 licence conditions were inspected at the same source revision. No release-image bytes, dependency source archive or executable artifact is redistributed.

Not established by this review

  • No dependency download, Go compilation, container pull/build/start or host registration
  • No MCP initialize, tools/list or tool call
  • No GitHub/private-registry authentication or network-restriction test
  • No image-to-commit verification, signature/attestation verification, vulnerability scan or transitive dependency audit

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Read the publisher's container/stdio setup and the displayed source revision. The README's latest-image example is not a pinned binary receipt.
  2. Before any separately authorized installation, bind the chosen build or image bytes to the intended source revision and review its runtime user, egress and credential exposure.
  3. Configure a stdio-capable host only after that review. Do not pass unrelated tokens, a Docker socket or host mounts; none is required by the inspected client examples.
  4. Keep changes to workflow files or Dockerfiles outside this lookup server's scope and review them separately. This packet publishes no synthesized launch command or config.

Before you start

  • A stdio MCP host; publisher supplies VS Code/Copilot and Cursor examples
  • Container runtime for the documented image path, or the Go toolchain required by go.mod for a separately reviewed source build
  • Network access to the chosen GitHub API and container registries
  • Only narrowly authorized read credentials if private resources require them; public GitHub lookup can use the unauthenticated branch

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Publisher README ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/README.md

    Supports: Exact description, documented setup and mutable-image caveat

  2. Server entrypoint ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/main.go

    Supports: Tool-provider registration and stdio transport

  3. GitHub handlers ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/github.go

    Supports: Three tool names and read API calls

  4. Container handlers ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/docker.go

    Supports: Two tool names, DefaultKeychain, digest lookup and tag-order limitation

  5. https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/go.mod

    Supports: Go version and exact credential-adapter dependency pin

  6. https://github.com/safedep/dry/blob/df91d0868e72d0032bf938ec43f2d8e9f6aa7a51/adapters/github.go

    Supports: Token/client credential precedence, enterprise URLs and unauthenticated branch

  7. https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/Dockerfile

    Supports: Build/download steps, pinned base digests, CA installation and absent USER instruction

  8. https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.vscode/mcp.json

    Supports: Local image config and lack of host/socket mounts

  9. https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.cursor/mcp.json

    Supports: Separate host config with local image

  10. https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.github/workflows/container.yml

    Supports: Build/push lifecycle and mutable latest tag

  11. Developer hooks ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/lefthook.yml

    Supports: Developer hook commands distinguished from consumer setup

  12. Pinned licence ↗Checked

    https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/LICENSE

    Supports: Apache-2.0 redistribution conditions

Evidence & Ask