Worldpay MCP Server

mcp-worldpay is an MCP server in the security category that exposes 22 tools to an agent, covering payment, token, read & search.

People who work with payment, token and dispute and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

One of 127 MCP servers published from codespar/mcp-dev-latam. Stars and repository activity are shared across all of them. See all 127 →

VERIFIED ACTIVE

LAST COMMIT 2026-08-29 · VERIFIED 2026-09-18

MIT · TypeScript servers · how we verify → /methodology

01 · Install Worldpay

before you install - you'll need

Set WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY, MCP_HTTP before connecting. WORLDPAY_ENV, WORLDPAY_API_VERSION are optional or environment-specific per the README.

Claude Code

claude mcp add codespar-mcp-dev-latam-packages-payments -- npx -y @codespar/mcp-worldpay

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "codespar-mcp-dev-latam-packages-payments": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-worldpay"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @codespar/mcp-worldpay - published under the repo owner's npm scope (@codespar)

registry namespace io.github.codespar is GitHub-verified and matches the repo owner

03 · What Worldpay can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can run an AVS/CVC account verification on a card without charging it, capture (settle) an authorized payment, retrieve the detail of a payment event by its Worldpay eventId, and retrieve a stored card token's metadata (bin, scheme, last4, cardHolderName, expiryDate, etc.).

Capability map

Tools grouped from the project's README - what Worldpay lets an agent do.

Payment

8 tools - e.g. Authorize a card payment.; Capture (settle) an authorized payment.; Void an authorization that has not yet been captured.

authorize_payment · capture_payment · cancel_payment · refund_payment · reverse_payment · get_payment…

Token

4 tools - e.g. Tokenize a card for reuse (card-on-file).; Retrieve a stored card token's metadata (bin, scheme, last4, cardHolderName, expiryDate, etc.).; Update metadata on a stored card token (e.g.

create_token · get_token · update_token · delete_token

read & search

3 tools - e.g. Step 1 of 3DS2 - submit device-data-collection (DDC) output to Worldpay to determine whether a challenge is...; Retrieve a dispute's current state, evidence requirements, deadlines, and HATEOAS action…

lookup_3ds · get_dispute · get_reconciliation_batch

Verify

1 tool - e.g. Run an AVS/CVC account verification on a card without charging it.

verify_account

auth & access

1 tool - e.g. Step 2 of 3DS2 - authenticate the cardholder.

authenticate_3ds

Challenge

1 tool - e.g. Step 3 of 3DS2 - post the CReq back after the issuer challenge window closes, to retrieve the final authent...

challenge_3ds

Defend

1 tool - e.g. Open a defence on a dispute - signals intent to defend before submit_dispute_evidence.

defend_dispute

Accept

1 tool - e.g. Accept a dispute (forfeit the chargeback).

accept_dispute

04 · Who maintains Worldpay

mcp-worldpay is maintained by codespar. We track 127 MCP servers from codespar - 127 actively maintained, 271 combined GitHub stars, oldest repo from Mar 2026. Full record: all servers from codespar.

  1. mcp-brasil-api MCP server for BrasilAPI - CEP, CNPJ, banks, FIPE, holidays, weather ★ 271
  2. mcp-iugu MCP server for iugu - invoices, subscriptions, customers, payment methods ★ 271
  3. mcp-asaas MCP server for Asaas - billing automation, Pix, boleto, credit card, subscriptions ★ 271
  4. mcp-omie MCP server for Omie - ERP, customers, products, orders, invoices, financials ★ 271
  5. mcp-mercado-bitcoin MCP server for Mercado Bitcoin - Brazilian crypto exchange, trading, orderbook, withdrawals ★ 271
  6. mcp-sendgrid MCP server for SendGrid - global transactional + marketing email (Twilio-owned) ★ 271

05 · Facts

category
security - actively maintained as of 2026-09-18.
registry
io.github.codespar/mcp-worldpay (active, first published 2026-06-20 · 2 versions)
packages
npm:@codespar/mcp-worldpay

06 · Worldpay FAQ

Is Worldpay still maintained?

Yes - as of 2026-09-18, its last commit was 2026-08-29. We re-verify nightly.

What can Worldpay do?

With this server connected, an agent can run an AVS/CVC account verification on a card without charging it, capture (settle) an authorized payment, retrieve the detail of a payment event by its Worldpay eventId, and retrieve a stored card token's metadata (bin, scheme, last4, cardHolderName, expiryDate, etc.).

How do I install Worldpay?

Run `npx -y @codespar/mcp-worldpay`. The README documents 6 environment variables (WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY…) to set first. Set WORLDPAY_USERNAME, WORLDPAY_PASSWORD, WORLDPAY_ENTITY, MCP_HTTP before connecting. WORLDPAY_ENV, WORLDPAY_API_VERSION are optional or environment-specific per the README. You can also paste the ready-made client config above.

Does Worldpay run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Worldpay