verified.fyi
REMOTE · VERIFIED.FYI
Check whether a website is trustworthy: trust score, verdict, red flags and a citable report.
Available components
Last scanned (14 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 542 → 757 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “check_ip” functional
- 2 Nov 26 +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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://verified.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=verified.fyi | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6325884b5876a30ed3cdfcfbebfc8b8d476 |
| SANs: *.verified.fyi, verified.fyi | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verified.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | DS published | 6839, 24340 | 8, 8 | Verified |
| verified.fyi. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://plausible.io; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://plausible.io; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verified.fyi/mcp | Verified | 200 | |
| http (plaintext) | http://verified.fyi/mcp | HTTPS enforced | 308 | https://verified.fyi/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_ip Look up IP evidence ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | A bare IPv4 or IPv6 address, without a URL, port, CIDR prefix or zone identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | Citation line for this data. |
| blocklist_status | string | yes | 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 | yes | IPv4 or IPv6. |
| ip | string | yes | The canonical IPv4 or IPv6 address. |
| network | null|object | – | Network owner; omitted if unavailable, unmatched or not applicable. |
| report_url | string | yes | The full IP profile, including source dates and related websites. |
| scope | string | yes | – |
No examples provided.
check_website Check website trust ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url_or_domain | string | yes | The website to check: a bare domain such as example.com, or any URL on it. Only the hostname is assessed. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | Citation line for this data. |
| checked_at | string | – | When the report was generated. Reports are refreshed at most every 7 days. |
| domain | string | yes | 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 | yes | 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 | yes | 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). |
No examples provided.
list_research List verified.fyi research ~91
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | yes | Citation line for this data. |
| stories | null|array | yes | – |
No examples provided.
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.
remote · verified.fyi
claude mcp add --transport http fyi-verified-trust-reports 'https://verified.fyi/mcp'
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.