Relayer

tech.xnsPublished by xns.techv0.12.0Updated Nov 7, 2026

Conversationally set up & manage an XNS Relayer over stdio: install, claim, VPD, S3, backups.

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

Lets an assistant set up and manage an XNS Relayer over stdio, covering installation, claiming, VPD, S3 storage and backups.

What you can do
  • Install and configure an XNS Relayer through conversation.
  • Claim a relayer and manage its VPD settings.
  • Handle S3 storage configuration and backups.
  • No tool list, instructions or README were supplied, so the exact commands and parameters are not documented here.
When to use it
Worth considering if you run or plan to run an XNS Relayer and want an assistant to walk through installation, claiming and storage or backup setup instead of doing it by hand.
Requirements
Runs as a local process over stdio, installed from the npm package @xns-cloud/relayer-mcp, so a Node.js runtime is needed. Desktop-only; no authentication, environment variables or headers are declared.
Before you install
It can install software and change relayer configuration, including claiming and backups, on your machine. No credentials are declared, but the setup steps may still involve storage or account details; review what it asks for before confirming.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.12.0LatestOct 8, 2026
  2. v0.11.1Oct 3, 2026
  3. v0.10.2Sep 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 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.