Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Test Card Hub

NPM · TEST-CARD-HUB-MCP

Sandbox test cards, Playwright tests, real-card scanner and decline codes for LATAM gateways.

Available components

0 this week 71 Trust /100

Last scanned (19 hours ago)

Scores higher than 42% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 855 tokens (~122/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/test-card-hub-mcp@1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~855 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_decline ~144

Explains a payment decline / error code of a gateway: the official meaning and source URL (from the gateway docs) plus a SUGGESTED customer message (es/en) and merchant action. Omit code to list the known codes of a gateway. Gateways: stripe, mercado-pago, conekta, openpay, netpay, clip, payu-latam, dlocal, adyen.

NameTypeReqDescription
codestring–Decline/error code exactly as the gateway returned it.
gatewaystringyesGateway id, e.g. "stripe".
langstring–Language for descriptions, notes and hints. Default "en".

No output schema declared.

No examples provided.

find_test_cards ~182

Returns sandbox test cards to type into a checkout, filtered by gateway, outcome and brand. Each card includes the number, brand, expected outcome, gateway notes and generic fill values (expiry, CVV, postal code). When gatewayHint contradicts fill values, the hint wins (e.g. Mercado Pago decides the outcome by cardholder name). Returns at most 50 cards (default 10); total tells how many matched.

NameTypeReqDescription
brandstring––
environmentstring–User environment name from list_environments.
gatewaystring–Gateway id from list_gateways, e.g. "stripe".
langstring–Language for descriptions, notes and hints. Default "en".
limitinteger––
outcomestring–Expected result of the charge.
sourcestring–Default "all".

No output schema declared.

No examples provided.

generate_checkout_tests ~168

Writes a Playwright test file (TypeScript) with one test per sandbox scenario of a gateway: card, expiry, CVV, and the extra fields the gateway needs (e.g. NetPay customer email, Mercado Pago or Adyen cardholder name), taken from official docs. Selectors in fillCheckout/expectOutcome are a starting point the user must map to their checkout. Returns the file contents; the server writes nothing to disk.

NameTypeReqDescription
checkoutUrlstringyeshttp(s) URL of the checkout in test mode.
gatewaystringyesGateway id from list_gateways, e.g. "netpay".
langstring–Language for descriptions, notes and hints. Default "en".
outcomesarray–Only these outcomes. Default: all.

No output schema declared.

No examples provided.

list_environments ~46

Lists the environments saved in the Test Card Hub extension (development, staging, a client), read from the exported backup file configured on the server. Use the names with find_test_cards.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_gateways ~102

Lists the payment gateway sandboxes with official test cards (Stripe, Mercado Pago MX, Conekta, Openpay, NetPay, Kushki, Clip, PayU, dLocal, Adyen): id, docs URL, date verified, card count per outcome, and the gateway hint (expiry/CVV/cardholder-name rules). Call first to pick a gateway id.

NameTypeReqDescription
langstring–Language for descriptions, notes and hints. Default "en".

No output schema declared.

No examples provided.

scan_for_real_cards ~146

Scans text (source code, test fixtures, logs, seed data) for card numbers that may be REAL: Luhn-valid, a known brand, and not a published sandbox number. Findings are masked (first 6 + last 4; last 4 only under 16 digits) and include line and column. Detects digits that are contiguous or grouped by single spaces or dashes; numbers split across lines or by dots are not detected. Pass the file contents as text; this server never reads files. Limits: 200000 characters per call, 50 findings shown.

NameTypeReqDescription
textstringyesText to scan, e.g. a file's contents.

No output schema declared.

No examples provided.

validate_card ~67

Checks a card number before using it in a checkout: Luhn, length, brand, and whether it is a known sandbox test number. verdict "possibly_real_card" means stop: never type it into a form.

NameTypeReqDescription
numberstringyesCard number, spaces and dashes allowed.

No output schema declared.

No examples provided.

Install

How do I install the Test Card Hub MCP server?

Test Card Hub runs locally as an npm package, launched with npx -y test-card-hub-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · test-card-hub-mcp

# add to Claude Code
claude mcp add eyrockscript-test-card-hub -- npx -y test-card-hub-mcp
Common questions

What is the Test Card Hub MCP server?

Test Card Hub is an MCP server listed in the public MCP registry as io.github.eyrockscript/test-card-hub. Sandbox test cards, Playwright tests, real-card scanner and decline codes for LATAM gateways. This page covers its npm package (test-card-hub-mcp).

Is the Test Card Hub MCP server safe to use?

Test Card Hub scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Test Card Hub MCP server expose?

Test Card Hub exposes 7 tools: list_gateways, find_test_cards, list_environments, validate_card, scan_for_real_cards, and 2 more. Their descriptions and schemas cost roughly 855 tokens of context every time the server is loaded.

Is the Test Card Hub MCP server still maintained?

Test Card Hub is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Test Card Hub MCP server under?

Test Card Hub declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Test Card Hub MCP server?

VerifyMCP ran 15 checks on Test Card Hub, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Test Card Hub: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.