Truedge Crypto Safety
Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links.
Should I use this
Quality & Safety
Findings (2)
- HIGHTool poisoning patterns detected
- INFOTool description contains placeholder or incomplete textin get_recent_hacks
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"crypto-safety": {
"url": "https://truedge.xyz/mcp"
}
}
}Remote endpoints
https://truedge.xyz/mcpstreamable-httpWhat it can do
Tool inventory
Tools (5)
🟢check_token_risk(symbol)
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.
Input Schema
{
"type": "object",
"properties": {
"symbol": {
"type": "string",
"description": "Token symbol, e.g. PEPE, BTC, ASTER"
}
},
"required": [
"symbol"
]
}🟢check_contract_safety(symbol)
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.
Input Schema
{
"type": "object",
"properties": {
"symbol": {
"type": "string",
"description": "Token symbol"
}
},
"required": [
"symbol"
]
}🟢get_recent_hacks(days)
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.
Input Schema
{
"type": "object",
"properties": {
"days": {
"type": "number",
"description": "Lookback window in days (default 30, max 90)"
}
}
}🟡check_address(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.
Input Schema
{
"type": "object",
"properties": {
"address": {
"type": "string",
"description": "A wallet/contract address (0x… EVM or a Solana base58 address)"
}
},
"required": [
"address"
]
}🟢check_url(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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A website URL or domain, e.g. app.uniswap.org"
}
},
"required": [
"url"
]
}Community
Evidence