Registry Verifier Target B

life.lhr.e80b81ce69cb44Published by e80b81ce69cb44.lhr.lifeOfficial publisherv1.0.0Updated Oct 26, 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 tools, instructions or documentation listed.

What you can do
  • The registry lists no tools for this server.
  • Its description presents it as an MCP compatibility and transport verification server, so it appears intended to check that a client can connect and negotiate the streamable HTTP transport.
  • No instructions or README are provided, so nothing is documented about what an assistant could actually do with it.
When to use it
Only worth connecting if you specifically want to test whether an MCP client can reach a remote streamable HTTP endpoint; it is not aimed at real work tasks.
Requirements
A remote endpoint at the given host over streamable HTTP; no packages, environment variables, headers or authentication are declared.
Before you install
The endpoint is hosted on a temporary-looking lhr.life domain, so availability is likely short-lived. No tools, instructions or documentation are published, so its behavior cannot be reviewed before connecting; treat any data sent to it as going to an unknown third party.

Installation

In SourceWeft

  1. Open Registry Verifier Target 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/life.lhr.e80b81ce69cb44%2Fregistry-verifier-target-d/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-b": {
      "type": "http",
      "url": "https://e80b81ce69cb44.lhr.life/mcp-d"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.