Skip to content

RelayShield Scam Checks

by nzdsf2-gif · remote · no sign-in to list tools · v1.30.0 · published by GitHub user nzdsf2-gif

Free scam checks for links, wallets, emails, and breach exposure. No signup.

Changes · 3
CompareRegistry entry

4 tools: 3 change things and 1 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http relayshield-free https://relayshieldadmin-relayshield-free-mcp.hf.space/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warncheck_link

    The server marks "check_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "check_link" says "link": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 3Claude Code: ask
  • check_breachChecks whether an email address appears in known data breaches.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks whether an email address appears in known data breaches. Provide `email`. Returns the number of breaches found with the named sources behind each; a count of zero means no breaches were found in the corpus, not that the address is safe. Read-only: it only looks up breach records. Requires the RELAYSHIELD_API_KEY environment variable; without it, the tool returns setup instructions instead of calling the API.

    Annotations the server declares

    • title: Check an email against known data breaches
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • check_emailScores a suspicious email for phishing signals from its parsed fields.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scores a suspicious email for phishing signals from its parsed fields. Provide any of: from_address, from_name, reply_to, return_path, subject, body_text, and links (up to 25). Returns a risk level and score with the specific flags behind them; links in the email are also checked against RelayShield's threat-intelligence corpus. A verdict of unknown means nothing conclusive was found; this tool never reports an email as safe.

    Annotations the server declares

    • title: Score an email for phishing signals
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 1Claude Code: allow
  • check_walletReturns a read-only risk assessment of a cryptocurrency wallet address.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns a read-only risk assessment of a cryptocurrency wallet address. It never moves funds or initiates transactions. Provide `address`; the chain (EVM, Solana, TON, or Bitcoin) is detected from the address format automatically. Returns a risk level of CRITICAL, HIGH, MEDIUM, LOW, or unknown, with the specific sanctions, scam, drainer, and phishing flags behind it. A verdict of unknown means nothing is known against the address; it does not mean the address is safe.

    Annotations the server declares

    • title: Check a crypto wallet for risk
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.30.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http relayshield-free https://relayshieldadmin-relayshield-free-mcp.hf.space/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__relayshield-free__check_wallet"
    ],
    "ask": [
      "mcp__relayshield-free__check_link",
      "mcp__relayshield-free__check_email",
      "mcp__relayshield-free__check_breach"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as relayshield-free. Review it before you use it.