PagoKit — Payment Integration Agent vs io.github.codespar/mcp-epayco
PagoKit — Payment Integration Agent is a plugin bundle for AI coding tools published by Enrique Rocha. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.codespar/mcp-epayco is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
| Marketplace | ||
|---|---|---|
| Community marketplace hainrixz/agente-pagokit | Listed Version: 0.2.2 Forks (GitHub): 7 Stars (GitHub): 70 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (npm): 134 Downloads/week (npm): 57 Forks (GitHub): 52 Stars (GitHub): 279 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
| Fact | PagoKit — Payment Integration Agent | io.github.codespar/mcp-epayco |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 70 (worse) | 279 (better) |
| Forks (GitHub) (differs) | 7 (worse) | 52 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@codespar/mcp-epayco) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 22 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hainrixz/agente-pagokit | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
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
PagoKit — Payment Integration Agent
Picks the right payment provider for your project and writes the integration, with deterministic validators that block insecure writes as they happen.
io.github.codespar/mcp-epayco
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks
How to run each
PagoKit — Payment Integration Agent As a Claude Code plugin
/plugin marketplace add hainrixz/agente-pagokit
/plugin install pagokit@tododeia
io.github.codespar/mcp-epayco As a local MCP server: npm package
claude mcp add --env "EPAYCO_PRIVATE_KEY=<YOUR_EPAYCO_PRIVATE_KEY>" --env "EPAYCO_PUBLIC_KEY=<YOUR_EPAYCO_PUBLIC_KEY>" --transport stdio mcp-epayco -- npx -y @codespar/mcp-epayco
Requires: EPAYCO_PRIVATE_KEY (secret), EPAYCO_PUBLIC_KEY
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 PagoKit — Payment Integration Agent publish no settings it asks for, so we do not compare settings.
What it can do: PagoKit — Payment Integration Agent · What it can do: io.github.codespar/mcp-epayco · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.