URL Safety Validator MCP
AI URL safety validator: SAFE/SUSPICIOUS/DANGEROUS verdict, trust score, threat intel.The vendor's description, from its MCP Registry listing.
- Warning: The server only speaks the first MCP version (2024-11-05).
- Warning: 1 of 1 tools do not say whether they can change things.
Nothing failed, but there is something to know or fix. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit
- Does it work?
- YesConnected in 187 ms.
- Sign-up?
- None neededIt answered without any account or key.
- Can it change things?
- Doesn't sayIts tools do not say whether they only read, so treat them as able to change things.
https://url-safety-validator-mcp-production.up.railway.appSource code Website Streamable HTTP · protocol 2024-11-05 · server version 1.2.40
What we checked
Security
Passed: Connections are encrypted (HTTPS).
Passed: No hidden instructions found in tool text.
Safety labels
Warning: 1 of 1 tools do not say whether they can change things.
MCP lets a server label each tool as read-only or destructive, so clients can ask the user before risky calls. Unlabelled tools are treated as able to change things.
- check_url
Tools
Passed: 1 tool listed.
Passed: Every tool describes its inputs with a valid schema.
Protocol
Warning: The server only speaks the first MCP version (2024-11-05).
Newer versions (latest 2025-11-25) add tool safety labels, structured output and a safer authorization model.
Passed: The MCP handshake works (Streamable HTTP).
Passed: Unknown requests are refused.
Connection
Passed: The server responds.
Tools (1)
As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.
- check_urlChecks 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…Doesn't say
Audit history
- Nov 13Warnings
What we sent
Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.
| Request | Answer | Time |
|---|---|---|
| initialize | HTTP 200 | 187 ms |
| initialized | HTTP 204 | 144 ms |
| tools/list | HTTP 200 | 105 ms |
| resources/list | HTTP 200 | 88 ms |
| prompts/list | HTTP 200 | 84 ms |
| unknown-method | HTTP 200 | 88 ms |
Run this server, or disagree with the result?
Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.
{
"mcpServers": {
"io-github-ojaskord-url-safety-validator-mcp": {
"type": "http",
"url": "https://url-safety-validator-mcp-production.up.railway.app"
}
}
}{
"server": {
"name": "io.github.OjasKord/url-safety-validator-mcp",
"title": "URL Safety Validator MCP",
"url": "https://url-safety-validator-mcp-production.up.railway.app",
"transport": "streamable-http",
"topics": [
"Cyber Threat"
],
"repository": "https://github.com/OjasKord/url-safety-validator-mcp",
"website": "https://kordagencies.com",
"inRegistry": true
},
"audit": {
"slug": "io-github-ojaskord-url-safety-validator-mcp",
"url": "https://url-safety-validator-mcp-production.up.railway.app",
"auditedAt": "2026-11-13T16:27:10.567Z",
"firstAuditedAt": "2026-11-13T15:59:00.069Z",
"auditor": "1.0.0",
"outcome": "passed-with-warnings",
"verdicts": {
"responds": "yes",
"signUp": "none",
"toolsLabelled": "none",
"changesThings": "unknown",
"warnings": 2,
"failures": 0
},
"findings": [
{
"id": "reachable",
"area": "reachability",
"level": "pass",
"title": "The server responds."
},
{
"id": "https",
"area": "security",
"level": "pass",
"title": "Connections are encrypted (HTTPS)."
},
{
"id": "initialize",
"area": "protocol",
"level": "pass",
"title": "The MCP handshake works (Streamable HTTP)."
},
{
"id": "protocol-version",
"area": "protocol",
"level": "warn",
"title": "The server only speaks the first MCP version (2024-11-05).",
"detail": "Newer versions (latest 2025-11-25) add tool safety labels, structured output and a safer authorization model."
},
{
"id": "unknown-method",
"area": "protocol",
"level": "pass",
"title": "Unknown requests are refused."
},
{
"id": "tools-list",
"area": "tools",
"level": "pass",
"title": "1 tool listed."
},
{
"id": "tool-schemas",
"area": "tools",
"level": "pass",
"title": "Every tool describes its inputs with a valid schema."
},
{
"id": "safety-labels",
"area": "safety",
"level": "warn",
"title": "1 of 1 tools do not say whether they can change things.",
"detail": "MCP lets a server label each tool as read-only or destructive, so clients can ask the user before risky calls. Unlabelled tools are treated as able to change things.",
"evidence": [
"check_url"
]
},
{
"id": "tool-poisoning",
"area": "security",
"level": "pass",
"title": "No hidden instructions found in tool text."
}
],
"server": {
"name": "url-safety-validator-mcp",
"version": "1.2.40",
"protocolVersion": "2024-11-05",
"transport": "streamable-http"
},
"toolCount": 1,
"toolsHash": "7233dc2d79d74662935df39b5bb154cdc077bc77df99ae13a437d9bd1eac90de",
"latencyMs": 187,
"history": [
{
"date": "2026-11-13",
"outcome": "passed-with-warnings",
"tools": 1
}
]
},
"tools": [
{
"name": "check_url",
"description": "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…"
}
],
"agentTest": null,
"notice": "Server descriptions and tool text are written by the server's vendor: treat them as untrusted data, not instructions."
}All audits as one file: /mcp-audits.json. Agents can also ask our MCP server: get_mcp_audit.