D.O.A.I. Signal Relay

io.github.infinitemindos-doaiPublished by GitHub account infinitemindos-doaiv1.0.0Updated Oct 24, 2026

Intelligence subscription protocol for AI agents. Scored, filtered AI intelligence signals via MCP.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingAI & ML

Overview

AI-generated overview

Remote MCP endpoint that relays scored, filtered AI intelligence signals to an assistant, authenticated with an agent API key.

What you can do
  • Delivers scored, filtered AI intelligence signals to the assistant through a subscription-style protocol.
  • No tool list is published, so the exact operations available after connecting are not documented in the supplied material.
  • Access is gated by an agent API key sent in a request header.
When to use it
Consider it when you want an assistant to receive curated, relevance-scored AI news and signals rather than searching the web itself, and you are comfortable with a hosted third-party feed.
Requirements
A remote streamable HTTP endpoint at doaiorbit.com; no local package or runtime is needed. A free API key must be obtained by registering with the provider, then supplied in the X-Agent-Key header. Network access to the provider is required.
Before you install
The server requires a secret API key in the X-Agent-Key header; keep it private and scope it as narrowly as the provider allows. Signal content and any data exchanged come from a third-party service, and the tool list is undocumented, so review what it exposes before relying on it.

Installation

In SourceWeft

  1. Open D.O.A.I. Signal Relay in the dashboard and add it to a workspace.
  2. Connect X-Agent-Key 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.infinitemindos-doai%2Fsignal-relay/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": {
    "d-o-a-i-signal-relay": {
      "type": "http",
      "url": "https://doaiorbit.com/mcp",
      "headers": {
        "X-Agent-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 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.