URL Safety Validator MCP

io.github.OjasKordPublished by GitHub account OjasKordv1.2.27Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

A URL safety checker that gives an assistant a single tool to screen links and return a SAFE, SUSPICIOUS or DANGEROUS verdict with a trust score before it fet.

What you can do
  • Check a single URL and get a verdict of SAFE, SUSPICIOUS or DANGEROUS with a 0-100 AI trust score.
  • Review threat categories such as phishing, malware, typosquatting, newly registered domains, suspicious redirects and brand impersonation.
  • Inspect supporting signals: SSL validity, domain registration age, redirect chain flags, and raw Google Web Risk and Safe Browsing results.
  • Read a short plain-English reasoning summary with a HIGH, MEDIUM or LOW confidence rating.
When to use it
Use it when an agent handles URLs from untrusted sources, such as links in emails, scraped pages, documents or API responses, and should decide whether to fetch, follow, store or forward them. It suits agentic commerce or content pipelines that want a gate before any navigation happens.
Requirements
Either the hosted remote endpoint or the npm package run locally with Node.js. Local use requires an ANTHROPIC_API_KEY; GOOGLE_WEB_RISK_API_KEY is optional and falls back to GOOGLE_SAFE_BROWSING_API_KEY. The remote service has a free tier of 10 calls per month, with paid bundles above that using an x-api-key header.
Before you install
The local setup asks for an Anthropic API key and Google API keys, which are secrets. Paid tiers cost money (for example $20 for 500 calls and $70 for 2,000 calls). URLs you check are sent to the provider and to Google and Anthropic services. The README states results are informational only and not a guarantee of safety.

Installation

In SourceWeft

  1. Open URL Safety Validator MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OjasKord%2Furl-safety-validator-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "url-safety-validator": {
      "type": "http",
      "url": "https://url-safety-validator-mcp-production.up.railway.app/"
    }
  }
}

README

[smithery badge]

URL Safety Validator MCP

[ToolRank]

Stop your agent from fetching a dangerous URL before it's too late.

Agents that process emails, scrape pages, or consume API responses encounter URLs from untrusted sources constantly. This server gives your agent a single call to gate every URL before it proceeds — returning a SAFE/SUSPICIOUS/DANGEROUS verdict backed by Google Web Risk, Google Safe Browsing, and AI analysis.

What It Does

One tool: check_url. One call returns:

  • Verdict: SAFE / SUSPICIOUS / DANGEROUS
  • AI trust score: 0–100 (0 = definitely dangerous, 100 = definitely safe)
  • Threat categories: phishing, malware, unwanted_software, typosquatting, newly_registered, suspicious_redirect, brand_impersonation
  • SSL status: valid or not
  • Domain age: registration date and age in days
  • Redirect chain flag: detected from URL parameters
  • Database signals: raw results from Google Web Risk and Google Safe Browsing
  • AI reasoning: 2–3 sentence plain-English explanation
  • AI confidence: HIGH / MEDIUM / LOW

AI-powered analysis — NOT a simple database lookup.

When to Call This Tool

Call check_url BEFORE your agent:

  • Fetches content from a URL found in an email
  • Visits a link extracted from a scraped page or document
  • Passes a URL to a browser tool or web scraper
  • Stores or forwards a URL from any untrusted source
  • Approves any outbound link in a content pipeline

If the verdict is DANGEROUS — halt. If SUSPICIOUS — flag for review. If SAFE — proceed.

Data Sources

SourceTypeCoverage
Google Web RiskCommercial APIMalware, phishing, unwanted software
Google Safe BrowsingFreeMalware, phishing, unwanted software (fallback when Web Risk key absent)
RDAPFreeDomain registration date
Anthropic ClaudeAITrust scoring and reasoning synthesis

Pricing

TierCallsPrice
Free10/monthNo API key needed
Starter500-call bundle$20
Pro2,000-call bundle$70

Remote Usage (No Install)

https://url-safety-validator-mcp-production.up.railway.app

Add x-api-key: YOUR_KEY header for Pro/Enterprise tiers. Leave blank for free tier.

Local Install (stdio)

bash
npm install -g url-safety-validator-mcp
json
{  "mcpServers": {    "url-safety-validator": {      "command": "url-safety-validator-mcp",      "env": {        "ANTHROPIC_API_KEY": "your-key",        "GOOGLE_WEB_RISK_API_KEY": "your-key"      }    }  }}

Harness Integration

Claude Code / Claude Desktop (.mcp.json)

json
{  "mcpServers": {    "url-safety-validator": {      "type": "http",      "url": "https://url-safety-validator-mcp-production.up.railway.app"    }  }}

LangChain (Python)

python
from langchain_mcp_adapters.client import MultiServerMCPClientclient = MultiServerMCPClient({    "url-safety-validator": {        "url": "https://url-safety-validator-mcp-production.up.railway.app",        "transport": "http"    }})tools = await client.get_tools()

OpenAI Agents SDK (Python)

python
from agents import Agent, HostedMCPToolagent = Agent(    name="Assistant",    tools=[HostedMCPTool(tool_config={        "type": "mcp",        "server_label": "url-safety-validator",        "server_url": "https://url-safety-validator-mcp-production.up.railway.app",        "require_approval": "never"    })])

LangGraph

Same as LangChain above — langchain-mcp-adapters works with LangGraph natively.

Example Response

json
{  "url": "https://suspicious-domain.xyz/login",  "hostname": "suspicious-domain.xyz",  "verdict": "DANGEROUS",  "trust_score": 4,  "ssl_valid": true,  "domain_age_days": 12,  "redirect_chain_detected": false,  "threat_categories": ["phishing", "newly_registered"],  "reasoning": "Domain registered 12 days ago and impersonates a financial institution's login page. Google Web Risk flags this as SOCIAL_ENGINEERING.",  "ai_confidence": "HIGH",  "analysis_type": "AI-powered -- NOT a simple database lookup"}

Legal

Results are for informational purposes only. Verdict is a risk signal — not a guarantee of safety or danger. We do not log or store your query content. Full terms: kordagencies.com/terms.html

Provider: Kord Agencies Pte Ltd, Singapore.

Source: README.md at commit 96fdf32

Tools

1

check_url

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.

Parametersurlrequired

Version history

1
  1. v1.2.27LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts