# domain_check_score_v1

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.

Agent View of the PolicyLayer registry record for `domain_check_score_v1`. HTML page: https://policylayer.com/tools/com-feranor-resilience/domain-check-score-v1

## Facts

- Tool: `domain_check_score_v1`
- Server: Feranor Resilience (`https://www.feranor.com/mcp`) — https://policylayer.com/tools/com-feranor-resilience.md
- Homepage: https://github.com/https://www.feranor.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | 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 an |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "domain_check_score_v1",
    "arguments": {
      "domain": "<domain>"
    }
  }
}
```

## Why domain_check_score_v1 is rated Low

domain_check_score_v1 performs a read-only assessment of publicly available domain security metrics (TLS, headers, DNS, response time). It returns scores and summary statistics but does not modify any data, execute code, delete resources, or trigger external operations.

From the tool's own definition: "Tool 'returns the overall resilience score' and 'tells you which categories are weak and how many issues they hold, but not what the issues are.' This is purely informational retrieval with 'no side effects' - it queries and reads data about a domain's public…"

## Use case

AI agents call domain_check_score_v1 to retrieve information from Feranor Resilience without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Feranor Resilience:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "domain_check_score_v1": {}
  }
}
```

## Other tools on Feranor Resilience (2)

- `domain_check_batch_v1` — Read — https://policylayer.com/tools/com-feranor-resilience/domain-check-batch-v1.md
- `domain_check_v1` — Read — https://policylayer.com/tools/com-feranor-resilience/domain-check-v1.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-feranor-resilience · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-feranor-resilience