Creditcard
Server Details
Credit-card number validation MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 38.4% over 45 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-creditcard
- GitHub Stars
- 0
- Server Listing
- mcp-creditcard
TDQS
Scored across 33 tools
Several tools have overlapping purposes or are intentionally similar: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to data sources with subtle distinctions; polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, polymarket_kalshi_spread, and polymarket_edge_tracker overlap around prediction-market scanning and execution. Some tools are clearly distinct, but the boundaries between the meta-lookup and prediction-market families are fuzzy.
Tool names consistently use lower_snake_case throughout, with no camelCase or mixed-style violations. The pattern is mostly noun/verb based but not uniformly verb_noun, which is a minor deviation rather than a readability problem.
With 33 tools, the set is heavy for any single server, and it mixes credit-card utilities, data-gateway meta-tools, prediction-market analytics, memory, subscriptions, and dependency scanning. The count feels more like a platform bundle than a well-scoped tool surface.
For a server named Creditcard, only validate_card and check_luhn relate to the domain; there is no card issuance, authorization, transaction, billing, fraud, or lifecycle coverage. The remaining 31 tools belong to unrelated data-research and prediction-market domains, leaving the stated credit-card purpose severely incomplete.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
Barcode / GTIN validation MCP (EAN-13, UPC-A, EAN-8, GTIN-14).
Related MCP Servers
- FlicenseAqualityBmaintenanceA local MCP server providing payment validation tools and resources, including card number Luhn checks, card network detection, and IBAN validation, with no network calls required.3-
- AlicenseNot gradedqualityBmaintenanceA hosted MCP server for AI-powered credit card advice, enabling search, comparison, portfolio analysis, and personalized recommendations for US credit cards through natural language.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables users to search and compare credit card recommendations, view card details and popular top-5 cards, and retrieve financial knowledge articles through MCP tools.-
- AlicenseAqualityCmaintenanceEmail validation MCP server using MailboxValidator API to determine validity of an email address.330 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.