MCP Worldpay

Name: MCP Worldpay
Author: codespar

by codesparversion 0.2.0-alpha.3i★ –iRuns on your computer

Registry nameio.github.codespar/mcp-worldpay

Install

Overview

Description from the maker (original English)

MCP server for Access Worldpay — enterprise processor: authorize, capture, refund, tokenize

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY, WORLDPAY_ENV, WORLDPAY_API_VERSION

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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": {
    "worldpay": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-worldpay"
      ],
      "env": {
        "WORLDPAY_USERNAME": "your-value",
        "WORLDPAY_PASSWORD": "your-value",
        "WORLDPAY_ENTITY": "your-value",
        "WORLDPAY_ENV": "your-value",
        "WORLDPAY_API_VERSION": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add worldpay --env WORLDPAY_USERNAME=your-value --env WORLDPAY_PASSWORD=your-value --env WORLDPAY_ENTITY=your-value --env WORLDPAY_ENV=your-value --env WORLDPAY_API_VERSION=your-value -- npx -y @codespar/mcp-worldpay

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "worldpay": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-worldpay"
      ],
      "env": {
        "WORLDPAY_USERNAME": "your-value",
        "WORLDPAY_PASSWORD": "your-value",
        "WORLDPAY_ENTITY": "your-value",
        "WORLDPAY_ENV": "your-value",
        "WORLDPAY_API_VERSION": "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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "worldpay": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-worldpay"
      ],
      "env": {
        "WORLDPAY_USERNAME": "your-value",
        "WORLDPAY_PASSWORD": "your-value",
        "WORLDPAY_ENTITY": "your-value",
        "WORLDPAY_ENV": "your-value",
        "WORLDPAY_API_VERSION": "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.

Values you fill in

WORLDPAY_USERNAME required env
Access Worldpay API username (Basic Auth)
WORLDPAY_PASSWORD secret required env
Access Worldpay API password (Basic Auth)
WORLDPAY_ENTITY required env
Merchant entity identifier assigned during onboarding. Injected as merchant.entity into every request body.
WORLDPAY_ENV env
sandbox | production. Defaults to sandbox. sandbox -> https://try.access.worldpay.com, production -> https://access.worldpay.com.
WORLDPAY_API_VERSION env
Payments API version for the Content-Type/Accept media-type header. Defaults to v7.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account codespar, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32568 servers in this category
Published to the registry more recently than 14% of the other 32568 servers in this category
Basic checks equal to or better than 100% of the other 32568 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Worldpay safe?

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.

What keys or codes does it need?

You need to fill in: WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0-alpha.3) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FlyDocs

by flydocs.ai

Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.

Runs on your computerUpdated today

Install

README from the maker

Open the README

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.

@codespar/mcp-worldpay

MCP server for Access Worldpay — global enterprise payment processor.

Worldpay is one of the largest card acquirers in the world and a default rail for EU/UK/US enterprise merchants. This server targets the modern Access Worldpay REST surface, not the legacy FIS/WPG XML gateway.

Status: 0.1.0-alpha.1 — Access Worldpay uses HATEOAS action links (linkData) for lifecycle operations. Exact endpoint paths and media-type versions have been validated against the public docs (v7 payments, v4 verifications, v3 tokens, v1 fraudsight/disputes) but are moving targets. See Stability below.

Tools (22)

Tool	Purpose
`verify_account`	Run an AVS/CVC account verification on a card without charging it.
`authorize_payment`	Authorize a card payment.
`capture_payment`	Capture (settle) an authorized payment.
`cancel_payment`	Void an authorization that has not yet been captured.
`refund_payment`	Refund a captured payment.
`reverse_payment`	Reverse a payment atomically — voids if not yet captured, refunds if already captured.
`get_payment`	Retrieve the detail of a payment event by its Worldpay eventId.
`create_token`	Tokenize a card for reuse (card-on-file).
`get_token`	Retrieve a stored card token's metadata (bin, scheme, last4, cardHolderName, expiryDate, etc.).
`update_token`	Update metadata on a stored card token (e.g.
`delete_token`	Delete a stored card token.
`query_payment`	Look up a payment by the merchant-side transactionReference you assigned on authorize_payment.
`list_payment_events`	List recent payment events for the configured merchant entity.
`lookup_3ds`	Step 1 of 3DS2 — submit device-data-collection (DDC) output to Worldpay to determine whether a challenge is...
`authenticate_3ds`	Step 2 of 3DS2 — authenticate the cardholder.
`challenge_3ds`	Step 3 of 3DS2 — post the CReq back after the issuer challenge window closes, to retrieve the final authent...
`get_dispute`	Retrieve a dispute's current state, evidence requirements, deadlines, and HATEOAS action links.
`defend_dispute`	Open a defence on a dispute — signals intent to defend before submit_dispute_evidence.
`get_reconciliation_batch`	Retrieve a reconciliation batch (daily settlement file equivalent) — lists all settled transactions, fees,...
`accept_dispute`	Accept a dispute (forfeit the chargeback).
`submit_dispute_evidence`	Submit evidence to defend a dispute.
`fraud_screen`	Run a standalone FraudSight assessment on a payment method (no authorization).

Install

npm install @codespar/mcp-worldpay@alpha

Environment

WORLDPAY_USERNAME="..."    # API username (Basic Auth)

WORLDPAY_PASSWORD="..." # API password (Basic Auth) WORLDPAY_ENTITY="..." # Merchant entity id; injected as merchant.entity WORLDPAY_ENV="sandbox" # sandbox | production; default sandbox WORLDPAY_API_VERSION="v7" # Payments API version; default v7

Authentication

HTTP Basic auth with your Worldpay-issued credentials:

Authorization: Basic base64(username:password)

Each API family uses its own versioned media type. The server sets the correct Content-Type / Accept headers per call:

Family	Media type
payments	`application/vnd.worldpay.payments-v7+json`
verifications	`application/vnd.worldpay.verifications.accounts-v4+json`
tokens	`application/vnd.worldpay.tokens-v3.hal+json`
fraudsight	`application/vnd.worldpay.fraudsight-v1.hal+json`
disputes	`application/vnd.worldpay.disputes-v1.hal+json`

HATEOAS and `linkData`

Access Worldpay is HATEOAS-driven. After authorize_payment, the response contains _links such as payments:settle, payments:partialSettle, payments:cancel, payments:refund, payments:partialRefund, and payments:reverse. Each href ends in an opaque segment we call `linkData`, e.g.:

/payments/settlements/eyJrIjoiazNhYjYzMiJ9

^^^^^^^^^^^^^^^^^^^ linkData

Extract that segment and pass it as linkData to capture_payment / cancel_payment / refund_payment / reverse_payment. When omitted, the server POSTs to the bare resource path; this only works for onboardings configured for transactionReference-addressable settlements.

Run

# stdio (default — for Claude Desktop, Cursor, etc.)

npx @codespar/mcp-worldpay

HTTP (for server-to-server testing)

MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-worldpay

Stability

Published as 0.1.0-alpha.1 until we validate end-to-end against a real sandbox account.
Global Payments acquired Worldpay in January 2026. Base URLs (try.access.worldpay.com / access.worldpay.com) remain valid as of this writing, but Global Payments has publicly signalled platform consolidation. Expect URL and media-type rebranding over the next 12–18 months. Pin the WORLDPAY_API_VERSION env var and watch the release notes.
This server does not cover: Worldpay Total (US CNP-API legacy), the WPG/FIS XML gateway, Disputes Direct (separate from Access Disputes), or Worldpay for Platforms. Those are separate surfaces and would be separate packages.

Enterprise

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.

License

MIT

MCP Worldpay

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FlyDocs

README from the maker

@codespar/mcp-worldpay

Tools (22)

Install

Environment

Authentication

HATEOAS and linkData

Run

HTTP (for server-to-server testing)

Stability

Enterprise

License

HATEOAS and `linkData`