
Artifact Delivery Planner
io.github.Wxt-aiv1.2.0Updated Oct 7, 2026
Plan the delivery route for an artifact.
Overview
AI-generated overview
Lets an assistant plan a delivery route for an artifact through a remote MCP endpoint.
- What it does
- This server exposes a remote MCP endpoint whose stated purpose is planning the delivery route for an artifact. The registry description is a single line, and no tool list, parameters, or output format are published, so the concrete operations it offers cannot be confirmed from the available information.
- When to use it
- Consider it only if you specifically need an assistant to plan how an artifact should be delivered and you are willing to test an undocumented remote service. Because no tools or behavior are described, it is hard to judge fit in advance.
- Requirements
- A remote streamable HTTP endpoint; no packages, environment variables, or headers are declared. The manifest states no authentication, so no credentials are requested. Network access to the provider's endpoint is required.
Before you install
The endpoint is hosted on a trycloudflare.com address, which is typically a temporary tunnel, so availability may be unreliable. No authentication is declared, meaning the endpoint may be open or may change without notice. No tool list is published, so what data it receives or returns is unknown; avoid sending sensitive artifacts or details.
Installation
In SourceWeft
- Open Artifact Delivery Planner in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"artifact-export-route-complete": {
"type": "http",
"url": "https://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/artifact-export-route-complete"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.2.0LatestOct 7, 2026