
RelayShield Security Intelligence
io.github.nzdsf2-gifPublished by GitHub account nzdsf2-gifv0.3.0Updated Oct 24, 2026
Breach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection.
Overview
Local MCP server that gives an assistant RelayShield security checks: breach, SIM swap, infostealer, lookalike domain, wallet, URL/file and credential exposure.
- What you can do
- Look up breach and infostealer exposure for emails, OAuth apps, sessions and non-human credentials, plus secrets in public repositories and supply-chain vendors. Check SIM swap and eSIM status through live carrier data. Detect typosquat and lookalike domains and assess MCP registry risk. Scan URLs and files for malware across many engines, then poll for the verdict. Check EVM wallet on-chain risk and prompt-injection-related breach exposure.
- When to use it
- Useful when vetting an identity, vendor, domain, MCP server or agent authority before trusting it, or when triaging a suspicious URL, file or wallet. Suited to security and fraud investigations rather than everyday tasks.
- Requirements
- Runs locally as a Python package (pip install or uvx). Requires RELAYSHIELD_API_URL. Access needs either a RelayShield API key in RELAYSHIELD_API_KEY (free tier 100 calls/month, paid tiers from $29/month) or an x402 payment proof in RELAYSHIELD_X_PAYMENT; set one, not both. Network access to the RelayShield API.
Installation
In SourceWeft
- Open RelayShield Security Intelligence in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
relayshield-mcp
mcp-name: io.github.nzdsf2-gif/relayshield-mcp
RelayShield security intelligence as an MCP server — plug breach detection, SIM swap detection, domain lookalike monitoring, OAuth supply chain watchlist, and URL/file scanning directly into Claude and any MCP-compatible AI agent.
Tools
check_oauth_watchlist, check_supply_chain, check_session_risk, check_nhi_exposure, and
check_secret_scan cover related ground — connected-app, session, and machine-credential exposure
for an identity or its supply chain — and are a natural set to use together when vetting an agent's
current authority, not just a login.
Access modes
Subscription — API key from api.relayshield.net/developers. All 15 tools available. Free tier: 100 calls/month. Paid tiers from $29/month.
Pay-as-you-go — No API key needed. Pay per check in USDC on Base (x402 protocol). Set RELAYSHIELD_X_PAYMENT with your payment proof. All 15 tools available ($0.05–$0.50/check, check_scan_result free). Call a tool with no payment set to receive pricing and payment instructions.
Discovery — Set neither key nor payment. Tool calls return payment requirements and a subscription link.
Install
Or run without installing:
Configure Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Subscription (RelayShield API key):
Pay-as-you-go (x402 USDC on Base):
Quit and relaunch Claude Desktop after editing.
Configure Claude Code (CLI)
Usage examples
Once configured, ask Claude:
For URL and file scans, Claude automatically polls check_scan_result every 5 seconds until the verdict is ready.
Environment variables
Set RELAYSHIELD_API_KEY or RELAYSHIELD_X_PAYMENT — not both. API key takes priority if both are set.
Links
Source: README.md at commit 85a11ac
Tools
0Version history
2- v0.3.0LatestSep 27, 2026
- v0.2.12Sep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.