Registry

io.github.urnetworkPublished by GitHub account urnetworkv2026.2.20Updated Oct 24, 2026

Cloud-hosted MCP server for URnetwork VPN and Proxy

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

A cloud-hosted MCP server for URnetwork VPN and Proxy, letting an assistant reach URnetwork services through a remote OAuth-protected endpoint.

What you can do
Connects an assistant to URnetwork's VPN and proxy services through a hosted remote endpoint rather than a local package. No tool list is published, so the specific actions available are not documented here. Access is gated by OAuth sign-in.
When to use it
Consider it when you already use URnetwork and want an assistant to work with its VPN and proxy services from a hosted endpoint, without installing anything locally.
Requirements
A remote connection to the hosted endpoint at mcp.bringyour.com over streamable HTTP, plus an OAuth sign-in with a URnetwork account. No environment variables or headers are declared.
Before you install
Authentication is required and handled through OAuth, so the assistant gains access to your URnetwork account context. The published material does not describe which tools exist or whether they change settings, start or stop connections, or send data to third parties; confirm this before connecting.

Installation

In SourceWeft

  1. Open Registry in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.urnetwork%2Fregistry/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "registry": {
      "type": "http",
      "url": "https://mcp.bringyour.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2026.2.20LatestSep 16, 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 listed15 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.