Ext Ops Panel
Open dashboard
Comparison

mastercard-developers vs VeriFactu

mastercard-developers is a plugin bundle for AI coding tools published by Mastercard. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). VeriFactu is an MCP server published by ArceeDev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacemastercard-developersVeriFactu
Copilot CLI: github/awesome-copilot Listed
Version: 1.0.0
Forks (GitHub): 40
Stars (GitHub): 60
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

mastercard-developers vs VeriFactu
Factmastercard-developersVeriFactu
Marketplaces that list it11
Stars (GitHub) (differs)60 (better)0 (worse)
Forks (GitHub) (differs)40 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.keyflint.dev/verifactu/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mastercard/developers-agent-toolkitgithub.com/arceedev/verifactu-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-11-042026-11-06
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 h ago, requires authentication

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

mastercard-developers

In its own words, on Copilot CLI: github/awesome-copilot:

Mastercard Developers plugin to help build integrations with Mastercard APIs, including best practices and the Mastercard Developers MCP server.

VeriFactu

In its own words, on Official MCP Registry:

Audit VERI*FACTU hash chains, build the AEAT tax QR, build and validate Facturae 3.2.2 invoices.

How to run each

mastercard-developers

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

VeriFactu As a remote MCP server

Claude Code
claude mcp add --transport http verifactu-mcp https://mcp.keyflint.dev/verifactu/mcp

Requires: KEYFLINT_LICENSE (secret)

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

Only VeriFactu 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

The marketplaces of mastercard-developers publish no settings it asks for, so we do not compare settings.

What it can do: mastercard-developers · What it can do: VeriFactu · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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