Skip to main content
Glama
OjasKord

url-safety-validator-mcp

by OjasKord
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

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.

Related MCP server: unphurl-mcp

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

Source

Type

Coverage

Google Web Risk

Commercial API

Malware, phishing, unwanted software

Google Safe Browsing

Free

Malware, phishing, unwanted software (fallback when Web Risk key absent)

RDAP

Free

Domain registration date

Anthropic Claude

AI

Trust scoring and reasoning synthesis

Pricing

Tier

Calls

Price

Free

10/month

No API key needed

Starter

500-call bundle

$20

Pro

2,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)

npm install -g url-safety-validator-mcp
{
  "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)

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

LangChain (Python)

from langchain_mcp_adapters.client import MultiServerMCPClient
client = 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)

from agents import Agent, HostedMCPTool
agent = 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

{
  "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.

Available Tools

1 tool
check_urlAInspect

Call this BEFORE your agent fetches, visits, follows, or forwards any URL from an untrusted source — at the moment a URL is received from an email, scraped page, user input, document, API response, or redirect and has not yet been acted on. Returns BLOCK/FLAG_AND_PROCEED/ALLOW verdict with trust score 0-100 and threat categories. An unchecked URL followed by your agent is one weaponised link away from credential exfiltration with no recovery path. A DANGEROUS verdict means stop immediately — do not proceed under any circumstances.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to check. Full URL preferred (e.g. https://example.com/path). Bare domains also accepted.

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries the burden of behavioral disclosure. It describes the return values (BLOCK/FLAG_AND_PROCEED/ALLOW verdict with trust score and threat categories) and the consequence of not using it. No contradictions. Could mention if results are cached or if there are rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat long but every sentence adds value. It is front-loaded with the key instruction. Could be slightly more concise, but well-structured and no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description covers the essential behavioral aspects: when to use, return types, and severity. It omits detailed output structure but mentions verdict, score, and categories. Adequately complete for a simple tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter 'url' with 100% schema coverage. The schema description already clarifies accepted formats. The tool description adds context about untrusted sources but no new parameter details beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to check a URL from an untrusted source before acting on it. It uses a specific verb ('check') and resource ('URL'), and provides context about when to call it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use the tool: 'Call this BEFORE your agent fetches, visits, follows, or forwards any URL from an untrusted source...'. It also explains what to do with the verdict, and gives a strong warning about consequences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.2.14
    • First observedcheck_url
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

There is only one tool, so naming consistency is perfect. The name check_url follows a clear verb_noun pattern.

Tool Count4/5

A single tool is slightly minimal for URL safety validation, but it covers the core functionality well. A few additional tools for batch or domain-level checks could be useful, but the count is reasonable for a focused server.

Completeness4/5

The tool provides comprehensive URL checking with verdicts and trust scores. Minor gaps like batch processing or threat intel integration exist, but the core validation workflow is complete.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • unphurl-mcp

    123Ergo
    A
    license
    A
    quality
    D
    maintenance
    URL intelligence for AI agents. One URL in, structured security and data quality signals out across 7 dimensions. 13 tools, risk score 0-100 with 23 configurable weights.
    16
    110
    1
    MIT

  • PreClick MCP Server

    cybrlab-ai
    A
    license
    Not graded
    quality
    F
    maintenance
    A URL security scanner and MCP server that enables AI agents to analyze URLs for phishing, malware, and other threats before navigation, with optional intent alignment checks.
    6
    Apache 2.0

  • Nullcone MCP Server

    maco144
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time threat intelligence for AI agents, enabling checks on IPs, domains, URLs, hashes, CVEs, prompt-injection payloads, and malicious AI-skill/MCP-tool definitions against a free database of 890K+ IOCs.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OjasKord/url-safety-validator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server