DirFast
REMOTE · PSEO.ROVY.TECH
DNS, TLS, HTTP and SEO checks, plus stateful change watches that diff a page over time.
Available components
Last scanned (23 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 15 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 971 tokens (~64/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "watch_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 3 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.
- 2 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 558 → 971 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: pass → 0 functional
- New tool “watch_check” functional
- New tool “watch_create” functional
- New tool “watch_delete” functional
- New tool “watch_diff” functional
- New tool “watch_history” functional
- New tool “watch_list” functional
- 1 Nov 26 59
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 4 Nov 2026 · Probed https://pseo.rovy.tech/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rovy.tech | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 408ec7f9800556ea0e78c4c475c409c6 |
| SANs: rovy.tech, *.rovy.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pseo.rovy.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| rovy.tech. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pseo.rovy.tech/api/mcp | Verified | 200 | |
| http (plaintext) | http://pseo.rovy.tech/api/mcp | Served over HTTP | 200 |
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 →
dns_lookup ~78
Resolve DNS records (A/AAAA/MX/TXT/NS/CNAME/SOA) for a domain, queried live against 1.1.1.1. Use when you need to verify a domain resolves, check mail routing, or inspect TXT/SPF records.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Domain name, e.g. example.com |
No output schema declared.
No examples provided.
http_head ~59
Fetch a URL and report HTTP status, total latency in ms, key response headers (server, cache, content-type) and the page title. Use as a cheap liveness/uptime probe.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
ip_echo ~34
Return the caller's public IP address and reverse DNS name. Use to confirm which egress IP an agent or service is presenting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
redirect_chain ~60
Follow a URL through its full redirect chain (up to 8 hops) and report each hop's status code and Location target. Use to detect redirect loops or http->https and www canonicalisation issues.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
robots_txt ~47
Fetch and parse a site's robots.txt into allow/disallow rules and declared sitemaps. Use before crawling a site to respect its policy.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
security_headers ~65
Audit HTTP security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) and return a 0-100 score with the missing ones listed.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
seo_snapshot ~60
Extract on-page SEO signals from a URL: title, meta description, canonical, robots meta, h1 count, Open Graph tags, and word count. Use for quick SEO triage without a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
site_audit ~60
Run the full audit bundle in one call: SSL + security headers + redirect chain + HTTP head + DNS + SEO. Use when you need a complete health picture of a site rather than one signal.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL or bare domain |
No output schema declared.
No examples provided.
ssl_check ~53
Inspect a host's TLS certificate: issuer, subject, SAN list, expiry date and days remaining. Use to catch expiring or misconfigured certificates.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname, e.g. example.com |
No output schema declared.
No examples provided.
watch_check ~48
Force an immediate re-fetch of a watch instead of waiting for its interval. Returns status, whether the content changed, and the new hash.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Watch id from watch_create |
No output schema declared.
No examples provided.
watch_create ~154
Start watching a URL for changes. The server stores a snapshot, re-fetches on your interval, and reports a unified diff when the extracted text changes. Use this when you need to know if something changed since last time - an ordinary fetch cannot tell you that. Selector forms: css:#id, css:.class, css:tag, regex:PATTERN, json:$.path, or empty for whole body text.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | integer | – | Seconds between checks, 300 to 604800. Default 3600. |
| selector | string | – | What part to compare, e.g. css:#price or json:$.status. Empty = whole page text. |
| url | string | yes | URL to watch |
No output schema declared.
No examples provided.
watch_delete ~25
Delete a watch and its stored snapshots.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Watch id |
No output schema declared.
No examples provided.
watch_diff ~49
Get the unified diff of the most recent detected change for a watch. Use after watch_check reports changed=true, or to report what changed since you last looked.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Watch id |
No output schema declared.
No examples provided.
watch_history ~64
List a watch's snapshot timeline: timestamps, content hashes, HTTP status and which snapshots were detected as changes. Use to see how often a page actually changes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Watch id |
| limit | integer | – | Max snapshots to return, default 20 |
No output schema declared.
No examples provided.
watch_list ~29
List all watches with their URL, selector, interval, last check time, check count and change count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the DirFast MCP server?
DirFast is a hosted endpoint at https://pseo.rovy.tech/api/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 · pseo.rovy.tech
claude mcp add --transport http tech-rovy-dirfast 'https://pseo.rovy.tech/api/mcp'
What is the DirFast MCP server?
DirFast is an MCP server listed in the public MCP registry as tech.rovy/dirfast. DNS, TLS, HTTP and SEO checks, plus stateful change watches that diff a page over time. This page covers its hosted endpoint (https://pseo.rovy.tech/api/mcp).
Is the DirFast MCP server safe to use?
DirFast scores 59 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 DirFast MCP server expose?
DirFast exposes 15 tools: dns_lookup, ssl_check, http_head, security_headers, redirect_chain, and 10 more. Their descriptions and schemas cost roughly 885 tokens of context every time the server is loaded.
Does the DirFast MCP server require authentication?
No. We connected to DirFast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DirFast MCP server still maintained?
DirFast is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.