Feranor Resilience MCP MCP server

An official MCP server by Feranor that performs automated resilience and security checks on public domains. It provides scored reports covering TLS certificates, security headers, DNS redundancy, and response times. The server supports both single domain checks and batch processing, allowing agents to triage domains or retrieve detailed findings. It also includes tools to scan and purge hidden Unicode characters and homoglyphs from text strings to prevent spoofing attacks.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Feranor

MCP endpoint (Streamable HTTP)

https://www.feranor.com/mcp

Vendor documentation

What you can do with it

Scan a domain for TLS, DNS, and header security issues
Batch score multiple domains to triage security health
Detect and purge hidden Unicode characters from text
Automate unattended domain resilience monitoring

Tools advertised by the last live check:

text_purge_v1
domain_check_batch_v1
domain_check_v1
domain_check_score_v1
text_scan_v1
domain_check_score_batch_v1

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add feranor-resilience-mcp --url https://www.feranor.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable feranor-resilience-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "feranor-resilience-mcp": {
      "url": "https://www.feranor.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "feranor-resilience-mcp": {
      "type": "streamableHttp",
      "url": "https://www.feranor.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start feranor-resilience-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "feranor-resilience-mcp": {
      "type": "http",
      "url": "https://www.feranor.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http feranor-resilience-mcp https://www.feranor.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "feranor-resilience-mcp": {
      "url": "https://www.feranor.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "feranor-resilience-mcp": {
      "serverUrl": "https://www.feranor.com/mcp"
    }
  }
}

See all 957

Do you run Feranor Resilience MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing