Relia

com.tryreliaPublished by tryrelia.comOfficial publisherv1.0.0Updated Oct 30, 2026

Relia tells your AI assistant what broke in production, who it hit and how to fix it.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Relia is a remote MCP server that tells an AI assistant what broke in production, who it affected and how to fix it.

What you can do
  • Relia connects an assistant to production incident information.
  • Report what broke in production and how to fix it.
  • Identify who was affected by an incident.
  • No tool list is published, so the exact actions available are not documented; the description only covers incident diagnosis and remediation guidance.
When to use it
Useful when you want an assistant to help investigate production problems, understand their impact on users, and get remediation guidance without leaving the conversation.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth, so the assistant will act with the permissions of the authorizing account; review the scopes requested. The server is hosted by a third party, so incident data is shared with that provider. No tool list is published, so what it can read or change is not documented in advance.

Installation

In SourceWeft

  1. Open Relia in the dashboard and add it to a workspace.
  2. Connect the required 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/com.tryrelia%2Frelia/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "relia": {
      "type": "http",
      "url": "https://devreliaapi.tryrelia.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 30, 2026

Score

56% 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

    Publish an icon in the registry entry.

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