Truedge Crypto Safety

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Truedge Crypto Safety": {
      "url": "https://truedge.xyz/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• check_token_risk

  Get Truedge's overall risk posture for a crypto token (pump-and-dump / risk-watch tier, contract-safety verdict, and red flags). Use for 'is <token> risky / a scam / safe to buy?' questions. Informational only, not financial advice.

  Parameters:

  • symbol (required) — string — Token symbol, e.g. PEPE, BTC, ASTER

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• check_contract_safety

  Get the on-chain contract-safety findings (GoPlus) for a token: honeypot, mintable, ownership renounced, hidden owner, transfer-pausable, holder concentration. Use it when the question is specifically about the token's contract; use check_token_risk for an overall risk picture. Findings can be stale (the result says when a fresh check is needed), and a symbol shared by several tokens resolves to one of them. Absence of a flag is not a guarantee of safety.

  Parameters:

  • symbol (required) — string — Token symbol

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_recent_hacks

  List recent crypto hacks and exploits that Truedge tracks, newest first, one line per incident with the reported loss, date and the original report's URL. Only incidents with a source-stated date, a reported victim loss and an accountable original source are included; duplicates of one incident are merged. Loss figures are what sources reported, not Truedge investigations, and can change. Use it to answer 'what crypto hacks happened recently' or to check whether a protocol was recently exploited; it does not say whether a user was affected or how to recover funds.

  Parameters:

  • days — number — Lookback window in days (default 30, max 90)

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• check_address

  Check a crypto WALLET or contract ADDRESS for scam/sanctions risk before sending funds to it. Screens OFAC sanctions, known scam/drainer wallet lists, and on-chain reputation. Use for 'is 0x… a scam / safe to send to?'. Absence of a flag is NOT a guarantee of safety.

  Parameters:

  • address (required) — string — A wallet/contract address (0x… EVM or a Solana base58 address)

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• check_url

  Check whether a website URL is a known crypto PHISHING / fake site before connecting a wallet. Screens phishing blocklists plus look-alike-domain heuristics (punycode, brand impersonation, typosquats). Absence of a flag is NOT a guarantee of safety.

  Parameters:

  • url (required) — string — A website URL or domain, e.g. app.uniswap.org

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.