# verified.fyi (remote · verified.fyi)

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

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `verified.fyi`: 73/100 (this document), [markdown](https://verifymcp.io/servers/fyi-verified-trust-reports/verified.md), [page](https://verifymcp.io/servers/fyi-verified-trust-reports/verified)

## Channel facts

- Endpoint: `https://verified.fyi/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 757 tokens (~252/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the verified.fyi MCP server?

verified.fyi is a hosted endpoint at https://verified.fyi/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "fyi-verified-trust-reports": {
      "url": "https://verified.fyi/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fyi-verified-trust-reports": {
      "type": "http",
      "url": "https://verified.fyi/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fyi-verified-trust-reports]
url = "https://verified.fyi/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fyi-verified-trust-reports": {
      "type": "remote",
      "url": "https://verified.fyi/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fyi-verified-trust-reports --url 'https://verified.fyi/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fyi-verified-trust-reports:
    url: "https://verified.fyi/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fyi-verified-trust-reports": {
      "Transport": "http",
      "Url": "https://verified.fyi/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fyi-verified-trust-reports -t streamable-http -u 'https://verified.fyi/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fyi-verified-trust-reports": {
      "type": "http",
      "url": "https://verified.fyi/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 72, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 542 → 757
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “check_ip”

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 70)

First indexed and scored.

## MCP tools (3)

### `check_ip` (~144 tokens)

Look up IP evidence

Look up an IPv4 or IPv6 address's basics, network owner (ASN, name and country), blocklist status and IP profile URL. Detailed evidence, source dates and related websites are on the linked profile. Uses local data only; never connects to the address or queues a scan. Blocklist status currently covers Spamhaus ASN-DROP: listed, not_listed or not_assessed. It assesses the entire network, and absence does not prove safety. Accepts a bare IP address; use check_website for domains or URLs.

Input parameters:

- `ip` (string, required): A bare IPv4 or IPv6 address, without a URL, port, CIDR prefix or zone identifier.

Output parameters:

- `attribution` (string): Citation line for this data.
- `blocklist_status` (string): listed, not_listed or not_assessed, from our local Spamhaus ASN-DROP snapshot. This checks the whole network; not_listed does not prove the IP is safe.
- `family` (string): IPv4 or IPv6.
- `ip` (string): The canonical IPv4 or IPv6 address.
- `network` (null|object): Network owner; omitted if unavailable, unmatched or not applicable.
- `report_url` (string): The full IP profile, including source dates and related websites.
- `scope` (string)

### `check_website` (~216 tokens)

Check website trust

Look up verified.fyi's independent trust report for a website: a 0-100 trust score, a verdict and a plain-English summary, drawn from automated checks (domain age, TLS, DNS, Google Web Risk, VirusTotal, blocklists, reviews, archive history, page content), with a link to the full report that lists every check. 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.

Input parameters:

- `url_or_domain` (string, required): The website to check: a bare domain such as example.com, or any URL on it. Only the hostname is assessed.

Output parameters:

- `attribution` (string): Citation line for this data.
- `checked_at` (string): When the report was generated. Reports are refreshed at most every 7 days.
- `domain` (string): The hostname that was checked.
- `parent_domain` (string): For a service endpoint, the established domain it belongs to. Check that domain for a trust verdict.
- `report_url` (string): The full report on verified.fyi, listing every check behind the verdict.
- `retry_after_seconds` (integer): For generating and rate_limited: seconds to wait before calling again.
- `score` (null|integer): Trust score from 0 (dangerous) to 100 (trusted). Omitted for Inactive sites and service endpoints.
- `status` (string): complete: the report is included. generating: a first scan is running, call again after retry_after_seconds. rate_limited: no report exists and new scans are paused, retry after retry_after_seconds o…
- `summary` (string): Plain-English assessment of the site.
- `verdict` (string): Trusted, Mostly safe, Use caution, Suspicious, Dangerous, Inactive (site unreachable), or Service endpoint (a backend address of parent_domain, not a website).

### `list_research` (~91 tokens)

List verified.fyi research

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.

Output parameters:

- `attribution` (string): Citation line for this data.
- `stories` (null|array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fyi-verified-trust-reports/verified#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70

## Common questions

### What is the verified.fyi MCP server?

verified.fyi is an MCP server listed in the public MCP registry as fyi.verified/trust-reports. Check whether a website is trustworthy: trust score, verdict, red flags and a citable report. This page covers its hosted endpoint (https://verified.fyi/mcp).

### Is the verified.fyi MCP server safe to use?

verified.fyi scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the verified.fyi MCP server expose?

verified.fyi exposes 3 tools: check_ip, check_website, list_research. Their descriptions and schemas cost roughly 451 tokens of context every time the server is loaded.

### Does the verified.fyi MCP server require authentication?

No. We connected to verified.fyi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the verified.fyi MCP server still maintained?

verified.fyi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the verified.fyi MCP server?

VerifyMCP ran 13 checks on verified.fyi, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://verified.fyi/mcp
- Website: https://verified.fyi/
- Changelog RSS feed: https://verifymcp.io/servers/fyi-verified-trust-reports/verified.xml
- Changelog JSON feed: https://verifymcp.io/servers/fyi-verified-trust-reports/verified/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fyi-verified-trust-reports/verified.json
- HTML version of this page: https://verifymcp.io/servers/fyi-verified-trust-reports/verified