URL Safety Validator MCP
NPM · URL-SAFETY-VALIDATOR-MCP · 2 COMPONENTS · SCANNED AUG 3
AI URL safety validator: SAFE/SUSPICIOUS/DANGEROUS verdict, trust score, threat intel.
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. How we score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · url-safety-validator-mcp
claude mcp add ojaskord-url-safety-validator-mcp -- npx -y url-safety-validator-mcp
codex mcp add ojaskord-url-safety-validator-mcp -- npx -y url-safety-validator-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ojaskord-url-safety-validator-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"url-safety-validator-mcp"
],
"enabled": true
}
}
} openclaw mcp add ojaskord-url-safety-validator-mcp --command npx --arg -y --arg url-safety-validator-mcp
mcp_servers:
ojaskord-url-safety-validator-mcp:
command: "npx"
args: ["-y", "url-safety-validator-mcp"] {
"mcpServers": {
"ojaskord-url-safety-validator-mcp": {
"command": "npx",
"args": [
"-y",
"url-safety-validator-mcp"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −13
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +33
- 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 functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
check_url ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to check. Full URL preferred (e.g. https://example.com/path). Bare domains also accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | yes | — |
| agent_action | string | yes | Derived directly from verdict |
| ai_confidence | string|null | — | — |
| analysis_type | string | — | — |
| checked_at | string | yes | — |
| 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 | yes | — |
| reasoning | string | — | — |
| redirect_chain_detected | boolean | — | — |
| retry_after | number|null | — | — |
| source_url | string | — | — |
| ssl_valid | boolean | — | — |
| threat_categories | array | — | — |
| trust_score | number | yes | — |
| url | string | yes | — |
| verdict | string | yes | — |
No examples provided.