Feranor Resilience
REMOTE · WWW.FERANOR.COM · SCANNED AUG 3
Scores any web domain's public resilience: TLS, headers, DNS, response time. $0.01/call, no signup.
Available components
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 →
Endpoint Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.feranor.com
claude mcp add --transport http com-feranor-resilience https://www.feranor.com/mcp
[mcp_servers.com-feranor-resilience] url = "https://www.feranor.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-feranor-resilience": {
"type": "remote",
"url": "https://www.feranor.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-feranor-resilience --url https://www.feranor.com/mcp --transport streamable-http
mcp_servers:
com-feranor-resilience:
url: "https://www.feranor.com/mcp" {
"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.
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 Aug 26 +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.
- 2 Aug 26 +15
- Schema quality: 3700 → 224 ▲ functional
- Schema quality: unverified → excellent ▲ functional
- 1 Aug 26 −6
- 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 security
- Schema quality: fair → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 65
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 3 Aug 2026 · Probed https://www.feranor.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.feranor.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 25 Jun 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | c8aa7b02178f7c679e6527970a5cd3f |
| SANs: www.feranor.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
DNSSEC secure
Validation of www.feranor.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| feranor.com. | present | 2371 | 13 | Verified |
| www.feranor.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | script-src 'nonce-B12B4325B3FF98CA940769B1D2860ECF' 'strict-dynamic' 'unsafe-inline' 'self'; object-src 'none'; frame-ancestors 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.feranor.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.feranor.com/mcp | HTTPS enforced | 301 | https://www.feranor.com/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.
domain_check_score_v1 Domain Resilience Score ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
domain_check_v1 Domain Resilience Check ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array|null | — | — |
| domain | string|null | — | — |
| error | string|null | — | — |
| evaluatedAt | string | — | — |
| noArchive | boolean | — | — |
| noIndex | boolean | — | — |
| requestedDomain | string|null | — | — |
| score | integer | — | — |
| success | boolean | — | — |
No examples provided.