
Trust Onion MCP server
Which MCP servers are Trust Onion's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry nameio.trustonion/scam-checkverified in the MCP registry
The registry name sits under trustonion.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools7
- Server calls itselftrust-onion-scam-check
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 88 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- Parameters are untyped or undescribed in 5 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score96 of 100answers 100 · definitions 88 · context 100 · connects 100
- Answered100% of days8 of 8 daily checks
- Median first answer294 ms
- Space in an agent's context≈ 699 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsB · 88 of 100
- Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 5 of 7
What an agent can do with it
- not sure · verify a caller's identity with rotating codewords
- not sure · confirm a friend's request for money before sending
- cannot · prove identity to a contact with a signed selfie
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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. Returns compact summaries (newest first by default), a…
get_incidentGet the full published Trust Onion case study for one verified incident by slug, including source reporting and prevention analysis.
get_scam_statsReturn the current Trust Onion Pulse summary (all time, or for one incident year), including conservative loss classifications. Only explicitly-USD losses are summed.
explain_scam_typeExplain 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.
list_scam_typesList the current editorial scam patterns and published article links, separately from verified incident statistics.
get_verification_protocolReturn Trust Onion's five-step family verification protocol for suspicious calls, texts, and video calls.
assess_call_scenarioDeterministically match a described call or text to current scam hubs, red flags, and the recommended verification step. No external LLM is used.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"scam-check": {
"type": "http",
"url": "https://trustonion.io/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http trustonion https://trustonion.io/mcpclaude.ai, ChatGPT and other clients: add https://trustonion.io/mcp as a custom connector in the settings.
OpenAPI spec
8 paths, read 2026-10-27. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.