Get agent-economy payment metrics with real vs nominal volume separation. Filter out wash trading. Three views: summary KPIs, daily trends, top seller leaderboards across x402 and other protocols.
MIT
364,958 tools. Last updated 2026-08-02 02:20
"MasterCard" matching MCP tools:
- Check a payment card number's structural validity: verify Luhn checksum, detect brand (Visa, Mastercard, etc.), and confirm correct length. Do not assume a card is valid.Apache 2.0
- Validate credit card numbers using the Luhn algorithm and detect the card brand (Visa, Mastercard, Elo, Hipercard, Amex, Diners, JCB, Discover).MIT
- Verify a payment card number's structural validity: validate the Luhn checksum, detect the brand from the BIN, and check the correct length before using the number.Apache 2.0
- Check rental car CDW/LDW coverage provided by a credit card using the card product name or BIN and provider.MIT
- Scan log files for sensitive data like PII, credentials, API keys, and tokens. Redact matches or filter by category to control results.MIT
Matching MCP Servers
- Flicense-qualityDmaintenanceAn MCP server that provides access to Mastercard's BIN Table Resource API, allowing users to look up and interact with Bank Identification Number data through natural language queries.Last updated
- FlicenseCqualityBmaintenanceA standalone MCP server wrapping Mastercard Open Finance US (Finicity) APIs for open banking operations, enabling financial data access and payment services.Last updated62
- Validate credit card numbers using Luhn checksum and identify the issuing network from the BIN prefix. Checks brand-specific length and formatting, all processed locally without external lookups.MIT
- Compare agentic payment protocols across credential, signing, scope, rail, identity, and audit dimensions. Get a recommendation for your scenario.MIT
- Filter and retrieve merchant transactions by status, amount, date, card brand, customer email, and more. Returns paginated results with customer and payment details.MIT
- Retrieve daily activity balances broken down by card network, including PIN and signature purchase volumes. Use the 'expand' parameter to break out specific transaction types per network for detailed network-specific transaction analysis.MIT
- Validate credit card numbers using Luhn algorithm. Detect card brand (Visa, Mastercard, Amex, Discover, etc.) and return validity with masked number.MIT
- Order a Mastercard debit card, choosing between instant virtual card or physical delivery by post.
- Submit payment to complete a checkout session and finalize a purchase at a UCP-enabled merchant.MIT
- Order a Mastercard credit card for a user, choosing between immediate virtual delivery or physical card by post.
- Validate a credit/debit card number (keyless, offline): Luhn (mod-10) checksum, detected card network (Visa/Mastercard/Amex/Discover/JCB/Diners/UnionPay/Maestro), and whether the length is valid for that network. Spaces/dashes are ignored. NOTE: this checks the number is well-formed — it does NOT verify the card is real/active/funded (that needs a payment processor).Connector
- USE THIS to check a payment card number's structure before using it — never assume a card number is valid or guess its brand. Verifies the Luhn checksum, detects the brand (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay) from its BIN, and checks the length. Does NOT check whether the card is real, active or has funds.Connector
- Compare agentic payment protocols (AP2, ACP/Shared Payment Token, x402, Visa TAP, Mastercard Agent Pay) across credential, signing, scope, rail, identity, and audit dimensions; optionally recommend a fit for a scenario. Use when a developer or strategist needs to orient across the fragmenting agentic-payments standards. Renders the interactive AINumbers tool as a widget; inputs are applied via the AIN Bridge and the tool runs client-side (zero PII, zero network).Connector
- Look up rental car CDW/LDW coverage provided by a credit card. Provide EITHER credit_card_product_name OR card_number_bin + card_provider. Args: credit_card_product_name: Exact card product name (preferred when known). card_number_bin: First 6-8 digits of the card number (BIN). card_provider: Card network ("visa", "mastercard", "amex", or "discover"). Required with card_number_bin. Returns: Coverage type, max days, and a human-readable summary.Connector
- P75 registry aggregation: the cross-lens join applied to agent identity. Incumbent providers each consult only their own registry; this endpoint checks every registry TunnelMind can reach and labels each answer with an explicit state, so a gap can never be mistaken for a clean result: - `observed` — the subject IS in this registry (record attached) - `not_present` — checked, and it isn't (an observation, not a gap) - `not_applicable` — the registry doesn't key on this subject type - `degraded` — the check failed (timeout, upstream error) - `unavailable` — the registry is not publicly consultable (closed / platform-scoped); stated in-band because silence would read as clean Registries (v0): `crawler_ranges` (operator-published IP feeds — Googlebot, GPTBot, PerplexityBot…), `wba_directory` (RFC 9421 Signature-Agent JWKS at the subject domain), `mcp_registry` (registry.modelcontextprotocol.io), `tunnelmind_known_agents` (curated verifiable/claim-only set), plus honest `unavailable` rows for Visa TAP, Mastercard Agent Pay, and Cloudflare Verified Bots. Use this tool when: - You are deciding whether an agent, bot, or MCP server is registered anywhere that vouches for it — in one call instead of five. - You need the blind spots stated: which registries could NOT be consulted for this subject, and why. Inputs: subject — an IP (registry membership by published ranges), a domain (WBA directory + MCP registry), or an agent name/UA fragment (e.g. `gptbot`, `claudebot`). `?receipt=true` attaches a signed Receipt v1.0 committed to the transparency log. Latency: remote registry checks are KV-cached for 1h; a warm call is edge-fast, a cold one bounded by 5s per-registry timeouts.Connector
- Returns a quote for a VISA/Mastercard card charge. STEP 1 in charging a tokenised Visa/Mastercard. Returns a quote for a VISA/Mastercard card charge. Cards are charged in ZAR. A fee is levied for each charge. This end point only performs a quote, no cards are charged. The quote is valid for 10 minu @param api_key: The api key allocated to your application @param token: The wallet_api_token provided by /access/login @param wallet_fk: The wallet_fk @param account_fk: The account_fk (this is a database ID (int) not an account address (str) and may not be 0) The account_fk provided by /wallet/accounts_list @param amount: The amount in currency of the account_fk. All cards are charged in ZAR but a conversion of this amount to ZAR will be automatically performed. On top of this amount a fee with be charged equal to 3.5% for fees and insurance plus South African VAT of 15% (only on the fee portion). @return: a json objectConnector