Truedge Crypto Safety
REMOTE · TRUEDGE.XYZ · SCANNED SEP 25
Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links.
Available components
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 575 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · truedge.xyz
claude mcp add --transport http xyz-truedge-crypto-safety 'https://truedge.xyz/mcp'
{
"mcpServers": {
"xyz-truedge-crypto-safety": {
"url": "https://truedge.xyz/mcp"
}
}
} {
"servers": {
"xyz-truedge-crypto-safety": {
"type": "http",
"url": "https://truedge.xyz/mcp"
}
}
} [mcp_servers.xyz-truedge-crypto-safety] url = "https://truedge.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-truedge-crypto-safety": {
"type": "remote",
"url": "https://truedge.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-truedge-crypto-safety --url 'https://truedge.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-truedge-crypto-safety:
url: "https://truedge.xyz/mcp" {
"McpServers": {
"xyz-truedge-crypto-safety": {
"Transport": "http",
"Url": "https://truedge.xyz/mcp"
}
}
} assistant mcp add xyz-truedge-crypto-safety -t streamable-http -u 'https://truedge.xyz/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://truedge.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=truedge.xyz | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f7fceed9fb247a130e57adb4d96cd48d |
| SANs: truedge.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of truedge.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| truedge.xyz. | present | 2371 | 13 | Verified |
| truedge.xyz. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://truedge.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://truedge.xyz/mcp | HTTPS enforced | 301 | https://truedge.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_address ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | A wallet/contract address (0x… EVM or a Solana base58 address) |
No output schema declared.
No examples provided.
check_contract_safety ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Token symbol |
No output schema declared.
No examples provided.
check_token_risk ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Token symbol, e.g. PEPE, BTC, ASTER |
No output schema declared.
No examples provided.
check_url ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A website URL or domain, e.g. app.uniswap.org |
No output schema declared.
No examples provided.
get_recent_hacks ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days (default 30, max 90) |
No output schema declared.
No examples provided.
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.