truedge
Registry code: 498cd6d439f86a23
Truedge risk-intelligence tools. Use check_token_risk / check_contract_safety for a token, get_recent_hacks for exploits. Informational only, never financial advice.
- endpoint
- https://truedge.xyz/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is truedge live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is truedge free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does truedge have?
- 5 tools: check_address, check_contract_safety, check_token_risk, check_url, get_recent_hacks.
- Is truedge safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 5 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- check a token for scam risk
- check a contract for honeypot flags
- check an address before sending funds
- check a url for crypto phishing
- list recent crypto hacks
- takes → gives
- text → data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_contract_safety reads open 24h ago
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", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Token symbol" } } }arguments 12 linescheck_token_risk reads open 13h ago
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", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "description": "Token symbol, e.g. PEPE, BTC, ASTER" } } }arguments 12 linescheck_url reads open 24h ago
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", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "A website URL or domain, e.g. app.uniswap.org" } } }arguments 12 linesget_recent_hacks reads open 24h ago
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)" } } }arguments 9 linescheck_address reads unknown never probed
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", "required": [ "address" ], "properties": { "address": { "type": "string", "description": "A wallet/contract address (0x… EVM or a Solana base58 address)" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id498cd6d439f86a23.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/498cd6d439f86a23/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/498cd6d439f86a23?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.