Developer · Local MCP server
RelayShield Security Intelligence
Breach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nzdsf2-gif/relayshield-mcp- Version
- 0.3.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- nzdsf2-gif (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nzdsf2-gif) · how
- Website
- relayshield.net
- Repository
- github.com/relayshield/relayshield-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | relayshield-mcp | 0.3.0 | stdio |
How to connect RelayShield Security Intelligence
RelayShield Security Intelligence runs locally from a Python package published to PyPI: relayshield-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx relayshield-mcp. It reads these environment variables: RELAYSHIELD_API_URL (required), RELAYSHIELD_API_KEY (secret) and RELAYSHIELD_X_PAYMENT (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
],
"env": {
"RELAYSHIELD_API_URL": "<value>",
"RELAYSHIELD_API_KEY": "<secret>",
"RELAYSHIELD_X_PAYMENT": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. 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 from nzdsf2-gif (GitHub)
| Server | Runs |
|---|---|
| RelayShield Scam ChecksFree scam checks for links, wallets, emails, and breach exposure. No signup. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| Regulatory MonitorFederal Register monitoring and regulations.gov tracking. 4 MCP tools for regulatory compliance. | Remote · HTTPLive check: ✗ no handshake |
| Regulatory SignalsAudit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor. | Local · stdio |
| RektREKT Store - browse and buy REKT drinks with AI-discounted pricing from any MCP client. | Local · stdio |
| RelayMCP relay server for Claude Desktop <-> Claude Code communication. | Local · stdio |
| RelaystationPay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC. | Remote · HTTPLive check: ✓ handshake |
| Release GatePre-deploy security auditor for AI agent code - the risks generic SAST misses. | Local · stdio |
| Release RadarCorrelate GitHub releases with Sentry issues and PagerDuty incidents. | Remote · HTTPLive check: ✓ handshake |
| RelinInspect webhook health, investigate delivery failures, configure sources, and replay events. | Remote · HTTPLive check: ✓ handshake |