Registry Verifier Target A

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

MCP compatibility and transport verification server.

The publisher's own server: Registry Verifier Probe

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

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

What you can do
The registry lists no tools, so the only stated capability is acting as an MCP compatibility and transport verification server over streamable HTTP. No further detail on what an assistant could do with it is provided in the description, instructions or README. Treat it as a connectivity test target rather than a working toolset.
When to use it
Possibly useful when you want to check that an MCP client can connect to a remote streamable HTTP endpoint. It is not a substitute for a server that provides actual tools, since none are documented.
Requirements
A remote endpoint reached over streamable HTTP; no local runtime, package, environment variables or headers are declared. No authentication is declared. Network access to the remote host is required.
Before you install
The endpoint is hosted on a third-party free tunnel domain, which may be temporary or unstable. No tools, instructions or README are published, so its behavior cannot be reviewed before connecting. No authentication is declared, so avoid sending sensitive data to it.

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.njjtx-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://njjtx-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 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 Pinggy integrations

Registry Verifier Probe

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

A remote MCP compatibility and transport verification server, intended for checking that a client can connect to and communicate with an MCP endpoint.

Streamable HTTPWeb executable
Developer ToolsNot indexed yetOct 25, 2026

Registry Verifier Target B

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

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

Streamable HTTPWeb executable
Developer ToolsNot indexed yetOct 25, 2026

Registry Verifier Probe B

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

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

Streamable HTTPWeb executable
Developer ToolsNot indexed yetOct 25, 2026