Saudi Invoices (ZATCA Fatoora Phase 2 reporting & clearance)

app.wishpoolPublished by wishpool.appOfficial publisherv0.1.0Updated Oct 27, 2026

Saudi ZATCA Fatoora Phase 2: AI agents report B2C and clear B2B tax invoices, stateless.

The publisher's own server: Algeria Payments (Chargily Pay — EDAHABIA / CIB)

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an AI assistant report B2C and clear B2B Saudi ZATCA Fatoora Phase 2 tax invoices, statelessly.

What you can do
  • Submit B2C tax invoices to ZATCA Fatoora Phase 2 reporting
  • Submit B2B tax invoices for clearance
  • Operate statelessly, with no stored invoice state between calls
  • No individual tools are listed in the manifest, so exact operations are not documented.
When to use it
Use it when an assistant needs to file Saudi e-invoices with ZATCA under Fatoora Phase 2, either reporting simplified B2C invoices or clearing standard B2B invoices, from a workflow that already produces invoice data.
Requirements
A remote streamable HTTP endpoint at inv-sa.wishpool.app; no packages, environment variables or headers are declared. The manifest declares no authentication, though ZATCA submissions normally require taxpayer credentials and certificates, which are not described here.
Before you install
Submitting invoices to a tax authority is a legally significant, irreversible action that creates official records. The manifest declares no authentication, so it is unclear how taxpayer identity and ZATCA credentials are supplied; confirm this before sending real invoice data. Invoice contents are sent to a third-party host and onward to ZATCA.

Installation

In SourceWeft

  1. Open Saudi Invoices (ZATCA Fatoora Phase 2 reporting & clearance) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.wishpool%2Fsaudi-invoice-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "saudi-invoices-zatca-fatoora-phase-2-rep": {
      "type": "http",
      "url": "https://inv-sa.wishpool.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wishpool integrations