---
title: "SafeDep Pinner MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/safedep-pinner-mcp/
description: "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."
---

# SafeDep Pinner MCP: review, setup & limitations · Undominated.ai

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

[← Explore all mcp servers](/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.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/safedep/pinner-mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 12 linked sources
 Publisher SafeDep
 Licence [Apache-2.0 ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/LICENSE)
 Revision 095b2c028568
 [Read what was—and wasn’t—checked ↓](#review)

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

 [SafeDep · upstream description ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/README.md) Our analysis follows below.

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.

### A good fit for

 - A proposed GitHub Actions and container pin manifest with human review
- Reproducibility evidence for the harness or image used in an inference/evaluation run

### Weigh up before choosing

 - A digest or commit identifies content; it is not a signature, attestation, SBOM, vulnerability verdict or proof the content is safe.
- The Docker version handler reverses the registry tag list and truncates it. It does not sort semantically or establish that the first result is the newest release.
- Container references are caller-controlled and no registry allowlist appears in the handlers. Docker authentication uses DefaultKeychain; restrict available credentials and egress outside the server.
- The README uses a mutable latest image. Its relationship to the reviewed commit, image signatures and packaged bytes was not verified; no installation command or config is promoted by this packet.
- The Dockerfile has no USER instruction. Source-level read handlers do not constitute a least-privilege container or a sandbox certification.

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 ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/README.md)
 - Read the publisher's container/stdio setup and the displayed source revision. The README's latest-image example is not a pinned binary receipt.
- 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.
- 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.
- 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

### Compatibility

MCP stdio clients · VS Code with GitHub Copilot · Cursor

### Implementation

Go

### Transports

stdio

### Network lookups with optional ambient credentials

 - Read GitHub repository commit/release metadata under the selected credential or unauthenticated client
- Read selected container-registry tags/manifests using the process-visible Docker keychain
- Caller-selected repository/image inputs and enterprise URL overrides require host-level egress and credential controls
- No file-writing tool in the inspected handlers; any host editor, registry credential helper or transitive-library behavior is a separate boundary

### Cost model

Apache-licensed source. Registry/API limits and host/container operating costs are separate; no paid plan or free-service guarantee was verified.

04 / FOLLOW THE EVIDENCE

## The source trail.

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

 - [Publisher README ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/README.md) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/README.md Supports: Exact description, documented setup and mutable-image caveat
- [Server entrypoint ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/main.go) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/main.go Supports: Tool-provider registration and stdio transport
- [GitHub handlers ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/github.go) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/github.go Supports: Three tool names and read API calls
- [Container handlers ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/docker.go) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/tools/docker.go Supports: Two tool names, DefaultKeychain, digest lookup and tag-order limitation
- [Module and toolchain requirements ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/go.mod) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/go.mod Supports: Go version and exact credential-adapter dependency pin
- [Pinned dependency credential adapter ↗](https://github.com/safedep/dry/blob/df91d0868e72d0032bf938ec43f2d8e9f6aa7a51/adapters/github.go) Checked 2026-10-14 https://github.com/safedep/dry/blob/df91d0868e72d0032bf938ec43f2d8e9f6aa7a51/adapters/github.go Supports: Token/client credential precedence, enterprise URLs and unauthenticated branch
- [Container build boundary ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/Dockerfile) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/Dockerfile Supports: Build/download steps, pinned base digests, CA installation and absent USER instruction
- [VS Code development configuration ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.vscode/mcp.json) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.vscode/mcp.json Supports: Local image config and lack of host/socket mounts
- [Cursor development configuration ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.cursor/mcp.json) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.cursor/mcp.json Supports: Separate host config with local image
- [Container release workflow ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.github/workflows/container.yml) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/.github/workflows/container.yml Supports: Build/push lifecycle and mutable latest tag
- [Developer hooks ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/lefthook.yml) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/lefthook.yml Supports: Developer hook commands distinguished from consumer setup
- [Pinned licence ↗](https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/LICENSE) Checked 2026-10-14 https://github.com/safedep/pinner-mcp/blob/095b2c0285684f54efae7dd9ae32e23c9a32665a/LICENSE Supports: Apache-2.0 redistribution conditions

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### AWS Labs Finch ↗ Builds and pushes container images through the local Finch CLI, with additional ECR repository support.](/mcp-servers/awslabs-finch/)[### MinIO AIStor MCP Server ↗ MinIO's MCP server for AIStor object stores lists buckets and objects, reads metadata and tags, issues presigned URLs and answers questions about object contents. It runs as a container image from MinIO's Quay registry, starts read-only, and needs --allow-write, --allow-delete or --allow-admin for the rest. The repository is archived and holds no source or licence file.](/mcp-servers/minio-aistor/)[### Socket MCP Server ↗ Exposes Socket supply-chain analysis so an assistant can check packages for vulnerabilities and suspicious behavior. It supports both local stdio and a hosted Streamable HTTP endpoint at the pinned revision.](/mcp-servers/socket/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
