Truedge Crypto Safety

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

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
98%
이름 품질
100%
오염 위험
80%
권한 일치
100%
프로토콜 준수
100%

발견 사항 (2)

  • HIGHTool poisoning patterns detected
  • INFOTool description contains placeholder or incomplete textget_recent_hacks에서

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~648토큰 (도구 정의)
~396 B일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 0.51%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`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"
  ]
}

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 5개
검증됨버전이 기록되지 않음도구 5개