Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Feranor Resilience

REMOTE · WWW.FERANOR.COM · SCANNED SEP 20

Scan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions.

Available components

0 this week 91 Trust /100
Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1154 tokens (~128/item across 9 items; 6 tools + 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Feranor Resilience MCP server?

Feranor Resilience is a hosted endpoint at https://www.feranor.com/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 · www.feranor.com

# add to Claude Code
claude mcp add --transport http com-feranor-resilience 'https://www.feranor.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-feranor-resilience": {
      "url": "https://www.feranor.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-feranor-resilience": {
      "type": "http",
      "url": "https://www.feranor.com/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-feranor-resilience --url 'https://www.feranor.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-feranor-resilience:
    url: "https://www.feranor.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-feranor-resilience": {
      "Transport": "http",
      "Url": "https://www.feranor.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-feranor-resilience -t streamable-http -u 'https://www.feranor.com/mcp'
// mcp.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 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.

  • 13 Sept 26 +5
    • Stability: fail → pass security
  • 12 Sept 26 −5
    • Stability: pass → fail security
  • 29 Aug 26 +1
    • Stability: 0.97 → pass security
  • 27 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.

  • 26 Aug 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
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability rose 1.

  • 24 Aug 26 +1

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

  • 14 Aug 26 0
    • Tool “purge_text_v1” was removed security
    • Tool “scan_text_v1” was removed security
    • Server version: 1.1.2 → 1.1.4 functional
    • New tool “text_purge_v1” functional
    • New tool “text_scan_v1” functional
Diagnostics

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 20 Sept 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

Background: What to check on a remote MCP endpoint →

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-6D005106CE45E0CD99305C5B6CB73D76' '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=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 6 exposed · ~1,073 tokens

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 →

Tool Tokens
domain_check_batch_v1 ~247

Runs the full resilience check on up to 100 domains in a single call and returns the same scored report for each one: TLS certificate, security headers, DNS redundancy, response time, with every individual finding. Use it to audit a portfolio, to rank a list of vendors, or to re-check a fleet after a config rollout. A domain that cannot be reached is returned with its own error rather than failing the batch, and it is still charged, because the crawl was attempted. Do not use it for a single domain: domain_check_v1 is simpler and costs the same for one. Private, internal and localhost hostnames and IP addresses are rejected. Price: $0.01 per domain, dropping to $0.005 from 100 domains, up to 100 per call. One payment covers the whole batch (x402, USDC on Base). No signup, no API key.

NameTypeReqDescription
domainsarrayyesBare domain names, apex or subdomain, for example ['example.com', 'www.example.org']. Between 1 and 100 entries. Scheme, path, port and query string are ignored if present. Duplicates are removed bef…
NameTypeReqDescription
evaluatedintegerNumber of distinct domains actually evaluated. This is the billed quantity.
evaluatedAtstringUTC timestamp of the batch.
requestedintegerNumber of domains in the request, before de-duplication.
resultsarray|nullOne entry per distinct domain, in no guaranteed order.
succeededintegerHow many produced a full report. The rest carry an error field.

No examples provided.

domain_check_score_batch_v1 ~210

Free. Returns the overall resilience score out of 100 for up to 100 public web domains, plus the score of each category and how many findings each one raised. Use it to triage a portfolio: rank a list of domains, confirm which ones are healthy, or decide which ones are worth pulling the full report on. It tells you which categories are weak and how many issues they hold, but not what the issues are. A domain that cannot be reached is returned with its own error rather than failing the batch. Duplicates are removed. For the individual findings and the prioritised remediation list on a whole list, use domain_check_batch_v1. For a single domain, use domain_check_score_v1. Free, no payment required.

NameTypeReqDescription
domainsarrayyesBare domain names, apex or subdomain, for example ['example.com', 'www.example.org']. Between 1 and 100 entries. Scheme, path, port and query string are ignored if present.
NameTypeReqDescription
evaluatedintegerNumber of distinct domains actually evaluated. This is the billed quantity.
evaluatedAtstringUTC timestamp of the batch.
requestedintegerNumber of domains in the request, before de-duplication.
resultsarray|nullOne entry per distinct domain, in no guaranteed order.
succeededintegerHow many produced a full report. The rest carry an error field.

No examples provided.

domain_check_score_v1 ~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.

NameTypeReqDescription
domainstringyesBare 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…
NameTypeReqDescription
categoriesarray|nullPer-category score and finding count. Finding details are not included.
detailsAvailableViastring|nullName of the tool returning the full findings behind these scores.
domainstring|nullDomain that was actually evaluated, after normalisation.
errorstring|null
evaluatedAtstringUTC timestamp of the evaluation.
measuredCategoriesintegerNumber of categories that could actually be measured. Compare two domains only when this matches.
scoreintegerWeighted resilience score out of 100.
successboolean

No examples provided.

domain_check_v1 ~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.

NameTypeReqDescription
domainstringyesBare 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…
NameTypeReqDescription
checksarray|null
domainstring|null
errorstring|null
evaluatedAtstring
noArchiveboolean
noIndexboolean
requestedDomainstring|null
scoreinteger
successboolean

No examples provided.

text_purge_v1 ~91

Removes invisible Unicode characters and replaces homoglyphs in a text string. Returns the cleaned text plus a before-and-after comparison. Use this tool after text_scan_v1 to fix flagged issues. Price: $0.01 per call (x402, USDC on Base). No signup, no API key.

NameTypeReqDescription
textstringyesThe text to clean of hidden characters and homoglyphs.
NameTypeReqDescription
charsRemovedinteger
homoglyphsReplacedinteger
purgedTextstring|null
reportAfterobject|null
reportBeforeobject|null

No examples provided.

text_scan_v1 ~77

Free. Scans a text string for invisible Unicode characters, homoglyphs, and normalization issues. Returns a risk score and a detailed report. Use this tool before text_purge_v1 to inspect suspicious content. Free, no payment required.

NameTypeReqDescription
textstringyesThe text to scan for hidden characters and homoglyphs.
NameTypeReqDescription
categoryCountsobject|null
flaggedCharsarray|null
homoglyphMatchesarray|null
isCleanboolean
isNormalizedboolean
normalizationFormstring|null
notesarray|null
riskScoreinteger

No examples provided.

Common questions

What is the Feranor Resilience MCP server?

Feranor Resilience is an MCP server listed in the public MCP registry as com.feranor/resilience. Scan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions. This page covers its hosted endpoint (https://www.feranor.com/mcp).

Is the Feranor Resilience MCP server safe to use?

Feranor Resilience scores 91 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 Feranor Resilience MCP server expose?

Feranor Resilience exposes 6 tools: text_purge_v1, domain_check_batch_v1, domain_check_v1, domain_check_score_v1, text_scan_v1, domain_check_score_batch_v1. Their descriptions and schemas cost roughly 1,073 tokens of context every time the server is loaded.

Does the Feranor Resilience MCP server require authentication?

No. We connected to Feranor Resilience without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Feranor Resilience MCP server still maintained?

Feranor Resilience is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.