# Url Safety Checker — REST API endpoint `url-safety-checker`

Run offline heuristic safety checks on a URL and return a risk level (low/medium/high), a 0+ risk score, per-check results, and warnings. Checks HTTPS, suspicious TLDs, URL shorteners, phishing keyword patterns and brand lookalikes (e.g. paypa1 for paypal), raw IP hosts, deceptive domain characters, and excessive subdomains. No network requests — pattern analysis only.

- Category: security
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/url-safety-checker/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/url-safety-checker/
- Same tool on the other surface: https://findutils.com/mcp/url-safety-checker/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/url-safety-checker/execute \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/url-safety-checker
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `url` | string | yes | The URL to check. "https://" is assumed when no scheme is given. |

Example arguments (verified):

```json
{
  "url": "https://example.com"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:url_safety_checker`. Full MCP reference: https://findutils.com/mcp/url-safety-checker/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt