Truedge Crypto Safety

xyz.truedgePublished by truedge.xyzOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant run free crypto safety checks on tokens, contracts, wallet addresses and website URLs.

What you can do
Check a token's overall risk posture, including risk tier, contract-safety verdict and red flags, and get contract-level findings such as honeypot, mintable, hidden owner and holder concentration. Screen a wallet or contract address for sanctions, scam and drainer lists before sending funds. Check whether a URL is a known crypto phishing or look-alike site. List recent tracked crypto hacks and exploits, newest first, with reported loss, date and source.
When to use it
Useful when an assistant answers questions like whether a token is risky or safe to buy, whether an address is safe to send funds to, or whether a site is a phishing link before connecting a wallet. Also handy for summarizing recent crypto hacks.
Requirements
Remote streamable HTTP endpoint at truedge.xyz; no packages, environment variables, headers or authentication are declared. Network access to the endpoint is needed.
Before you install
Results are informational only and not financial advice; an absent flag is not a guarantee of safety, and contract findings can be stale. Do not treat a clean result as approval to send funds or connect a wallet.

Installation

In SourceWeft

  1. Open Truedge Crypto Safety in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.truedge%2Fcrypto-safety/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "truedge-crypto-safety": {
      "type": "http",
      "url": "https://truedge.xyz/mcp"
    }
  }
}

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.

Parameterssymbolrequired

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.

Parameterssymbolrequired

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.

Parametersdays

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.

Parametersaddressrequired

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.

Parametersurlrequired

Version history

1
  1. v1.0.0LatestSep 24, 2026

Score

72% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.