Ext Ops Panel
Open dashboard
Comparison

io.github.kOlapsis/gofact vs Qeemah Accounting & ZATCA e-Invoicing

io.github.kOlapsis/gofact is an MCP server published by kOlapsis. Marketplaces we read that list it: 1 (Official MCP Registry). Qeemah Accounting & ZATCA e-Invoicing is an MCP server published by mosmn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.kOlapsis/gofactQeemah Accounting & ZATCA e-Invoicing
Official MCP Registry Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 1.0.1
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.kOlapsis/gofact vs Qeemah Accounting & ZATCA e-Invoicing
Factio.github.kOlapsis/gofactQeemah Accounting & ZATCA e-Invoicing
Marketplaces that list it11
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/kOlapsis/gofact/releases/download/v1.2.0/gofact-mcp_1.2.0_darwin_amd64.mcpb)Remote server (api.qeemahcloud.com/api/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)AGPL-3.0-or-laterNot stated
Repository (differs)github.com/kolapsis/gofactgithub.com/mosmn/qeemah-accounting
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 45 h ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.kOlapsis/gofact

In its own words, on Official MCP Registry:

Creates compliant French e-invoices locally: Factur-X PDF/A-3 with EN 16931 CII XML, legal numbering

Qeemah Accounting & ZATCA e-Invoicing

In its own words, on Official MCP Registry:

Saudi ZATCA e-invoicing Phase 2 compliance audit, invoice drafting, and CFO VAT analytics.

How to run each

io.github.kOlapsis/gofact

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Qeemah Accounting & ZATCA e-Invoicing As a remote MCP server

Claude Code
claude mcp add --transport http qeemah https://api.qeemahcloud.com/api/v1/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Qeemah Accounting & ZATCA e-Invoicing has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.kOlapsis/gofact · What it can do: Qeemah Accounting & ZATCA e-Invoicing · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built