Security & Testing

usealertrelay.com

Provides integration instructions for connecting AlertRelay to set up security event monitoring, including the ingest API, event schema, heartbeats, and copy-paste snippets.

1 endpoint2 known toolsFirst detected September 25, 2026Last detected September 25, 2026

ENDPOINT 1

https://usealertrelay.com/mcp

No auth detected

MCP server metadata

Name: alertrelay
Version: 0.1.0

Capabilities

tools

Known tools 2

how_to_connect

Explain how to connect AlertRelay to this account so the agent can set up monitoring.

Inferred read-only

get_integration_guide

Full plain-text guide: the ingest API, the event schema, the standard security event types (failed_login, signup, error, blocked, …), heartbeats, and copy-paste snippets.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.alertrelay]
url = "https://usealertrelay.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "alertrelay": {
      "type": "http",
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: alertrelay
Remote MCP URL: https://usealertrelay.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "alertrelay": {
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "alertrelay": {
      "type": "http",
      "url": "https://usealertrelay.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "alertrelay",
  "transport": "streamable-http",
  "url": "https://usealertrelay.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.