Ext Ops Panel
Open dashboard
Comparison

Askell vs io.github.codespar/mcp-worldpay

Askell is an MCP server published by Neschadin. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-worldpay is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplaceAskellio.github.codespar/mcp-worldpay
Official MCP Registry Listed
Version: 0.4.24
Downloads/month (npm): 2 779
Downloads/week (npm): 299
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.2.0-alpha.3
Downloads/month (npm): 91
Downloads/week (npm): 19
Forks (GitHub): 52
Stars (GitHub): 274
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

Askell vs io.github.codespar/mcp-worldpay
FactAskellio.github.codespar/mcp-worldpay
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)274 (better)
Forks (GitHub) (differs)0 (worse)52 (better)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (askell-mcp)On your machine (@codespar/mcp-worldpay)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/neschadin/askell-mcpgithub.com/codespar/mcp-dev-latam
Changes in the last 7 days00
First seen2026-10-112026-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

Askell

In its own words, on Official MCP Registry:

MCP server for the Askell payment and subscription API (Bun + stdio)

io.github.codespar/mcp-worldpay

In its own words, on Official MCP Registry:

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

How to run each

Askell As a local MCP server: npm package

Claude Code
claude mcp add --env "ASKELL_PRIVATE_API_KEY=<YOUR_ASKELL_PRIVATE_API_KEY>" --transport stdio askell-mcp -- npx -y --no-env-file x askell-mcp askell-mcp

Requires: ASKELL_PRIVATE_API_KEY (secret)

io.github.codespar/mcp-worldpay As a local MCP server: npm package

Claude Code
claude mcp add --env "WORLDPAY_ENTITY=<YOUR_WORLDPAY_ENTITY>" --env "WORLDPAY_PASSWORD=<YOUR_WORLDPAY_PASSWORD>" --env "WORLDPAY_USERNAME=<YOUR_WORLDPAY_USERNAME>" --transport stdio mcp-worldpay -- npx -y @codespar/mcp-worldpay

Requires: WORLDPAY_ENTITY, WORLDPAY_PASSWORD (secret), WORLDPAY_USERNAME

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

Only Askell asks for

  • ASKELL_ENV
  • ASKELL_PRIVATE_API_KEY (secret)

Only io.github.codespar/mcp-worldpay asks for

  • WORLDPAY_API_VERSION
  • WORLDPAY_ENTITY
  • WORLDPAY_ENV
  • WORLDPAY_PASSWORD (secret)
  • WORLDPAY_USERNAME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Askell · What it can do: io.github.codespar/mcp-worldpay · Compare two other plugins

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