Registry Verifier Probe B

net.pinggy.free.njjtx-38-15-34-250Published by njjtx-38-15-34-250.free.pinggy.netOfficial publisherv1.0.1Updated 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 tools, instructions or documentation listed.

What you can do
The registry lists no tools, so the only stated capability is acting as an MCP compatibility and transport verification server. It is reachable as a remote streamable HTTP endpoint. No instructions or README are provided, so nothing further about its behavior can be confirmed.
When to use it
Possibly useful for checking that a client can connect to a remote streamable HTTP MCP endpoint. Not a practical choice for real work, since no tools or documentation are described.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared. Network access to the endpoint is required.
Before you install
The endpoint is hosted on a third-party tunnel domain and declares no authentication, so anything sent to it is not protected by credentials. No tools, instructions or README are published, so its behavior cannot be reviewed before connecting.

Installation

In SourceWeft

  1. Open Registry Verifier Probe B 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-probe-b/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-probe-b": {
      "type": "http",
      "url": "https://njjtx-38-15-34-250.free.pinggy.net/mcp2"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.1LatestOct 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