Execute 3d-pallet-packing-mcp

io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026

Premium agentic endpoint for 3d-pallet-packing-mcp.

VerifiedSSEWeb executable

Overview

AI-generated overview

A remote MCP endpoint for 3D pallet packing that requires a paid per-call signature header.

What you can do
The registry lists this as a premium agentic endpoint for 3d-pallet-packing-mcp, reachable over SSE at a remote host. No tools are listed in the manifest, so the specific operations it exposes are not documented here. Based on the name, it appears intended to support 3D pallet packing tasks, but the input does not confirm any tool names or outputs.
When to use it
Consider it only if you specifically need a hosted 3D pallet packing service and are willing to pay per call. Because no tools are documented, verify the actual capabilities before relying on it.
Requirements
A remote SSE endpoint at No packages, environment variables, or accounts are declared. Each request must include a Payment-Signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, quoted at $0.2 USDC.
Before you install
This server requires a Payment-Signature header that authorizes an on-chain USDC transfer on Base Mainnet, so using it spends real funds. The signature is a payment authorization; treat it as sensitive and do not share it. No tools or data-handling details are documented, so review what data is sent to the remote endpoint before use.

Installation

In SourceWeft

  1. Open Execute 3d-pallet-packing-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Evozim%2F3d-pallet-packing-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "execute-3d-pallet-packing": {
      "type": "sse",
      "url": "https://api.m2mcent.com/3d-pallet-packing-mcp/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.