# relayer

> relayer, an MCP server by xns.tech, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Conversationally set up & manage an XNS Relayer over stdio: install, claim, VPD, S3, backups.

- Canonical: https://www.anchorterminal.com/tools/xns-relayer
- Markdown: https://www.anchorterminal.com/tools/xns-relayer.md (~450 tokens)
- Slim: https://www.anchorterminal.com/tools/xns-relayer.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/xns-relayer.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

# relayer

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by xns.tech (https://xns.tech)
- Listed because: It's published in the registry under xns.tech, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Conversationally set up & manage an XNS Relayer over stdio: install, claim, VPD, S3, backups.

## Facts

- MCP registry: `tech.xns/relayer` 0.11.1
- Package: npm `@xns-cloud/relayer-mcp` (stdio)
- Source: https://gitlab.com/scpcorp/relayer-mcp
- Website: https://xns.tech
- npm downloads a week: 105
- Registry entry updated: 2026-10-03

- JSON: https://www.anchorterminal.com/api/v1/tools/xns-relayer.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming