mcpbeat Sign in

URL Safety Validator MCP Server

answering

URL Safety Validator MCP is answering right now. Last checked 9 min ago. 90 installs a week from npm. It exposes 1 tools. Last commit 7 Sep 2026.

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

Installs per day peak 69 · avg 16 · +26% w/w
a month agotoday
Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
353 ms
Response time
average over 24h
90
Installs / week
npm and PyPI

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 August 2026. No other catalogue keeps this.

7 Sep a tool changed version2 times that day
24 Aug a tool changed version
19 Aug a tool changed version
and 1 more, back to 19 August 2026

Nothing serious here today

Today is the operative word: we check URL Safety Validator MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add url-safety-validator-mcp --transport http https://url-safety-validator-mcp-production.up.railway.app
Settings → Connectors → Add custom connector, then paste this address
https://url-safety-validator-mcp-production.up.railway.app
~/.codex/config.toml
[mcp_servers.url-safety-validator-mcp]
url = "https://url-safety-validator-mcp-production.up.railway.app"
.cursor/mcp.json
{
  "mcpServers": {
    "url-safety-validator-mcp": {
      "url": "https://url-safety-validator-mcp-production.up.railway.app"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "url-safety-validator-mcp": {
      "type": "http",
      "url": "https://url-safety-validator-mcp-production.up.railway.app"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

url
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.

Endpoints

URLTransportStateLatencyChecked
https://url-safety-validator-mcp-production.up.railway.app streamable-http answering 329 ms 9 min ago

Alternatives to URL Safety Validator MCP

same job, measured the same way
Domain Trust
by trusterinfo

Website trust checks: 0-100 safety score, verdict and community reviews (truster.info).

43 installs/wk 3 tools answering
Entropy0dev
by entropy0dev

Entropy0 MCP server — source trust and URL safety tools for AI agents

40 installs/wk local only
Golem Intel
by golem

Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.

answering
Golem Security
by golem

Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.

answering
Scam Detection
by cautellus

Scam and phishing detection for AI agents: safe/warn/danger verdicts for URLs and messages.

3 tools answering
Verdict — Send anything. Get the truth.
by nrupala

Send anything. Get the truth — REAL, SUSPICIOUS or LIKELY SCAM verdicts on messages and links.

3 tools answering
satoshidata — Bitcoin entity intelligence
by satoshidata

Bitcoin entity and risk-exposure evidence for AI agents; keyless MCP, no risk_check score/verdict.

44 tools answering
Agentsafe
by andyscott88

Real-time URL trust scoring for AI agents. Blocks phishing and malicious sites.

41 installs/wk local only

URL Safety Validator MCP — questions

Answers built from our own checks of this server.

What can URL Safety Validator MCP do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_url. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is URL Safety Validator MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 353 ms. The bar chart above shows every period we have measured.
How do I connect URL Safety Validator MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does URL Safety Validator MCP need an API key?
No. URL Safety Validator MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is URL Safety Validator MCP?
It answers our handshake in 353 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use URL Safety Validator MCP?
The npm package url-safety-validator-mcp was installed 90 times in the last week. Week over week that is +26%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is URL Safety Validator MCP open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 1 stars on GitHub. The licence covers the code in the repository, not the hosted service at url-safety-validator-mcp-production.up.railway.app, which runs on its operator's own terms.