Vsafe Risk MCP Server

ai.v-safe/vsafe-risk

answering

Vsafe Risk is answering right now. Last checked 1 min ago. It exposes 2 tools.

KYB risk scores for Israeli companies: sanctions, insolvency, adverse media, cyber, registry.

Uptime history 39 hours of history

39 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

346 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add vsafe-risk --transport http https://mcp.v-safe.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vsafe-risk": {
      "url": "https://mcp.v-safe.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.vsafe-risk]
url = "https://mcp.v-safe.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "vsafe-risk": {
      "url": "https://mcp.v-safe.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "vsafe-risk": {
      "url": "https://mcp.v-safe.ai/mcp"
    }
  }
}

Available tools 2

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

israeli

check_israeli_company

Full V-Safe risk assessment of an Israeli company — all 8 layers incl. AI-scored adverse media. Returns a 0-100 risk score + LOW/MEDIUM/HIGH band, per-layer breakdown, linked evidence, confidence and coverage. Input: the 9-digit Israeli company number (registration_number / ח.פ); optional name, website and global ids (LEI/DUNS/VAT) enrich the result. Response time is typically 8-20s: V-Safe queries primary sources LIVE (registries, insolvency courts, sanctions, adverse media, domain) at request time, not from a cache. Set the client timeout to >= 30s.

quick

quick_check

Fast, cheap pre-screen — registry + insolvency + banking-restriction + domain only (no sanctions/adverse-media/market, no AI). Same output schema as the full check. Input: the 9-digit company number (ח.פ); optional website. Response time is typically 8-20s: V-Safe queries primary sources LIVE (registries, insolvency courts, sanctions, adverse media, domain) at request time, not from a cache. Set the client timeout to >= 30s.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.v-safe.ai/mcp	streamable-http	answering	333 ms	1 min ago

Vsafe Risk — questions

Answers built from our own checks of this server.

What can Vsafe Risk do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_israeli_company, quick_check. 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 Vsafe Risk working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 346 ms. The bar chart above shows every period we have measured.

How do I connect Vsafe Risk?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Vsafe Risk need an API key?

No. Vsafe Risk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Vsafe Risk?

It answers our handshake in 346 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.