RelayShield

Created By
RelayShielda month ago
RelayShield gives AI agents and developers real-time identity and infrastructure threat detection via a single REST API. Monitor breach exposure, SIM/eSIM swap attacks, and domain lookalikes. Install as a native MCP server for Claude Desktop and Claude Code in one line: pip install relayshield-mcp
Overview

What RelayShield Does

RelayShield gives AI agents and developers real-time identity and infrastructure threat detection via a single REST API.

Available Tools

  • check_breach — Check if an email address appears in known data breaches
  • check_sim_swap — Detect SIM/eSIM swap activity on a phone number
  • check_domain_lookalikes — Scan for typosquat/lookalike domains targeting your brand
  • scan_url — Analyse a URL for phishing and malware signals (coming soon)
  • scan_file — Scan a file hash for malware detection (coming soon)

Quick Start

pip install relayshield-mcp

Get your API key at relayshield.net

Use Cases

  • Verify user identity risk before high-value transactions
  • Alert users when their credentials appear in a breach
  • Detect infrastructure attacks against your domain in real time
  • Add security tooling to any Claude Desktop or Claude Code workflow

Server Config

{
  "mcpServers": {
    "relayshield": {
      "command": "uvx",
      "args": [
        "relayshield-mcp"
      ],
      "env": {
        "RELAYSHIELD_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}
Project Info
Created At
a month ago
Updated At
a month ago
Author Name
RelayShield
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago