Registry Verifier Target A

net.pinggy.free.wpgcs-38-15-34-250Published by wpgcs-38-15-34-250.free.pinggy.netOfficial publisherv1.0.0Updated Oct 26, 2026

MCP compatibility and transport verification server.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint described only as a compatibility and transport verification server; no tools or documentation are published.

What you can do
  • The registry lists no tools, and no instructions or README are provided.
  • The only stated purpose is verifying MCP compatibility and transport behavior.
  • Nothing indicates what an assistant could actually do with it beyond connecting.
When to use it
Only worth considering if you specifically want to test whether a client can connect to and negotiate with a remote streamable HTTP MCP endpoint. It is not a general-purpose tool server.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared. Works in browsers as well as desktop clients.
Before you install
The endpoint is hosted on a third-party free tunnel domain with no declared authentication, so anything sent to it is outside your control. No tools, instructions or README are published, so its behavior cannot be reviewed 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/net.pinggy.free.wpgcs-38-15-34-250%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://wpgcs-38-15-34-250.free.pinggy.net/mcp-a"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestOct 26, 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 Pinggy integrations

Registry Verifier Target B

net.pinggy.free.wpgcs-38-15-34-250Official publisher

A remote MCP endpoint described only as a compatibility and transport verification server, with no tools, instructions or documentation listed.

Streamable HTTPWeb executable
Developer ToolsNot indexed yetOct 26, 2026