# Truedge Crypto Safety (remote · truedge.xyz)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `truedge.xyz`: 65/100 (this document), [markdown](https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge.md), [page](https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge)

## Channel facts

- Endpoint: `https://truedge.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 575 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Truedge Crypto Safety MCP server?

Truedge Crypto Safety is a hosted endpoint at https://truedge.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-truedge-crypto-safety": {
      "type": "remote",
      "url": "https://truedge.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-truedge-crypto-safety --url 'https://truedge.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-truedge-crypto-safety:
    url: "https://truedge.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-truedge-crypto-safety": {
      "Transport": "http",
      "Url": "https://truedge.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-truedge-crypto-safety -t streamable-http -u 'https://truedge.xyz/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65)

First indexed and scored.

## MCP tools (5)

### `check_token_risk` (~87 tokens)

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 parameters:

- `symbol` (string, required): Token symbol, e.g. PEPE, BTC, ASTER

### `check_contract_safety` (~121 tokens)

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 parameters:

- `symbol` (string, required): Token symbol

### `get_recent_hacks` (~143 tokens)

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 parameters:

- `days` (number): Lookback window in days (default 30, max 90)

### `check_address` (~99 tokens)

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 parameters:

- `address` (string, required): A wallet/contract address (0x… EVM or a Solana base58 address)

### `check_url` (~85 tokens)

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 parameters:

- `url` (string, required): A website URL or domain, e.g. app.uniswap.org

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge#diagnostics

## Score history

- 2026-09-25: 65
- 2026-09-24: 65

## Common questions

### What is the Truedge Crypto Safety MCP server?

Truedge Crypto Safety is an MCP server listed in the public MCP registry as xyz.truedge/crypto-safety. Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links. This page covers its hosted endpoint (https://truedge.xyz/mcp).

### Is the Truedge Crypto Safety MCP server safe to use?

Truedge Crypto Safety scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Truedge Crypto Safety MCP server expose?

Truedge Crypto Safety exposes 5 tools: check_token_risk, check_contract_safety, get_recent_hacks, check_address, check_url. Their descriptions and schemas cost roughly 535 tokens of context every time the server is loaded.

### Does the Truedge Crypto Safety MCP server require authentication?

No. We connected to Truedge Crypto Safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Truedge Crypto Safety MCP server still maintained?

Truedge Crypto Safety is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://truedge.xyz/mcp
- Website: https://truedge.xyz/check-url
- Changelog RSS feed: https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge.json
- HTML version of this page: https://verifymcp.io/servers/xyz-truedge-crypto-safety/truedge