# Feranor Resilience (remote · www.feranor.com)

Scores any web domain's public resilience: TLS, headers, DNS, response time. $0.01/call, no signup.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.feranor.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-feranor-resilience/www.md), [page](https://verifymcp.io/servers/com-feranor-resilience/www)

## Channel facts

- Endpoint: `https://www.feranor.com/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-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 448 tokens (~224/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-feranor-resilience https://www.feranor.com/mcp
```

### Codex

```toml
[mcp_servers.com-feranor-resilience]
url = "https://www.feranor.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-feranor-resilience": {
      "type": "remote",
      "url": "https://www.feranor.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-feranor-resilience --url https://www.feranor.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-feranor-resilience:
    url: "https://www.feranor.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-feranor-resilience": {
      "type": "http",
      "url": "https://www.feranor.com/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-08-03 (score 75, +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-08-02 (score 74, +15)

- [functional improvement] Schema quality: 3700 → 224
- [functional improvement] Schema quality: unverified → excellent

### 2026-08-01 (score 59, −6)

- [security] Tool “domain_check_score_v1” rewrote its description, which is the text the model reads
- [security] Tool “domain_check_v1” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: fair → unverified

### 2026-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65)

First indexed and scored.

## MCP tools (2)

### `domain_check_v1` (~280 tokens)

Domain Resilience Check

Measures how resilient a public web domain is from the outside and returns a weighted score out of 100, a per-category breakdown, and prioritised findings explaining what to fix first. Use it to audit a domain you do not control, to verify a fix after deployment, or to compare several domains on the same scale. Covers TLS certificate validity and protocol version, HTTP to HTTPS redirection, HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, cache directives, response time, DNS redundancy, IPv6 availability, CDN detection and software version disclosure. Everything is read from the public internet: nothing is authenticated, no ports are scanned, and no credentials are needed. Do not use it for private, internal, or localhost hostnames, for IP addresses, or to test a service you need logged-in access to. For a free score without the detailed findings, use domain_check_score_v1 instead. Price: $0.01 per call (x402, USDC on Base). No signup, no API key.

Input parameters:

- `domain` (string, required): Bare domain name, apex or subdomain, for example 'example.com' or 'www.example.com'. Scheme, path, port and query string are ignored if present. IP addresses and private or localhost hostnames are re…

Output parameters:

- `checks` (array|null)
- `domain` (string|null)
- `error` (string|null)
- `evaluatedAt` (string)
- `noArchive` (boolean)
- `noIndex` (boolean)
- `requestedDomain` (string|null)
- `score` (integer)
- `success` (boolean)

### `domain_check_score_v1` (~168 tokens)

Domain Resilience Score

Free. Returns the overall resilience score out of 100 for a public web domain, plus the score of each category and how many findings each one raised. Use it to triage: to rank a list of domains, to confirm a domain is healthy, or to decide whether the detailed report is worth pulling. It tells you which categories are weak and how many issues they hold, but not what the issues are. For the individual findings and the prioritised remediation list, use domain_check_v1. Free, no payment required.

Input parameters:

- `domain` (string, required): Bare domain name, apex or subdomain, for example 'example.com' or 'www.example.com'. Scheme, path, port and query string are ignored if present. IP addresses and private or localhost hostnames are re…

Output parameters:

- `categories` (array|null): Per-category score and finding count. Finding details are not included.
- `detailsAvailableVia` (string|null): Name of the tool returning the full findings behind these scores.
- `domain` (string|null): Domain that was actually evaluated, after normalisation.
- `evaluatedAt` (string): UTC timestamp of the evaluation.
- `measuredCategories` (integer): Number of categories that could actually be measured. Compare two domains only when this matches.
- `score` (integer): Weighted resilience score out of 100.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-feranor-resilience/www#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 74
- 2026-08-01: 59
- 2026-07-31: 65
- 2026-07-30: 65

## Links

- Remote endpoint: https://www.feranor.com/mcp
- Website: https://www.feranor.com/tools/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-feranor-resilience/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-feranor-resilience/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-feranor-resilience/www