Skip to content
    MCP Israel Logo
    עב

    We connect Israel's core business systems to Claude and ChatGPT over MCP — with the server running inside your network

    Priority, Hashavshevet, Rivhit and Green Invoice ship with no official MCP server. We build it, scope permissions per tool, and leave the keys with you.

    MCP Readiness Review — 90 minutes and a written documentSee what connects in your stack
    PASS · LIVE, AUTH-GATEDLive probe against an official endpoint
    $ curl -i -X POST https://mcp.monday.com/mcp \
    -H 'content-type: application/json' \
    -H 'accept: application/json, text/event-stream' \
    -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
         "params":{"protocolVersion":"2025-11-25",
                    "capabilities":{},
                    "clientInfo":{"name":"mcpisrael-probe"}}}'

HTTP/2 401
content-type: application/json
www-authenticate: Bearer realm="OAuth",
  resource_metadata="https://mcp.monday.com/.well-known/oauth-protected-resource/mcp",
  error="invalid_token", error_description="Missing or invalid access token"

{"error":"invalid_token",
 "error_description":"Missing or invalid access token"}

    HTTP 401 with a WWW-Authenticate challenge is the correct answer: the endpoint is live and authorization is enforced before any tool is reachable. A server that returns 200 without credentials is the problem, not the proof.

    Source: mcp.monday.com/mcp · official repository · Probe run: 27.07.2026

    Israel's front office is MCP-native. Its back office is a blank map.

    Two Israeli companies run official MCP servers for the front office. The finance and operations systems most Israeli companies actually run on do not. That is an engineering gap, not a marketing one.

    Official server exists

    No server found

    • Priority — The API is OData/REST. As of 27.07.2026 we found no mention of MCP, Model Context Protocol or AI agents in the official documentation, and no vendor-run MCP server.

      7 public repositories, 5 of them last pushed in 2017–2018.

      API documentation · vendor GitHub organisation

    • Rivhit — As of 27.07.2026 we found no public MCP server — not on GitHub, not on npm. The API is RivhitOnlineAPI.svc — SOAP over WCF, 126 operations. Generic MCP tooling and n8n/Make templates cannot consume that shape.

      GitHub search · npm search

    • Hashavshevet — The cloud API is documented with Swagger via WizCloud. As of 27.07.2026 we found no MCP server — not on GitHub, not on npm.

      GitHub search · npm search

    Found a server we missed? Tell us and we will update the table with the date and the source.

    What this means for you

    The front office can be connected this month: the vendor runs the server, documents it, and you decide which tools are enabled. The back office has to be built — a thin server over the existing API, a short tool list, and permissions you control.

    The shape of the API sets the effort, not the ambition. A modern REST API is days of work; SOAP over WCF is a project. That is why we publish the map before we sell anything.

    All 24 systems on the map

    Last verified: 27.07.2026

    The connection map

    Every row carries the vendor's status label in the vendor's own words, a link to the vendor's own documentation, and the date a human checked it. No score of ours, no star rating.

    SystemStatusEndpoint / repositoryVendor's label, verbatimChecked
    monday.comOfficial servermcp.monday.com/mcp“This feature is in testing and may change as improvements are made.”27.07.2026
    WixOfficial servermcp.wix.com/mcp27.07.2026
    MyBusiness CRMOfficial servermcp.mbapps.co.il“שרת ה-MCP מסתמך על חיבור פעיל של המשתמש למערכת ה-CRM.”27.07.2026
    Priority ERPNo server foundthe search we ranthe search we ran27.07.2026
    RivhitNo server foundthe search we ranthe search we ran27.07.2026
    HashavshevetNo server foundthe search we ranthe search we ran27.07.2026
    Green Invoice / MorningCommunity onlygithub.com/danielrosehill/GreenInvoice-MCP“NOT affiliated with, endorsed by, or supported by Green Invoice (Optimax Ltd)”27.07.2026
    iCountCommunity onlygithub.com/almog-ship-it/icount-mcp27.07.2026
    Google WorkspaceOfficial — previewgmailmcp.googleapis.com/mcp/v1“Developer Preview”27.07.2026
    Salesforce (Hosted MCP)Official serverNot checked — we will check it for you“across every Enterprise Edition org and above”27.07.2026
    All 24 systems
    Official server
    — vendor runs it, vendor documents it, no preview label
    Official — preview
    — vendor runs it and the vendor itself labels it preview or beta
    Community only
    — a third-party server exists — you own the security review
    No server found
    — as of the check date, none found on GitHub or npm

    How we build it

    One architecture, four controls. Each is enforced at a gateway we maintain — not by what a remote server reports about itself.

    Gateway architectureAI clients talk to one gateway running inside your network. The gateway holds the allow-list, the write approvals and the log, and it is the only thing that talks outward to vendor MCP servers and to your systems of record.ClaudeChatGPTCopilottrust boundary — your networkMCP gatewayallow-list · write approval · logvendor MCP serversmonday.com · Slackyour systems of recordPriority · Rivhit
    1. 01One server as the single egress point — no client talks directly to a third-party server.
    2. 02Human approval on every writing tool — enforced at the gateway, not by a flag the server sets about itself.
    3. 03Per-user OAuth with a short-lived token — never a shared credential.
    4. 04An append-only log for every tool call: arguments, identity, result.
    The full detail, against the spec clauses

    The offer

    MCP Readiness Review

    One 90-minute working session, followed by a written three-part document emailed within 3 business days. Not a deck, not a recording — a document that can be forwarded inside your organisation.

    Exactly what you receive

    1. 01

      A connection map of your stack

      Every row carries the vendor's own status label and a link to the vendor's own documentation. For example: monday.com — official server, the integration is labelled Beta by monday; Gmail — official, at Google's Developer Preview stage; Priority — no official server, a thin server over OData is required.

    2. 02

      A blast-radius table

      For each proposed connection: the exact OAuth scopes required, and what an attacker obtains if the model is prompt-injected. Scored against the official MCP security best-practices document.

    3. 03

      One first-automation spec

      Scoped small enough to ship, with written acceptance criteria. If you decide to build it yourselves, the spec is yours.

    Price

    ₪1,500

    Fully credited against the first project.

    Fixed, published price · 90-minute session · document within 3 business days · VAT not included

    The guarantee

    If the review does not identify at least one connection you can execute this quarter, you do not pay.

    This is why there are no testimonials on this site. A commitment we control beats a result we invented.

    Book a Readiness Review

    Go deeper

    All articles

    Questions asked before the call

    That is decided by architecture, not by a promise. An MCP server running inside your network, exposing narrow tools, sends out only the fields a specific call needs, instead of bulk-syncing a CRM or ERP into a foreign cloud service. Where a vendor runs the remote server itself, the map row says so.

    The regulatory context: Amendment 13 to Israel's Protection of Privacy Law took effect on 2025-08-14, replacing a database-registration regime with a personal-data processing framework. Transfers abroad are governed by the Privacy Protection (Transfer of Data to Databases Abroad) Regulations, 5761-2001. The European Commission determined on 2011-01-31 that Israel ensures an adequate level of protection and reaffirmed that status in its first-review report published 2024-01-15. None of this is legal advice.

    Full detail on the security page →

    Zapier solves a different problem, and solves it well: many SaaS applications with modern APIs. Zapier's MCP product page carries Beta labels, and its own figures are "30,000+ actions across 9,000+ apps".

    Two practical differences. First, the shape of the API: Rivhit is SOAP over WCF with 126 operations, which generic templates cannot consume — that is engineering, not configuration. Second, where authority is enforced: in the architecture we build, writes are approved at a gateway inside your network, against an allow-list you maintain, not by a flag the remote server sets about itself.

    zapier.com/mcp · the Rivhit search we ran

    The review itself: a 90-minute session and a written document within 3 business days.

    After that, the system decides. Where the vendor runs an official server, connecting it, choosing the tool set and scoping permissions is days of work. Where no server exists, a thin server has to be built over the existing API, and the shape of that API sets the order of magnitude: a modern REST API and a legacy SOAP interface are not the same job.

    What you will not find here is a "results in three hours" promise. It cannot be checked before you sign, so it is worth nothing.

    It changes, and that is by design. The current specification revision is 2025-11-25. Revision 2026-07-28 publishes on 28.07.2026. We last checked the versioning page ourselves on 27.07.2026.

    In practice that means three things: we pin server versions and lock dependencies rather than tracking latest; we alert on changes to tool names, descriptions and schemas, because such a change is a change to the authority you granted; and we publish every check with its date, so you can see when a human actually looked.

    the specification versioning page

    No. MCP Israel is an independent consultancy. We are not affiliated with Anthropic, the Linux Foundation or the Agentic AI Foundation. Model Context Protocol is an open standard governed under the Linux Foundation since December 2025.

    modelcontextprotocol.io

    As of 2026-07-27 we found none. Priority's official documentation contains no mention of MCP, Model Context Protocol, AI agents or LLM integrations, and the vendor's GitHub organisation holds 7 public repositories, 5 of them last pushed in 2017–2018. For Hashavshevet we found no server on GitHub or npm.

    What does exist for Priority is a community repository under MIT with 72 tools, plus gateways such as Zapier MCP. We name them, because our claim is about the absence of a first-party server, not the absence of code. With a community server, the security review is yours.

    Found a server we missed? Tell us and we will update the row with the date and the source.

    Priority API documentation · vendor GitHub organisation · the community repository assafch/Priority-Mcp · the Hashavshevet search

    Because we sell data governance and authority, and in that market social proof you cannot check is the risk itself. Instead we publish a dated, sourced map you can verify against each vendor's own documentation, and we hold one commitment we control: if the review does not identify at least one connection you can execute this quarter, you do not pay.

    When a first client is willing to be quoted by name, title and profile link, we will publish that. Until then, there are no counts of anything here.

    Start from the systems you already run

    We map which of your systems already speak MCP, which need a purpose-built server, and what the blast radius of each connection is.

    MCP Israel — MCP connections for business systems

    /* deployed 2026-04-08T12:08 */