Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Israel Companies Due Diligence

PYPI · MCP-IL-COMPANIES

Due diligence on Israeli companies, partnerships, nonprofits (עמותות) and public benefit companies —

Available components

79 Trust /100

Last scanned (14 hours ago)

Scores higher than 76% of PyPI servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to olegsher-ds-2025/mcp-il-companies). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 387 tokens (~77/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
  • 15 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/mcp-il-companies@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo olegsher-ds-2025/mcp-il-companies
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/olegsher-ds-2025/mcp-il-companies/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 3902605979
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:04cee89d46941ace7a721a8d705811d8f2f3e39159f99a7f04f4943de40deeca

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 22 packages
Packages resolved 22
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~322 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
due_diligence ~77

Quick red-flag check for a counterparty (supplier, client, investee, grantee). Flags: not active, registry 'violator' (מפרה), stale annual reports, fast-track liquidation, many recent charges, missing nonprofit proper-management certificate. Returns a risk level with reasons.

NameTypeReqDescription
numberstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

entity_profile ~52

Full registry profile for one registration number (company, partnership, nonprofit or PBC), including recent registry changes (e.g. charges/שעבודים), liquidation status and nonprofit certificates.

NameTypeReqDescription
numberstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

find_entity ~96

Find Israeli companies, partnerships, nonprofits (עמותות) or public benefit companies by name.

NameTypeReqDescription
entity_typestring–"any", "company", "partnership", "nonprofit" or "pbc".
limitinteger–Max results per registry (1-50).
namestringyesFull or partial name, Hebrew or English (e.g. "וסטמה" or "Vastama").

Structured output declared, but exposes no named fields.

No examples provided.

health ~17

Check that the server can reach data.gov.il.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_nonprofits ~80

Search Israeli nonprofits (עמותות) by keyword, sector words (e.g. "חינוך", "רווחה", "בריאות") and exact city name.

NameTypeReqDescription
active_onlyboolean––
citystring––
limitinteger––
querystring––
sectorstring––

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Israel Companies Due Diligence MCP server?

Israel Companies Due Diligence runs locally as a PyPI package, launched with uvx mcp-il-companies. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-il-companies

# add to Claude Code
claude mcp add olegsher-ds-2025-mcp-il-companies -- uvx mcp-il-companies
Common questions

What is the Israel Companies Due Diligence MCP server?

Israel Companies Due Diligence is an MCP server listed in the public MCP registry as io.github.olegsher-ds-2025/mcp-il-companies. Due diligence on Israeli companies, partnerships, nonprofits (עמותות) and public benefit companies… This page covers its PyPI package (mcp-il-companies).

Is the Israel Companies Due Diligence MCP server safe to use?

Israel Companies Due Diligence scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Israel Companies Due Diligence MCP server expose?

Israel Companies Due Diligence exposes 5 tools: find_entity, entity_profile, due_diligence, search_nonprofits, health. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.

Is the Israel Companies Due Diligence MCP server still maintained?

Israel Companies Due Diligence is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Israel Companies Due Diligence MCP server under?

Israel Companies Due Diligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Israel Companies Due Diligence MCP server?

VerifyMCP ran 15 checks on Israel Companies Due Diligence, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Israel Companies Due Diligence: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.