Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Izipay — Peru enterprise acquirer (Niubiz): authorize/capture/refund, cuotas
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
IZIPAY_USERNAME, IZIPAY_PASSWORD, IZIPAY_MERCHANT_CODE, IZIPAY_ENV, IZIPAY_BASE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"izipay": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-izipay"
],
"env": {
"IZIPAY_USERNAME": "your-value",
"IZIPAY_PASSWORD": "your-value",
"IZIPAY_MERCHANT_CODE": "your-value",
"IZIPAY_ENV": "your-value",
"IZIPAY_BASE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add izipay --env IZIPAY_USERNAME=your-value --env IZIPAY_PASSWORD=your-value --env IZIPAY_MERCHANT_CODE=your-value --env IZIPAY_ENV=your-value --env IZIPAY_BASE_URL=your-value -- npx -y @codespar/mcp-izipayFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"izipay": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-izipay"
],
"env": {
"IZIPAY_USERNAME": "your-value",
"IZIPAY_PASSWORD": "your-value",
"IZIPAY_MERCHANT_CODE": "your-value",
"IZIPAY_ENV": "your-value",
"IZIPAY_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"izipay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-izipay"
],
"env": {
"IZIPAY_USERNAME": "your-value",
"IZIPAY_PASSWORD": "your-value",
"IZIPAY_MERCHANT_CODE": "your-value",
"IZIPAY_ENV": "your-value",
"IZIPAY_BASE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
IZIPAY_ENV envIZIPAY_BASE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account codespar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: IZIPAY_USERNAME, IZIPAY_PASSWORD, IZIPAY_MERCHANT_CODE
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0-alpha.3) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server for Izipay — Peru's enterprise acquirer.
Izipay is the merchant-facing brand of Niubiz (Visa + Peruvian banks joint venture), the largest card acquirer in Peru with 20%+ share. Niubiz/Izipay is the default for enterprise merchants with serious volume and a direct acquirer contract.
| @codespar/mcp-culqi | @codespar/mcp-izipay | |
|---|---|---|
| Segment | Peru SMB | Peru enterprise |
| Type | PSP (Stripe-analog) | Acquirer (Niubiz) |
| Onboarding | Self-serve | Commercial contract |
| Customers | D2C, SaaS, startups | Retail chains, airlines, utilities, banks |
Peruvian merchants with serious volume typically have an Izipay acquirer contract before they adopt a PSP — different customers, different contracts, different commercial terms. The two servers complement each other.
This is 0.1.0-alpha.1. Izipay's developer portal at developers.izipay.pe is contract-gated — the public homepage advertises the API but the full REST reference is only available to contracted merchants. The endpoint paths in this server are best-effort inferences from Izipay's public SDK repositories (github.com/izipay-pe) and common Niubiz/Izipay REST conventions. Every endpoint below should be validated against your integration kit before going live, and corrections are welcome via PR.
| Tool | Method | Path |
|---|---|---|
| auth (internal) | POST | /auth/login |
create_charge | POST | /v1/charges |
capture_charge | POST | /v1/charges/{id}/capture |
cancel_charge | POST | /v1/charges/{id}/cancel |
refund_charge | POST | /v1/charges/{id}/refund |
get_charge | GET | /v1/charges/{id} |
tokenize_card | POST | /v1/tokens |
delete_token | DELETE | /v1/tokens/{id} |
create_installment_plan | POST | /v1/installments |
list_transactions | GET | /v1/transactions |
get_settlement | GET | /v1/settlements/{date} |
| Tool | Purpose |
|---|---|
create_charge | Authorize a card payment. |
capture_charge | Capture a previously authorized charge (when capture=false was used in create_charge). |
cancel_charge | Void an authorized-but-uncaptured charge. |
refund_charge | Refund a captured charge. |
get_charge | Retrieve a charge by Izipay charge id. |
tokenize_card | Tokenize a card for PCI-safe reuse. |
delete_token | Delete a stored card token. |
create_installment_plan | Create a Peruvian cuotas (installment) plan on a charge. |
list_transactions | List transactions for reconciliation. |
get_settlement | Get the daily settlement batch (liquidación) for a given date. |
get_charge_by_order | Retrieve a charge by the merchant-side orderNumber (order_id passed to create_charge). |
list_installment_options | Query available cuota programs for a given card BIN and amount. |
list_settlements | List settlement batches across a date range. |
create_payment_link | Create a hosted payment link (pay-by-link). |
get_payment_link | Retrieve a payment link by id. |
pay_yape | Initiate a Yape direct payment. |
pay_plin | Initiate a Plin direct payment. |
authenticate_3ds | Complete a 3-D Secure challenge. |
create_subscription | Start a recurring card charge (subscription). |
cancel_subscription | Cancel an active subscription. |
npm install @codespar/mcp-izipay@alpha
IZIPAY_USERNAME="..." # merchant username
IZIPAY_PASSWORD="..." # merchant password (secret) IZIPAY_MERCHANT_CODE="..." # codigoComercio IZIPAY_ENV="production" # or "sandbox" IZIPAY_BASE_URL="..." # Optional override
Defaults:
IZIPAY_ENV=production → https://api.izipay.peIZIPAY_ENV=sandbox → https://sandbox-api.izipay.peJWT Bearer. On the first API call the server POSTs { username, password, merchantCode } to /auth/login, caches the returned JWT in memory, and attaches it as Authorization: Bearer on every subsequent request. The cached JWT is refreshed 60s before expiry. Transparent to callers.
# stdio (default)
npx @codespar/mcp-izipay
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-izipay
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
MIT