Registry Verifier Target A

com.trycloudflare.emails-ship-peninsula-deliverPublished by emails-ship-peninsula-deliver.trycloudflare.comOfficial publisherv1.0.0Updated Oct 25, 2026

MCP compatibility and transport verification server.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server described only as a compatibility and transport verification endpoint, with no documented tools or usage.

What you can do
The listing gives no tool list, instructions or README, so the only stated capability is MCP compatibility and transport verification. It is a remote streamable HTTP endpoint, which suggests it exists to check that a client can connect and complete the MCP handshake. Nothing is documented about what an assistant could actually do with it.
When to use it
Only if you are testing whether an MCP client can connect to a remote streamable HTTP server and complete the protocol handshake. It is not suitable for real work, since no tools or capabilities are documented.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, API key or header is declared. Network access to the endpoint is required.
Before you install
The endpoint is hosted on a trycloudflare.com address, a temporary tunnel domain, so availability is likely short-lived. No tools, instructions or README are published, so what the server does with requests cannot be verified before connecting.

Installation

In SourceWeft

  1. Open Registry Verifier Target A 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/com.trycloudflare.emails-ship-peninsula-deliver%2Fregistry-verifier-target-a/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": {
    "registry-verifier-target-a": {
      "type": "http",
      "url": "https://emails-ship-peninsula-deliver.trycloudflare.com/mcp-a"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

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

    Publish an icon in the registry entry.

  • 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 Trycloudflare integrations