URL Safety Validator MCP Server

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

Remote serverstreamable-httpPython

What is the URL Safety Validator MCP server?

URL Safety Validator MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. AI URL safety validator: SAFE/SUSPICIOUS/DANGEROUS verdict, trust score, threat intel.

What you get

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.

  • 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

What the assistant can call

Once URL Safety Validator is connected, these are the calls the assistant has available:

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

Configuration and credentials

You will need 3 environment variables: ANTHROPIC_API_KEY, GOOGLE_WEB_RISK_API_KEY, YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. URL Safety Validator's toolset — LangGraph — is a fair guide to whether it matches your workflow. It is maintained by OjasKord; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against URL Safety Validator's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the url safety validator mcp server does with a few real requests.

Available tools

ToolWhat it does
LangGraphSame as LangChain above — langchain-mcp-adapters works with LangGraph natively.

How to install the URL Safety Validator MCP server

```json
{
  "mcpServers": {
    "url-safety-validator": {
      "command": "url-safety-validator-mcp",
      "env": {
        "ANTHROPIC_API_KEY": "your-key",
        "GOOGLE_WEB_RISK_API_KEY": "your-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ANTHROPIC_API_KEYCredential the server authenticates with.Yes
GOOGLE_WEB_RISK_API_KEYCredential the server authenticates with.Yes
YOUR_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use URL Safety Validator to LangGraph.

Frequently asked questions

It connects URL Safety Validator to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (LangGraph) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with URL Safety Validator directly.