mcp-registry/xyz.truedge/crypto-safety · v1.0.0
As of 2026-10-26 16:45 UTC, the Truedge Crypto Safety MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Free crypto scam checks: token and contract risk, scam or sanctioned addresses, phishing links.
Point your MCP client at this streamable-http endpoint: https://truedge.xyz/mcp
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,593 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.truedge%2Fcrypto-safety/fixes
{
"name": "check_address",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "A wallet/contract address (0x… EVM or a Solana base58 address)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_contract_safety",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Token symbol"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_token_risk",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"symbol"
],
"properties": {
"symbol": {
"type": "string",
"description": "Token symbol, e.g. PEPE, BTC, ASTER"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.truedge/crypto-safety"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/xyz.truedge/crypto-safety"}) over MCP.
get_recent_hacks ~189 tokenscheck_contract_safety ~176 tokenscheck_address ~135 tokenscheck_url ~122 tokenscheck_token_risk ~118 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fxyz.truedge%2Fcrypto-safety?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fxyz.truedge%2Fcrypto-safety?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.truedge%2Fcrypto-safety.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.truedge%2Fcrypto-safety.svg :target: https://glimind.com/server/mcp-registry%2Fxyz.truedge%2Fcrypto-safety?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a17a9bbf3107e1e3…, first seen 2026-10-17, included at leaf 16792 of 74,198. Version history · verify what your client received.
Compare: most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:45 UTC, the Truedge Crypto Safety MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Truedge Crypto Safety MCP server advertises 5 tools, including check_address, check_contract_safety, check_token_risk, check_url, get_recent_hacks.
Point your MCP client at this streamable-http endpoint: https://truedge.xyz/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.