Trust Onion Scam Check MCP server
io.trustonion/scam-checktrustonion.iostreamable-httpv1.1.0Scanned
Verified AI voice-clone scam incidents, loss stats, and a family verification protocol. Keyless.
7 tools: 1 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Trust Onion Scam Check MCP server can do
The Trust Onion Scam Check MCP server is published by trustonion.io, a domain the MCP Registry verified. It has 7 tools. It can create or change data (1 tool: assess_call_scenario), but cannot delete data. 6 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 1Claude Code: ask
assess_call_scenarioDeterministically match a described call or text to current scam hubs, red flags, and the recommended verification step.1 finding
Why it is in this group
- The name "assess_call_scenario" says "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "assess_call_scenario" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "assess_call_scenario" says "call": a word for a change.
Description, as the server wrote it Deterministically match a described call or text to current scam hubs, red flags, and the recommended verification step. No external LLM is used.
Annotations the server declares
- title: Assess a suspicious call or message
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
explain_scam_typeExplain a documented editorial scam pattern with published article evidence, or a Trust Onion topic hub with warning signs and protection steps.No findings
Why it is in this group
- The name "explain_scam_type" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain an AI scam type
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_incidentGet the full published Trust Onion case study for one verified incident by slug, including source reporting and prevention analysis.No findings
Why it is in this group
- The name "get_incident" says "get": a word for reading.
Description, as the server wrote it Get the full published Trust Onion case study for one verified incident by slug, including source reporting and prevention analysis.
Annotations the server declares
- title: Get a verified incident
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_scam_statsReturn the current Trust Onion Pulse summary (all time, or for one incident year), including conservative loss classifications.No findings
Why it is in this group
- The name "get_scam_stats" says "get": a word for reading.
Description, as the server wrote it Return the current Trust Onion Pulse summary (all time, or for one incident year), including conservative loss classifications. Only explicitly-USD losses are summed.
Annotations the server declares
- title: Get current scam statistics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_verification_protocolReturn Trust Onion's five-step family verification protocol for suspicious calls, texts, and video calls.No findings
Why it is in this group
- The name "get_verification_protocol" says "get": a word for reading.
Description, as the server wrote it Return Trust Onion's five-step family verification protocol for suspicious calls, texts, and video calls.
Annotations the server declares
- title: Get the Three Words Check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_scam_typesList the current editorial scam patterns and published article links, separately from verified incident statistics.No findings
Why it is in this group
- The name "list_scam_types" says "list": a word for reading.
Description, as the server wrote it List the current editorial scam patterns and published article links, separately from verified incident statistics.
Annotations the server declares
- title: List documented scam patterns
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_incidentsSearch verified, published Trust Onion Pulse (Voice Clone Scam Pulse) incidents by attack type, victim type, country, outcome, incident year, publication date range, and keyword.No findings
Why it is in this group
- The name "search_incidents" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search verified scam incidents
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://trustonion.io/mcp: tools/list returned 7 tools to an anonymous client, including assess_call_scenario (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "assess_call_scenario" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "assess_call_scenario" says "call": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http scam-check https://trustonion.io/mcpclaude mcp add --transport http scam-check https://trustonion.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__scam-check__search_incidents",
"mcp__scam-check__get_incident",
"mcp__scam-check__get_scam_stats",
"mcp__scam-check__explain_scam_type",
"mcp__scam-check__list_scam_types",
"mcp__scam-check__get_verification_protocol"
],
"ask": [
"mcp__scam-check__assess_call_scenario"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as scam-check. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.trustonion/scam-check/verify?hash=a8462f9cfdc811d450def66e1f5692a00da42524dd5f183dab7b5ba01f8bf727" | jq -e '.changed == false'Pinned hash a8462f9cfdc8, from Nov 18, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.trustonion/scam-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.trustonion/scam-check)Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.
Trust Onion Scam Check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Trust Onion Scam Check MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Trust Onion Scam Check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Trust Onion Scam Check MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Trust Onion Scam Check MCP server have?
- 7 tools: 1 write, 6 read. assess_call_scenario, search_incidents, get_incident, get_scam_stats, explain_scam_type, list_scam_types and get_verification_protocol.
Does the Trust Onion Scam Check MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Trust Onion Scam Check MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Trust Onion Scam Check MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.