Skip to main content
mcpSource-backedReview first Safety Privacy
Packrift logo

Packrift MCP Server

Packrift MCP Server exposes Packrift's packaging-supplies catalog through a remote MCP endpoint. It lets AI agents search packaging products, retrieve pricing and inventory context, and create cart URLs for ecommerce packaging workflows.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://packrift.com/pages/agents, https://github.com/Packrift/packrift-mcp
Brand
Packrift
Brand domain
packrift.com
Brand asset source
brandfetch
Safety notes
Verify pricing, inventory, packaging, and cart output before purchasing or using it in customer-facing commerce workflows.
Privacy notes
Product searches, pricing context, cart URLs, packaging requirements, and merchant interaction details may be sent through tool calls.
Author
Packrift
Submitted by
Packrift
Reviewed by
JSONbored
Claim status
unclaimed
Last verified
2026-05-10

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Provided

Copy snippet

Provided

Prerequisites

None

Platforms

4 listed

Install type

CLI install

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 1 risk area.

1 area
  • SafetyGeneralVerify pricing, inventory, packaging, and cart output before purchasing or using it in customer-facing commerce workflows.
  • PrivacyGeneralProduct searches, pricing context, cart URLs, packaging requirements, and merchant interaction details may be sent through tool calls.

Safety notes

  • Verify pricing, inventory, packaging, and cart output before purchasing or using it in customer-facing commerce workflows.

Privacy notes

  • Product searches, pricing context, cart URLs, packaging requirements, and merchant interaction details may be sent through tool calls.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Full copyable content
{
  "mcpServers": {
    "packrift": {
      "type": "http",
      "url": "https://mcp.packrift.com/mcp"
    }
  }
}

About this resource

Overview

Packrift MCP Server exposes Packrift's packaging-supplies catalog through a remote MCP endpoint. It lets AI agents search packaging products, retrieve pricing and inventory context, and create cart URLs for ecommerce packaging workflows. Use it when an agent needs packaging-supply discovery, carton or mailer selection, or cart-building support.

Usage

{
  "mcpServers": {
    "packrift": {
      "type": "http",
      "url": "https://mcp.packrift.com/mcp"
    }
  }
}

Source citations

Add this badge to your README

Show that Packrift MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/packrift-mcp-server.svg)](https://heyclau.de/entry/mcp/packrift-mcp-server)

How it compares

Packrift MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Review status, Source provenance, Submitter).

Field

Packrift MCP Server exposes Packrift's packaging-supplies catalog through a remote MCP endpoint. It lets AI agents search packaging products, retrieve pricing and inventory context, and create cart URLs for ecommerce packaging workflows.

Open dossier

Official Baselight remote MCP server for searching and querying a catalog of 70,000+ public datasets from Claude via OAuth or x-api-key authentication.

Open dossier

Real-time product search and price comparison across 11M+ products from Singapore, Southeast Asia, and US marketplaces via a remote streamable-HTTP MCP endpoint with API key auth.

Open dossier

Docker's MCP CLI plugin and gateway for running catalog, OCI, registry, or local-file MCP servers in containers and exposing them to Claude, Cursor, VS Code, and other MCP clients through a shared gateway profile.

Open dossier
Next steps
Trust
Review statusDiffersReviewedJSONbored · 2026-05-16ReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSubmission linkedSource submissionSubmission linkedSource submissionSource-backedSource-backed
SubmitterDiffersPackriftkiannidevBuyWhereoktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
BrandPackrift logoPackriftBuyWhere logoBuyWhereDocker MCP Gateway logoDocker MCP Gateway
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorPackriftBaselightBuyWheredocker
Added2026-05-102026-06-142026-06-262026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesVerify pricing, inventory, packaging, and cart output before purchasing or using it in customer-facing commerce workflows.Query tools may return large result sets; scope filters to avoid excessive data transfer. Some datasets are community-contributed; validate schema and quality before production use. OAuth tokens and API keys grant persistent catalog access until revoked. Do not run unreviewed SQL-like queries against sensitive production mirrors without safeguards.Read-only product catalog access by default; no write or delete operations exposed. API key should be stored in the MCP client config or environment, never committed.Docker MCP Gateway can start and route multiple MCP servers, so each connected client inherits the permissions of every enabled server and tool. Container isolation reduces host exposure, but Docker Engine or Docker socket access is still highly privileged and should be limited to trusted users. The gateway supports tool allowlists, CPU limits, memory limits, network blocking, secret blocking, image signature verification, and interceptors; review defaults before production use. Catalog, profile, local-file, and registry references can change which servers run behind the gateway, especially when watch mode or shared profiles are enabled. Tool-call logging is enabled by default in the documented flags, so avoid routing secrets or sensitive payloads unless logging and retention are controlled.
Privacy notesProduct searches, pricing context, cart URLs, packaging requirements, and merchant interaction details may be sent through tool calls.Search terms and query filters are sent to Baselight and may appear in usage logs. Dataset rows returned through MCP may include PII or licensed third-party content subject to dataset terms. Avoid pasting raw dataset excerpts containing personal data into public channels.BuyWhere API key is sent as a Bearer token in the Authorization header on every request. Search queries are sent to BuyWhere's API to retrieve product data; no third-party analytics or telemetry is included in MCP responses. BuyWhere may log API request metadata (endpoint, timestamp, status) for abuse prevention and billing.Docker MCP Gateway may process MCP server definitions, catalog entries, profile exports, local server files, secrets, OAuth tokens, tool names, tool arguments, tool outputs, logs, container metadata, and Docker Engine metadata. Secrets may come from Docker Desktop secrets or `.env` fallback files; keep those stores out of version control and restrict filesystem permissions. Tool outputs can include local files, API responses, credentials, account data, or infrastructure details depending on the enabled downstream MCP servers. Exported profiles and catalogs can reveal internal server names, image references, allowed tools, configuration values, and service endpoints.
Prerequisites— none listed
  • Baselight account with API access or OAuth authorisation for dataset queries.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with remote HTTP connectors.
  • Understanding of the dataset topics you plan to query to narrow catalog searches effectively.
  • Compliance review if exported dataset rows may contain regulated or personal data.
  • A BuyWhere API key (free at https://buywhere.ai/api-keys).
  • An MCP client such as Claude Code, Claude Desktop, Cursor, Windsurf, or any MCP-compatible host.
  • Network access to https://api.buywhere.ai.
  • Docker Desktop `4.59+` with the MCP Toolkit feature enabled, or the Docker MCP CLI plugin built and installed independently.
  • Docker Engine access for running containerized MCP servers and the gateway.
  • MCP server sources prepared from Docker MCP Catalog entries, OCI images, MCP Registry entries, or local YAML/JSON server files.
  • Profiles feature enabled when using `docker mcp profile` and profile-based gateway runs outside Docker Desktop.
Install
No local install package is required for the hosted endpoint. Configure the remote MCP URL: https://mcp.packrift.com/mcp
claude mcp add --transport http baselight https://api.baselight.app/mcp
claude mcp add buywhere --transport http --header "Authorization: Bearer YOUR_BUYWHERE_API_KEY" https://api.buywhere.ai/mcp
docker mcp gateway run
Config
{
  "mcpServers": {
    "packrift": {
      "type": "http",
      "url": "https://mcp.packrift.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "baselight": {
      "url": "https://api.baselight.app/mcp",
      "type": "http",
      "headers": {
        "x-api-key": "YOUR_BASELIGHT_API_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "buywhere": {
      "type": "http",
      "url": "https://api.buywhere.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BUYWHERE_API_KEY",
        "X-Buywhere-Market": "SG"
      }
    }
  }
}
{
  "mcpServers": {
    "MCP_DOCKER": {
      "command": "docker",
      "args": [
        "mcp",
        "gateway",
        "run"
      ]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.