Delivery Acknowledgement Guide

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

Set acknowledgement guidance for a delivery.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant set acknowledgement guidance for a delivery.

What you can do
  • Sets acknowledgement guidance for a delivery.
  • No tools are listed in the manifest, so the exact operations are not documented; the only stated capability is configuring how a delivery is acknowledged.
When to use it
Only worth adding if you specifically need an assistant to configure acknowledgement guidance for deliveries and you trust the endpoint; there is too little documentation to judge it otherwise.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared.
Before you install
The endpoint is an unauthenticated, undocumented Cloudflare tunnel address with no README, no listed tools and no declared owner details beyond a GitHub-style provider name. It may change or disappear without notice, and any data sent to it goes to a third party whose handling is unknown.

Installation

In SourceWeft

  1. Open Delivery Acknowledgement Guide 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%2Fexport-confirmation-style-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": {
    "delivery-acknowledgement-guide": {
      "type": "http",
      "url": "https://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/export-confirmation-style-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.