Skills/PyPI/relayshield-mcp

relayshield-mcp@0.3.0

VERIFIED· not started

Publisher claims: "MCP server for RelayShield — breach detection, SIM swap, domain lookalikes, OAuth watchlist, infostealer detection, URL/file scanning, MCP registry risk, and prompt-injection breach detection. Subscription (RapidAPI) and pay-as-you-go (x402 USDC on Base) access modes." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher relayshield-relayshieldadmin · publishing for 51 daysInstalls 248Last detonated 43 min ago
$claude mcp add relayshield-mcp -- uvx relayshield-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
RELAYSHIELD_API_KEYConfiguration, not credentials: RELAYSHIELD_API_URL, RELAYSHIELD_X_PAYMENT, RS_SOURCE_TAG
Where it talks to
relayshield.net (its own)Also rapidapi.com, example-mcp-server.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names rapidapi.com, example-mcp-server.com as well as its own vendor. The guard injects RELAYSHIELD_API_KEY only into requests to relayshield.net (and its subdomains) and refuses the rest.

$vet-skills run --secrets RELAYSHIELD_API_KEY=relayshield.net -- uvx relayshield-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

LOW
Prompt injectionREADME.md:133 · Prompt injection — known jailbreak technique reference · informational: not an instruction file**ChatGPT** — ChatGPT connects to MCP servers through Developer ModeFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01
LOW
Financial transfer languageREADME.md:108 · Financial transfer language — potential advance-fee scam · informational: not an instruction file| `check_wallet` | Screen a crypto wallet before paying it (chain auto-detected) | no |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
LOW
Authorization escalation languageREADME.md:133 · Authorization escalation language · informational: not an instruction file**ChatGPT** — ChatGPT connects to MCP servers through Developer ModeFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

Cost to the agent

Instructions loaded
≈105 tok
1 file · 22 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.