Is the V Safe Vsafe Risk MCP server down?

mcp-registry/ai.v-safe/vsafe-risk · v1.27.2

healthy
Last checked 2026-10-26 19:08 UTC · handshake 691ms

As of 2026-10-26 19:08 UTC, the V Safe Vsafe Risk MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 26 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.9%
checks observed
4,966
outages (90d)
26
tools
2

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

Point your MCP client at this streamable-http endpoint: https://mcp.v-safe.ai/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 2 warning(s) across 2 tool(s); ~482 tokens of tool definitions.
Scores higher than 5% of 15,766 MCP servers Glimind has audited.
Its tool list costs an agent ~482 tokens per session — lighter than 90% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

8 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_israeli_company, quick_check

2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_israeli_company, quick_check

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.v-safe%2Fvsafe-risk/fixes

check_israeli_company 1 change
{
  "name": "check_israeli_company",
  "description": "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 ",
  "inputSchema": {
    "type": "object",
    "title": "check_israeli_companyArguments",
    "required": [
      "registration_number"
    ],
    "properties": {
      "lei": {
        "type": "string",
        "title": "Lei",
        "default": ""
      },
      "vat": {
        "type": "string",
        "title": "Vat",
        "default": ""
      },
      "duns": {
        "type": "string",
        "title": "Duns",
        "default": ""
      },
      "website": {
        "type": "string",
        "title": "Website",
        "default": ""
      },
      "company_name": {
        "type": "string",
        "title": "Company Name",
        "default": ""
      },
      "registration_number": {
        "type": "string",
        "title": "Registration Number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
quick_check 1 change
{
  "name": "quick_check",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "title": "quick_checkArguments",
    "required": [
      "registration_number"
    ],
    "properties": {
      "website": {
        "type": "string",
        "title": "Website",
        "default": ""
      },
      "registration_number": {
        "type": "string",
        "title": "Registration Number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.v-safe/vsafe-risk"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.v-safe/vsafe-risk"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.v-safe%2Fvsafe-risk.svg)](https://glimind.com/server/mcp-registry%2Fai.v-safe%2Fvsafe-risk?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.v-safe%2Fvsafe-risk?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.v-safe%2Fvsafe-risk.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.v-safe%2Fvsafe-risk.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.v-safe%2Fvsafe-risk?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1fc0dea951cc88ea…, first seen 2026-10-17, included at leaf 475 of 74,940. Version history · verify what your client received.

Tools (2)

Compare: most reliable knowledge servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the V Safe Vsafe Risk MCP server down right now?

As of 2026-10-26 19:08 UTC, the V Safe Vsafe Risk MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 26 outages in 90 days, with a median recovery of 2 minutes.

How many tools does V Safe Vsafe Risk MCP server provide?

V Safe Vsafe Risk MCP server advertises 2 tools, including check_israeli_company, quick_check.

How do I install V Safe Vsafe Risk MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.v-safe.ai/mcp

Is the V Safe Vsafe Risk MCP server safe to connect to an AI agent?

Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of V Safe Vsafe Risk MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve