Skip to content

verified.fyi

fyi.verified/trust-reportsverified.fyistreamable-httpv1.0.0Scanned

Check whether a website is trustworthy: trust score, verdict, red flags and a citable report.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

2 tools

Changes things 1Claude Code: ask
  • check_websiteLook up verified.fyi's independent trust report for a website: a 0-100 trust score, a verdict, a plain-English summary and the main red flags, drawn from automated checks (domain a…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look up verified.fyi's independent trust report for a website: a 0-100 trust score, a verdict, a plain-English summary and the main red flags, drawn from automated checks (domain age, TLS, DNS, Google Web Risk, VirusTotal, blocklists, reviews, archive history, page content). Use it before visiting, buying from, signing up to, or entering personal or payment details on an unfamiliar site, or when someone asks whether a site, online shop, link or sender's domain is legitimate, safe or a scam. Accepts a bare domain or any URL. Known sites return instantly. A site never checked before is scanned on demand, which usually takes 20-60 seconds; if the scan isn't finished within about 25 seconds the result has status "generating" and retry_after_seconds.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check website trust
Only reads 1Show 1 read-only tool
  • list_researchList verified.fyi's published research: original data stories built from its dataset of website trust reports, such as how a domain's age relates to scam risk.Reads text others writeNo findings

    Why it is in this group

    • The name "list_research" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List verified.fyi's published research: original data stories built from its dataset of website trust reports, such as how a domain's age relates to scam risk. Each entry has the headline statistic, a short description, the publication date, and links to the story and its JSON dataset. Useful when someone asks for statistics or trends about scam, phishing or fraudulent websites, or wants citable data on online safety.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List verified.fyi research

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

Tools listed without sign-in

Looked at Oct 31, 2026, 23:19 UTC, unchanged since Oct 31, 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.

    Matched text

    https://verified.fyi/mcp: tools/list returned 2 tools to an anonymous client, including check_website (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trust-reports https://verified.fyi/mcp
claude mcp add --transport http trust-reports https://verified.fyi/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trust-reports__list_research"
    ],
    "ask": [
      "mcp__trust-reports__check_website"
    ],
    "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 trust-reports. Review it before you use it.

Capability tags behind 2 rules
  • mcp__trust-reports__check_website untrusted-input
  • mcp__trust-reports__list_research untrusted-input

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://anlyon.dev/api/v1/servers/fyi.verified/trust-reports/verify?hash=c0bae147d4720559dee7705142c80cbfa36079416948af3c3ca529d20ed89853" | jq -e '.changed == false'

Pinned hash c0bae147d472, from Oct 31, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/fyi.verified/trust-reports/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for fyi.verified/trust-reports
[![anlyon.dev](https://anlyon.dev/badge/fyi.verified/trust-reports.svg)](https://anlyon.dev/servers/fyi.verified/trust-reports)

Source: MCP Registry. Synced Oct 31, 2026, 22:17 UTC.