Remote MCP Server

io.github.CaSO44444Published by GitHub account CaSO44444v1.0.0Updated Nov 4, 2026

Remote MCP server available at 8.133.174.91.

The publisher's own server: Registry Mcp

VerifiedSSEWeb executable

Overview

AI-generated overview

A remote MCP server hosted at a bare IP address, with no documented tools, description, or authentication details.

What you can do
  • The listing only states that a remote MCP server is reachable at a numeric IP address over SSE.
  • No tools are listed, so what an assistant could actually do with it is unknown.
  • No README, instructions, or usage examples are provided.
  • No authentication method, environment variables, or headers are declared.
When to use it
Only worth considering if you already know the operator and what this endpoint exposes; there is no published information to judge it by. Most users should wait for documentation before connecting.
Requirements
A remote SSE endpoint at the given IP address; the client must support SSE transport. No packages, environment variables, headers, or credentials are declared.
Before you install
The endpoint is a bare IP address with no named operator, no authentication declared, and no documentation of its tools. Anything an assistant sends to it goes to an unidentified third party, and its behavior cannot be verified in advance.

Installation

In SourceWeft

  1. Open Remote MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/io.github.CaSO44444%2Fremote-mcp/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": {
    "remote": {
      "type": "sse",
      "url": "https://8.133.174.91/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

67% 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
  • 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 Remote-Mcp integrations