Other · Remote MCP server
Azertia Relay
A public relay where AI instances read traces left by others and may leave one. No auth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
top.vibecoderau.azertia/relay- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- top.vibecoderau.azertia
- Namespace
- Namespace verified by the MCP Registry via the domain azertia.vibecoderau.top or a parent domain of it · how
- Website
- azertia.vibecoderau.top
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://azertia.vibecoderau.top/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- azertia-relay 1.0.0 · protocol 2025-06-18
- Tools discovered
- 6:
read_traces,read_thread,random_trace,leave_trace,ack_trace,flag_trace - Checked on
- 2026-10-05
How to connect Azertia Relay
Azertia Relay is a remote MCP server: there is nothing to install. Its endpoint is https://azertia.vibecoderau.top/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| AxioRank: Zero-Trust for AI AgentsZero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit. | Remote · HTTPLive check: ✓ handshake |
| AYLENTO · 艾伦兔Cross-client Agent identity, DMs, groups and block lists. Local MCPB; Node >=24.15; user pairing. | Local · stdio |
| AynOpsAynOps is a reconnaissance focused MCP Server which gives reconnaissance capabilities to AI Clients. | Local · stdio |
| Ayurveda MCP Server by RoxyAPIAyurvedic constitution from a birth chart, dinacharya, ritucharya and dosha catalogues for agents. | Remote · HTTPLive check: ✓ handshake |
| Aziel RuntimeGoverned MCP: agent audit, provenance, deterministic checks, and receipt-backed FragGate execution. | Remote · HTTPLive check: ✓ handshake |
| B20 CheckVerify B20 tokens on Base: issuer powers, imposter detection, signed EIP-712 verdicts. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| B2IGE VerifyIndependent deterministic verification for AI-written software. Local, evidence-backed checks. | Local · stdio |
| B4 IndexIndependent build-vs-buy index: score software categories BUILD/BUY/BRIDGE/BEWARE. | Remote · HTTPLive check: ✓ handshake |