Truedge Crypto Safety
Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links.
使うべきか
品質と安全性
検出事項（2）
- HIGHTool poisoning patterns detected
- INFOTool description contains placeholder or incomplete textget_recent_hacks 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"crypto-safety": {
"url": "https://truedge.xyz/mcp"
}
}
}リモートエンドポイント
https://truedge.xyz/mcpstreamable-httpできること
ツール一覧
ツール（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.
入力スキーマ
{
"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.
入力スキーマ
{
"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.
入力スキーマ
{
"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.
入力スキーマ
{
"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.
入力スキーマ
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A website URL or domain, e.g. app.uniswap.org"
}
},
"required": [
"url"
]
}コミュニティ
エビデンス