RelayShield Security Intelligence runs on your own machine — the client starts it, so there is no endpoint to ping. 125 installs a week from pypi. Last commit 7 Sep 2026.
Breach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
ENV RELAYSHIELD_API_KEY=""
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add relayshield-mcp -e 'RELAYSHIELD_API_URL=<RELAYSHIELD_API_URL>' -- uvx relayshield-mcp{
"mcpServers": {
"relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
],
"env": {
"RELAYSHIELD_API_URL": "<RELAYSHIELD_API_URL>"
}
}
}
}[mcp_servers.relayshield-mcp]
command = "uvx"
args = ["relayshield-mcp"]
env = { RELAYSHIELD_API_URL = "<RELAYSHIELD_API_URL>" }{
"mcpServers": {
"relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
],
"env": {
"RELAYSHIELD_API_URL": "<RELAYSHIELD_API_URL>"
}
}
}
}{
"servers": {
"relayshield-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"relayshield-mcp"
],
"env": {
"RELAYSHIELD_API_URL": "<RELAYSHIELD_API_URL>"
}
}
}
}Put your own value in place of
<RELAYSHIELD_API_URL> (RelayShield API base URL — https://api.relayshield.net).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
RELAYSHIELD_API_KEY (RelayShield API key for subscription access (all tools available) — get one at api.relayshield.net/developers), RELAYSHIELD_X_PAYMENT (x402 payment proof — USDC on Base (pay-as-you-go mode, no API key needed)).
Alternatives to RelayShield Security Intelligence
same job, measured the same waySecurity scanner for AI agents: prompt injection, leaked secrets, PII, and SSRF-risk URL detection.
Multi-agent LLM security layer detecting prompt injection and jailbreaks.
npm registry MCP server — package intelligence, security audits, dependency analysis
Scans MCP servers for tool poisoning, prompt injection and supply chain risks.
Prompt-injection shield for agents: read pages, scan content, audit MCP servers and skills. x402.
AI security layer: code scanning, PII detection, prompt injection, secrets, CVEs
Domain overviews for security and sales: registration, infrastructure, and risk signals.
MCP security scanner: detect tool poisoning, prompt injection & rug-pulls - 10 OWASP heuristics.
RelayShield Security Intelligence — questions
Answers built from our own checks of this server.