_ registry / mcp http-sse · checked 1h ago

trust-onion-scam-check

https://trustonion.io

Registry code: d50e2432b65bcb24

api record

Trust Onion Scam Check gives read-only access to Trust Onion Pulse (Voice Clone Scam Pulse): verified, published AI voice-clone and impersonation scam incidents, their statistics, editorial scam-pattern coverage, and the Three Words Check family verification protocol.

Use this server when a user asks about real AI voice-cloning, deepfake, or impersonation scam incidents, scam losses, how an AI scam type works, or what to do about a suspicious call, text, or video call.

endpoint
https://trustonion.io/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is trust-onion-scam-check live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is trust-onion-scam-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does trust-onion-scam-check have?
7 tools: assess_call_scenario, search_incidents, get_incident, explain_scam_type, get_verification_protocol, get_scam_stats, list_scam_types.
Is trust-onion-scam-check 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
458ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
3 open 4 never probed 3 of 7 classified

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.

  • get_verification_protocol open 1h ago

    Return Trust Onion's five-step family verification protocol for suspicious calls, texts, and video calls.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_scam_stats open 1h ago

    Return the current Trust Onion Pulse summary (all time, or for one incident year), including conservative loss classifications. Only explicitly-USD losses are summed.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1990
    }
  }
}
    arguments 11 lines
  • list_scam_types open 1h ago

    List the current editorial scam patterns and published article links, separately from verified incident statistics.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • assess_call_scenario unknown never probed

    Deterministically match a described call or text to current scam hubs, red flags, and the recommended verification step. No external LLM is used.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scenario"
  ],
  "properties": {
    "scenario": {
      "type": "string",
      "maxLength": 5000,
      "minLength": 3
    }
  }
}
    arguments 14 lines
  • search_incidents unknown never probed

    Search verified, published Trust Onion Pulse (Voice Clone Scam Pulse) incidents by attack type, victim type, country, outcome, incident year, publication date range, and keyword. Returns compact summaries (newest first by default), a total count, and nextCursor for the next page. Call get_incident with a slug for full detail.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "sort": {
      "enum": [
        "newest",
        "oldest",
        "incident_year_desc",
        "largest_loss"
      ],
      "type": "string"
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1990
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1
    },
    "since": {
      "type": "string"
    },
    "until": {
      "type": "string"
    },
    "cursor": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "keyword": {
      "type": "string"
    },
    "outcome": {
      "type": "string"
    },
    "attackType": {
      "type": "string"
    },
    "victimType": {
      "type": "string"
    }
  }
}
    arguments 49 lines
  • get_incident unknown never probed

    Get the full published Trust Onion case study for one verified incident by slug, including source reporting and prevention analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 13 lines
  • explain_scam_type unknown never probed

    Explain a documented editorial scam pattern with published article evidence, or a Trust Onion topic hub with warning signs and protection steps. Editorial coverage is not a verified incident count.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "scamType"
  ],
  "properties": {
    "scamType": {
      "type": "string",
      "minLength": 1
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d50e2432b65bcb24.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d50e2432b65bcb24/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d50e2432b65bcb24/badge.svg)](https://brick.blue/agent/d50e2432b65bcb24?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.