RelayShield Security Intelligence
PYPI · RELAYSHIELD-MCP · SCANNED SEP 20
Breach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4295 tokens (~268/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the RelayShield Security Intelligence MCP server?
RelayShield Security Intelligence runs locally as a PyPI package, launched with uvx relayshield-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · relayshield-mcp
claude mcp add nzdsf2-gif-relayshield-mcp -- uvx relayshield-mcp
{
"mcpServers": {
"nzdsf2-gif-relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
]
}
}
} {
"servers": {
"nzdsf2-gif-relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
]
}
}
} codex mcp add nzdsf2-gif-relayshield-mcp -- uvx relayshield-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nzdsf2-gif-relayshield-mcp": {
"type": "local",
"command": [
"uvx",
"relayshield-mcp"
],
"enabled": true
}
}
} openclaw mcp add nzdsf2-gif-relayshield-mcp --command uvx --arg relayshield-mcp
mcp_servers:
nzdsf2-gif-relayshield-mcp:
command: "uvx"
args: ["relayshield-mcp"] {
"McpServers": {
"nzdsf2-gif-relayshield-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"relayshield-mcp"
]
}
}
} assistant mcp add nzdsf2-gif-relayshield-mcp -t stdio -c uvx -a relayshield-mcp
{
"mcpServers": {
"nzdsf2-gif-relayshield-mcp": {
"command": "uvx",
"args": [
"relayshield-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Package version: 0.2.7 → 0.2.11 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 8 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 7 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 6 Sept 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- Package version: 0.2.7 → 0.2.11 functional
- 5 Sept 26 −15
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/relayshield-mcp@0.2.11
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_breach ~230
Check whether an email address appears in known data breaches. Uses Have I Been Pwned (HIBP) — 13 billion+ compromised accounts. Returns breach count and details (breach name, date, exposed data classes). Use before allowing high-risk actions that depend on credential integrity. Pay-as-you-go: $0.10 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to check | |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_domain_lookalikes ~283
Detect typosquat and lookalike domains impersonating a brand. Generates hundreds of permutations (TLD swaps, character typos, homoglyphs, phishing prefixes/suffixes), resolves them in parallel via DNS, and enriches live results with Certificate Transparency data (cert count, recent issuance). Returns all lookalike domains that are currently registered and resolving. Use to find domains impersonating your brand, or before an employee clicks a link that resembles a company domain. Pay-as-you-go: $0.50 USDC per scan (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain to scan (e.g. acme.com — no scheme or path needed) |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_infostealer ~289
Check whether an email address appears in infostealer malware logs. Uses Hudson Rock Cavalier — a database of credentials harvested directly from infected computers by infostealer malware (RedLine, Raccoon, Vidar, etc.). Returns found (bool), stealer count, and per-infection details: date compromised, operating system, malware path, and number of corporate/personal credentials stolen. Unlike breach databases (HIBP), infostealer hits mean the device itself was compromised — all stored passwords, session cookies, and crypto keys are at risk. Pay-as-you-go: $0.15 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to check for infostealer compromise | |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_llm_credential_exposure ~339
Check a domain, or up to 10 vendor domains, for exposed LLM/AI provider API keys in criminal stealer log archives (LLMjacking) — closed-source platforms including OpenAI, Anthropic Claude, Google Gemini, xAI Grok and Amazon Bedrock, alongside DeepSeek, Moonshot Kimi, Alibaba Qwen, NVIDIA NIM and Hugging Face. A leaked LLM provider key is a live, uncapped billing liability — real incidents have run from tens of thousands of dollars per day to a $500K single-month bill from one unthrottled key. Use to check your own domain or a vendor/supply-chain dependency. Pay-as-you-go: $0.40 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Your own domain to check. Provide this or vendor_domains (or both). |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| vendor_domains | array | – | Up to 10 vendor/supply-chain domains to check. |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_mcp_registry_risk ~308
Check an MCP server URL or package name for red flags: known-malicious IOC match, typosquat/near-miss against well-known MCP ecosystem domains, and domain registration age. Part of RelayShield's Agentic Attack Surface bundle — early coverage for an ecosystem with minimal dedicated security tooling as of 2026. Use before an agent connects to or installs a new, unfamiliar MCP server. Absence of findings means 'unknown,' not 'verified safe.' Pay-as-you-go: $0.35 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| package_name | string | – | Package name to check if no server_url is available (limited coverage — no dedicated MCP package registry yet) |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| server_url | string | – | MCP server URL to check (e.g. https://example-mcp-server.com) |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_nhi_exposure ~273
Check a domain, or up to 10 vendor domains, for exposed non-human-identity (NHI) credentials — API keys, service-account tokens, personal access tokens, and other machine identities found in criminal stealer logs. Use to assess exposure of the machine credentials an agent or its supply chain actually runs on, not just human logins. Pay-as-you-go: $0.40 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Your own domain to check. Provide this or vendor_domains (or both). |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| vendor_domains | array | – | Up to 10 vendor/supply-chain domains to check. |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_oauth_watchlist ~271
Check whether any high-risk OAuth-capable SaaS apps connected to an email account have appeared in recent data breaches. Monitors a curated watchlist of apps (Slack, Notion, GitHub, Zapier, Vercel, Loom, HubSpot, AI tools, and more). An attacker who breaches these services may obtain OAuth tokens granting access to your Google Workspace or Microsoft 365 without touching your password. Returns matched breached apps and recommended revocation steps. Pay-as-you-go: $0.15 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address whose connected OAuth apps to check | |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_prompt_injection_breach ~246
Check whether an email address has exposure in a criminal dump whose own announcement text suggests an AI agent — rather than a traditional phishing or malware campaign — was involved in obtaining it. Heuristic v1 classifier over Telegram dump-announcement text, not a confirmed-attribution guarantee. Use as an early signal that an AI agent workflow may have been the breach vector. Pay-as-you-go: $0.35 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to check | |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_scan_result ~217
Poll for the result of a previously submitted URL or file scan. Call every 5 seconds after scan_url or scan_file until status is 'completed'. Returns verdict (malicious/suspicious/clean) and engine vote counts, or {status: pending} if the scan is still running. Free with a paid scan (no additional charge).
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_id | string | yes | analysis_id returned by scan_url or scan_file |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_secret_scan ~251
Check a domain, or up to 5 vendor domains, for secrets and credentials exposed in public GitHub repositories. Use to assess whether an agent's own domain, or a vendor/supply-chain dependency's domain, has leaked credentials sitting in indexed public source code. Pay-as-you-go: $0.35 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Your own domain to check. Provide this or vendor_domains (or both). |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| vendor_domains | array | – | Up to 5 vendor domains to check. |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_session_risk ~230
Check an email address for active or reusable stolen session material (cookies, tokens) found in criminal stealer logs — exposure that can bypass MFA entirely, not just a password. Use to assess whether an identity currently has hijackable sessions in circulation. Pay-as-you-go: $0.30 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to check for active session/AiTM exposure | |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_sim_swap ~253
Detect whether a SIM swap or eSIM provisioning event has occurred on a phone number in the last 24 hours. Uses Twilio Lookup v2 with live carrier data. Returns swapped (bool), swap timestamp, and current carrier. Use when a user reports losing mobile service, or before completing a high-risk action that depends on SMS-based authentication. Pay-as-you-go: $0.25 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number in E.164 format (e.g. +14155551234) |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
check_supply_chain ~279
Check up to 10 vendor domains (or vendor emails, domain extracted automatically) for breach and infostealer exposure. Returns a per-vendor risk level plus an aggregate dark-web exposure score. Use to vet a third-party vendor, MCP server operator, or supply-chain dependency before an agent integrates with or grants access to it. Pay-as-you-go: $0.10 USDC per check (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| vendor_domains | array | – | Up to 10 vendor domains to check, e.g. ['vendor.example.com']. Provide this or vendor_emails. |
| vendor_emails | array | – | Alternative: vendor email addresses — the domain portion is extracted automatically. |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
scan_file ~272
Submit a file for binary malware analysis across 70+ AV engines. Provide a publicly accessible download URL — RelayShield handles the download. Returns an analysis_id immediately (async). Call check_scan_result with the analysis_id every 5 seconds until verdict is returned. Verdicts: malicious | suspicious | clean | timeout. Use when a user receives an email attachment and forwards the download link. Pay-as-you-go: $0.10 USDC per scan (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| file_url | string | yes | Publicly accessible URL to download the file from |
| filename | string | – | Optional filename hint (e.g. invoice_march.pdf) |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
scan_url ~246
Submit a URL for malware and phishing analysis across 70+ security engines. Returns an analysis_id immediately (async). Call check_scan_result with the analysis_id every 5 seconds until verdict is returned. Verdicts: malicious | suspicious | clean | timeout. Use before navigating to an unfamiliar URL or when a user forwards a suspicious link. Pay-as-you-go: $0.05 USDC per scan (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| url | string | yes | URL to scan (must start with http:// or https://) |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
scan_wallet ~308
Check an EVM wallet address for on-chain risk signals using GoPlus Security. Detects blacklisted addresses, contract risk flags, malicious activity, phishing associations, and other on-chain threat indicators. Returns risk_level (LOW/MEDIUM/HIGH), risk_flags list, and raw GoPlus data. Supports Ethereum mainnet (default) and other EVM chains via chain_id. Use before sending funds to an unknown address or in DeFi due-diligence flows. Pay-as-you-go: $0.10 USDC per scan (x402 on Base). Subscription: rapidapi.com/relayshield
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | EVM wallet address to scan (0x + 40 hex chars) |
| chain_id | string | – | EVM chain ID (default: 1 for Ethereum mainnet). Use 8453 for Base, 137 for Polygon. |
| rs_api_key | string | – | Optional. Your own RelayShield subscription API key for this call, overriding the server's default credential. Use when multiple callers share one running server (e.g. an Apify Actor) and each must p… |
| x_payment | string | – | Optional. x402 payment proof for this specific call, overriding the server's default. Ignored if rs_api_key is also given for this call (a key is cheaper per-check than paying per-call). Same use cas… |
No output schema declared.
No examples provided.
What is the RelayShield Security Intelligence MCP server?
RelayShield Security Intelligence is an MCP server listed in the public MCP registry as io.github.nzdsf2-gif/relayshield-mcp. Breach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection. This page covers its PyPI package (relayshield-mcp).
Is the RelayShield Security Intelligence MCP server safe to use?
RelayShield Security Intelligence scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RelayShield Security Intelligence MCP server expose?
RelayShield Security Intelligence exposes 16 tools: check_breach, check_sim_swap, check_domain_lookalikes, check_oauth_watchlist, check_infostealer, and 11 more. Their descriptions and schemas cost roughly 4,295 tokens of context every time the server is loaded.
Is the RelayShield Security Intelligence MCP server still maintained?
RelayShield Security Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the RelayShield Security Intelligence MCP server under?
RelayShield Security Intelligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.