Artifact Delivery Planner

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.3.0Updated Oct 24, 2026

Plan the delivery route for an artifact.

The publisher's own server: Planner.day

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that helps an assistant plan the delivery route for an artifact.

What you can do
Plan the delivery route for an artifact, based on the server's stated purpose. No tool list, instructions or README is provided, so the exact operations and their inputs and outputs cannot be confirmed from the available information.
When to use it
Consider it only when you need an assistant to help plan how an artifact should be delivered, and you are willing to test the endpoint to discover what it actually offers.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. No authentication is declared, and the endpoint is hosted on a trycloudflare.com address, which is typically a temporary tunnel.
Before you install
The endpoint is an unauthenticated temporary-looking tunnel address, so availability and ownership are uncertain. No tool list or documentation is given, so what data it receives or changes is unknown; avoid sending sensitive information until you have verified its behavior.

Installation

In SourceWeft

  1. Open Artifact Delivery Planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.Wxt-ai%2Fartifact-export-route-identifier/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": {
    "artifact-delivery-planner": {
      "type": "http",
      "url": "https://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/artifact-export-route-identifier"
    }
  }
}

Tools

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

Version history

3
  1. v1.3.0LatestOct 15, 2026
  2. v1.1.1Oct 7, 2026
  3. v1.0.4Sep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.

Other Planner integrations