# DirFast

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

- name: tech.rovy/dirfast
- version: 0.2.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 77/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/tech.rovy%2Fdirfast
- tools: https://api.protogrid.dev/v1/servers/tech.rovy%2Fdirfast/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-12d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 77/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 75 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: http_head (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); ip_echo (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); watch_check (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,316 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 83 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 16, about 1,316 tokens to load them all
- tool set hash: e9bacb99d98fe176c338dd428eba5377
- tools last changed: 2026-11-12T03:07:32.609Z
- badge: [![protogrid quality](https://protogrid.dev/badge/tech.rovy/dirfast.svg)](https://protogrid.dev/servers/tech.rovy/dirfast)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-12 `bounty_check` changed (description)
  - before: Before writing a patch for a GitHub 'bounty', check whether that repo has ever merged anyone's work. Returns the merged/total PR ratio, a verdict (COLLECTOR when a repo takes 50+ PRs and merges none), and any trap signals in its open issues - such as instructions asking contributors to paste their system prompt, home directory or runtime into a public file. Use this whenever a bounty promises money; an advertised amount costs the publisher nothing, a merge does.
  - after: Before writing a patch for a GitHub 'bounty', check whether that repo has ever merged anyone's work. Returns the merged/total PR ratio, a verdict, and any trap signals in its open issues - such as instructions asking contributors to paste their system prompt, home directory or runtime into a public file. Verdicts: CLOSED-LOOP means the issues state in writing that only the issue author may submit a PR, so outside work is unclaimable no matter what is advertised; COLLECTOR means 50+ PRs and zero merges while advertising payment. Use this whenever a bounty promises money; an advertised amount costs the publisher nothing, a merge does.
- 2026-11-11 `bounty_check` added
  - Before writing a patch for a GitHub 'bounty', check whether that repo has ever merged anyone's work. Returns the merged/total PR ratio, a verdict (COLLECTOR when a repo takes 50+ PRs and merges none), and any trap signals in its open issues - such as instructions asking contributors to paste their system prompt, home directory or runtime into a public file. Use this whenever a bounty promises money; an advertised amount costs the publisher nothing, a merge does.
- 2026-11-02 `watch_delete` added
  - Delete a watch and its stored snapshots.
- 2026-11-02 `watch_list` added
  - List all watches with their URL, selector, interval, last check time, check count and change count.
- 2026-11-02 `watch_history` added
  - 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.
- 2026-11-02 `watch_diff` added
  - 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.
- 2026-11-02 `watch_check` added
  - Force an immediate re-fetch of a watch instead of waiting for its interval. Returns status, whether the content changed, and the new hash.
- 2026-11-02 `watch_create` added
  - 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.

Full history: https://api.protogrid.dev/v1/servers/tech.rovy%2Fdirfast/changes

## Remotes

- https://pseo.rovy.tech/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (16)

- `bounty_check`: Before writing a patch for a GitHub 'bounty', check whether that repo has ever merged anyone's work. Returns the merged/total PR ratio, a verdict, and any trap signals in its open issues - such as instructions asking contributors to paste their system prompt, home directory or runtime into a public file. Verdicts: CLOSED-LOOP means the issues state in writing that only the issue author may submit a PR, so outside work is unclaimable no matter what is advertised; COLLECTOR means 50+ PRs and zero merges while advertising payment. Use this whenever a bounty promises money; an advertised amount costs the publisher nothing, a merge does.
- `dns_lookup`: 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.
- `http_head`: 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.
- `ip_echo`: Return the caller's public IP address and reverse DNS name. Use to confirm which egress IP an agent or service is presenting.
- `redirect_chain`: 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.
- `robots_txt`: Fetch and parse a site's robots.txt into allow/disallow rules and declared sitemaps. Use before crawling a site to respect its policy.
- `security_headers`: 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.
- `seo_snapshot`: 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.
- `site_audit`: 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.
- `ssl_check`: Inspect a host's TLS certificate: issuer, subject, SAN list, expiry date and days remaining. Use to catch expiring or misconfigured certificates.
- `watch_check`: Force an immediate re-fetch of a watch instead of waiting for its interval. Returns status, whether the content changed, and the new hash.
- `watch_create`: 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.
- `watch_delete`: Delete a watch and its stored snapshots.
- `watch_diff`: 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.
- `watch_history`: 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.
- `watch_list`: List all watches with their URL, selector, interval, last check time, check count and change count.