Truedge Crypto Safety MCP Server

by truedge Your server? Claim it

answering

Truedge Crypto Safety is answering right now. Last checked 3 min ago. It exposes 5 tools.

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

Uptime history 22 days of history

22 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

334 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Truedge Crypto Safety every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add crypto-safety --transport http https://truedge.xyz/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.crypto-safety]
url = "https://truedge.xyz/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

address

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.

contract

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.

recent

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.

token

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.

url

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.

Endpoints

URL	Transport	State	Latency	Checked
https://truedge.xyz/mcp	streamable-http	answering	287 ms	3 min ago

Alternatives to Truedge Crypto Safety

same job, measured the same way

Pathguard

by cieltech-pathguard

Crypto transaction safety tool — screens addresses and transactions for scam risk.

5 tools answering

Publicaml

by publicaml

AML screening for crypto addresses: risk, sanctions, fund tracing and counterparties.

41 installs/wk local only

traql

by traql

AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin

36 installs/wk local only

Sentinel

by 448c

Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.

2 tools answering

MCP Address History

by cryptoapis-io

MCP server for full transaction and token history on EVM and UTXO addresses via Crypto APIs

50 installs/wk local only

Stocks On Chain

by stocksonchain

Read-only tokenized stock data: issuers, chains, contract addresses and corporate actions.

8 tools answering

SaveSaveSaveSave

by stefantsezarov

Check messages, npm packages and crypto addresses before acting. Read-only scanner tools.

44 installs/wk local only

PnL Labs — Solana Trust & Risk Checks

by pnllabs

Trust checks for Solana trading: realized-PnL wallet trust, token safety, trade cost, forensics.

4 tools answering

Truedge Crypto Safety — questions

Answers built from our own checks of this server.

What can Truedge Crypto Safety do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_address, check_contract_safety, check_token_risk, check_url, get_recent_hacks. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Truedge Crypto Safety working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 334 ms. The bar chart above shows every period we have measured.

How do I connect Truedge Crypto Safety?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Truedge Crypto Safety need an API key?

No. Truedge Crypto Safety completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Truedge Crypto Safety?

It answers our handshake in 334 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.