Trust Onion Scam Check MCP Server

by trustonion Your server? Claim it

answering

Trust Onion Scam Check is answering right now. Last checked 1 min ago. It exposes 7 tools.

Verified AI voice-clone scam incidents, loss stats, and a family verification protocol. Keyless.

Uptime history 15 days of history · worst day 98%

15 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

442 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Trust Onion Scam Check every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add scam-check --transport http https://trustonion.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://trustonion.io/mcp

~/.codex/config.toml

[mcp_servers.scam-check]
url = "https://trustonion.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "scam-check": {
      "url": "https://trustonion.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "scam-check": {
      "type": "http",
      "url": "https://trustonion.io/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

scam

get_scam_stats

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

list_scam_types

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

assess

assess_call_scenario

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

explain

explain_scam_type

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.

incident

get_incident

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

incidents

search_incidents

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.

verification

get_verification_protocol

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

Endpoints

URL	Transport	State	Latency	Checked
https://trustonion.io/mcp	streamable-http	answering	429 ms	1 min ago

Alternatives to Trust Onion Scam Check

same job, measured the same way

Pagerduty

by mcparmory

Manage incidents, on-call schedules, escalation policies, and alert notifications

233 installs/wk local only

AccordTrace

by kosta1985

Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.

9 tools answering

AI Incident Reporting MCP

by csoai-org

AI Incident Reporting Compliance MCP. Unified classification + reporting-clock tracker across EU...

205 installs/wk local only

Devops Status MCP Server

by cyanheads

Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.

152 installs/wk 7 tools answering

Kaminari Ad

by kaminari-ad

Real-device ad verification: malvertising and cloaking scans, AI policies, alerts, webhooks.

88 installs/wk answering

API Status Check

by shibley

Live status probes plus published uptime and incident history for 280+ APIs and cloud services.

8 tools answering

Runvouch

by runvouch

Watchdog for unattended AI agents: alerts, evidence checks and a verifiable proof per run.

7 tools answering

Verdict: the due-diligence house for DeFi

by charles-verdict

Verdict, the due-diligence house for DeFi: keyless ratings, methodology and a hack incident feed.

26 installs/wk local only

Trust Onion Scam Check — questions

Answers built from our own checks of this server.

What can Trust Onion Scam Check do?

It exposes 7 tools, read directly from the server on our last check. Among them: assess_call_scenario, explain_scam_type, get_incident, get_scam_stats, get_verification_protocol, list_scam_types and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Trust Onion Scam Check working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 442 ms. The bar chart above shows every period we have measured.

How do I connect Trust Onion Scam Check?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Trust Onion Scam Check need an API key?

No. Trust Onion Scam Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Trust Onion Scam Check?

It answers our handshake in 442 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.