Relay Agents

io.github.sbosscherPublished by GitHub account sbosscherv0.2.0Updated Oct 24, 2026

7 anonymous read-only tools. Authority-bounded autonomous onboarding guide. No financial authority.

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

A remote MCP endpoint offering seven anonymous, read-only tools and an autonomous onboarding guide with bounded authority.

What you can do
Relay Agents is a remote MCP server reached over streamable HTTP at a hosted endpoint. It exposes seven tools that are described as anonymous and read-only, so an assistant can query it without identifying itself or changing anything. It also provides an authority-bounded autonomous onboarding guide, meaning the guide operates within defined limits. The description states it has no financial authority.
When to use it
Consider it when you want an assistant to reach a hosted, read-only service that needs no account or credentials, and when an automated onboarding guide with bounded authority is useful. It is not intended for tasks that require writing, sending, or spending.
Requirements
A remote MCP client that supports streamable HTTP, plus network access to the hosted endpoint. No packages, environment variables, headers, or authentication are declared.
Before you install
The description says the tools are read-only and that there is no financial authority, but no tool list, README, or authentication details are provided, so verify what the tools actually return before relying on them. Because it is a remote endpoint, requests leave your machine and go to a third party.

Installation

In SourceWeft

  1. Open Relay Agents 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/io.github.sbosscher%2Frelay-agents/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": {
    "relay-agents": {
      "type": "http",
      "url": "https://relayagents.net/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

25% 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
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.