# DirFast (remote · pseo.rovy.tech)

DNS, TLS, HTTP and SEO checks, plus stateful change watches that diff a page over time.

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

## Components

- remote · `pseo.rovy.tech`: 60/100 (this document), [markdown](https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp.md), [page](https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp)

## Channel facts

- Endpoint: `https://pseo.rovy.tech/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 971 tokens (~64/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http tech-rovy-dirfast 'https://pseo.rovy.tech/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-rovy-dirfast": {
      "url": "https://pseo.rovy.tech/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-rovy-dirfast": {
      "type": "http",
      "url": "https://pseo.rovy.tech/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-rovy-dirfast]
url = "https://pseo.rovy.tech/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-rovy-dirfast": {
      "type": "remote",
      "url": "https://pseo.rovy.tech/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-rovy-dirfast --url 'https://pseo.rovy.tech/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-rovy-dirfast:
    url: "https://pseo.rovy.tech/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-rovy-dirfast": {
      "Transport": "http",
      "Url": "https://pseo.rovy.tech/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-rovy-dirfast -t streamable-http -u 'https://pseo.rovy.tech/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-rovy-dirfast": {
      "type": "http",
      "url": "https://pseo.rovy.tech/api/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 60, +1)

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

### 2026-11-03 (score 59, +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-02 (score 58, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 558 → 971
- [functional improvement] 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”

### 2026-11-01 (score 59)

First indexed and scored.

## MCP tools (15)

### `dns_lookup` (~78 tokens)

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.

Input parameters:

- `host` (string, required): Domain name, e.g. example.com

### `ssl_check` (~53 tokens)

Inspect a host's TLS certificate: issuer, subject, SAN list, expiry date and days remaining. Use to catch expiring or misconfigured certificates.

Input parameters:

- `host` (string, required): Hostname, e.g. example.com

### `http_head` (~59 tokens)

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.

Input parameters:

- `url` (string, required): URL or bare domain

### `security_headers` (~65 tokens)

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.

Input parameters:

- `url` (string, required): URL or bare domain

### `redirect_chain` (~60 tokens)

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.

Input parameters:

- `url` (string, required): URL or bare domain

### `seo_snapshot` (~60 tokens)

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.

Input parameters:

- `url` (string, required): URL or bare domain

### `robots_txt` (~47 tokens)

Fetch and parse a site's robots.txt into allow/disallow rules and declared sitemaps. Use before crawling a site to respect its policy.

Input parameters:

- `url` (string, required): URL or bare domain

### `ip_echo` (~34 tokens)

Return the caller's public IP address and reverse DNS name. Use to confirm which egress IP an agent or service is presenting.

### `site_audit` (~60 tokens)

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.

Input parameters:

- `url` (string, required): URL or bare domain

### `watch_create` (~154 tokens)

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.

Input parameters:

- `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, required): URL to watch

### `watch_check` (~48 tokens)

Force an immediate re-fetch of a watch instead of waiting for its interval. Returns status, whether the content changed, and the new hash.

Input parameters:

- `id` (string, required): Watch id from watch_create

### `watch_diff` (~49 tokens)

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.

Input parameters:

- `id` (string, required): Watch id

### `watch_history` (~64 tokens)

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.

Input parameters:

- `id` (string, required): Watch id
- `limit` (integer): Max snapshots to return, default 20

### `watch_list` (~29 tokens)

List all watches with their URL, selector, interval, last check time, check count and change count.

### `watch_delete` (~25 tokens)

Delete a watch and its stored snapshots.

Input parameters:

- `id` (string, required): Watch id

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp#diagnostics

## Score history

- 2026-11-05: 60
- 2026-11-04: 59
- 2026-11-03: 59
- 2026-11-02: 58
- 2026-11-01: 59

## Common questions

### 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 60 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://pseo.rovy.tech/api/mcp
- Website: https://pseo.rovy.tech/api/
- Changelog RSS feed: https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-rovy-dirfast/api-mcp