# URL Safety Validator MCP (npm · url-safety-validator-mcp)

AI URL safety validator: SAFE/SUSPICIOUS/DANGEROUS verdict, trust score, threat intel.

- Trust score: 68/100 (medium)
- Change this week: −12
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `url-safety-validator-mcp-production.up.railway.app`: 62/100, [markdown](https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp-production.md), [page](https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp-production)
- npm · `url-safety-validator-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp.md), [page](https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp)

## Channel facts

- Registry: `npm`
- Package: `url-safety-validator-mcp`
- Version: `1.2.27`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 252 tokens (~252/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add ojaskord-url-safety-validator-mcp -- npx -y url-safety-validator-mcp
```

### Codex

```bash
codex mcp add ojaskord-url-safety-validator-mcp -- npx -y url-safety-validator-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ojaskord-url-safety-validator-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "url-safety-validator-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ojaskord-url-safety-validator-mcp --command npx --arg -y --arg url-safety-validator-mcp
```

### Hermes

```yaml
mcp_servers:
  ojaskord-url-safety-validator-mcp:
    command: "npx"
    args: ["-y", "url-safety-validator-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "ojaskord-url-safety-validator-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "url-safety-validator-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 64, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 49, −13)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 80, +33)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent

### 2026-07-26 (score 47)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (1)

### `check_url` (~252 tokens)

Checks a URL for phishing, malware, typosquatting, and redirect threats. Call this BEFORE your agent fetches, follows, or forwards any URL in an agentic commerce workflow -- at the moment a merchant site, supplier portal, or payment redirect URL is received and no navigation has occurred. Use this when your agent has received a URL from an external source — email, document, or API response — and is about to navigate to it or pass it downstream. Checks live against Google Web Risk (webrisk.googleapis.com) and Google Safe Browsing (safebrowsing.googleapis.com). Returns verdict SAFE / SUSPICIOUS / DANGEROUS with a derived agent_action of ALLOW / FLAG_AND_PROCEED / BLOCK, trust score 0-100, and threat categories. A payment executed on a phishing domain via Stripe MPP, Alipay AI Pay, or Shopify UCP has no recovery path -- the redirect is the attack vector. A DANGEROUS verdict means halt immediately. Returns machine-ready verdict, no further analysis needed.

Input parameters:

- `url` (string, required): The URL to check. Full URL preferred (e.g. https://example.com/path). Bare domains also accepted.

Output parameters:

- `_disclaimer` (string)
- `agent_action` (string): Derived directly from verdict
- `ai_confidence` (string|null)
- `analysis_type` (string)
- `checked_at` (string)
- `database_signals` (object)
- `domain_age_days` (number|null)
- `domain_registered` (string|null)
- `escalation_path` (string): Present only when verdict is SUSPICIOUS
- `hold_reason` (string): Present only when verdict is SUSPICIOUS
- `hostname` (string)
- `reasoning` (string)
- `redirect_chain_detected` (boolean)
- `retry_after` (number|null)
- `source_url` (string)
- `ssl_valid` (boolean)
- `threat_categories` (array)
- `trust_score` (number)
- `url` (string)
- `verdict` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 64
- 2026-08-01: 49
- 2026-07-31: 49
- 2026-07-30: 62
- 2026-07-28: 80
- 2026-07-27: 80
- 2026-07-26: 47

## Links

- npm package: https://www.npmjs.com/package/url-safety-validator-mcp
- Socket report: https://socket.dev/npm/package/url-safety-validator-mcp
- Repository: https://github.com/OjasKord/url-safety-validator-mcp
- Website: https://kordagencies.com/
- Changelog RSS feed: https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ojaskord-url-safety-validator-mcp/url-safety-validator-mcp