4,000+ servers built on MCP Fusion
Vinkius
LlamaIndexFramework
LlamaIndex
Why use Mastercard MCP Server with LlamaIndex?

Bring Bin Lookup
to LlamaIndex

Create your Vinkius account to connect Mastercard to LlamaIndex and start using all 12 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Bin LookupBin Lookup PostGet MerchantGet Place DetailsMerchant Category CodesMerchant Industry CodesNearby LocationsSearch MerchantsSearch PlacesSearch Places By AddressSubmit Fraud ReportValidate Account
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Mastercard

What is the Mastercard MCP Server?

Connect Mastercard payment infrastructure to any AI agent and unlock powerful payment intelligence, fraud detection, merchant discovery, and card validation capabilities through natural conversation.

What you can do

  • BIN Lookup — Identify any payment card's issuer bank, card type (credit/debit/prepaid/commercial), category (Standard/Gold/Platinum/World/World Elite), issuing country, and special flags from just the first 6-8 digits
  • Account Validation — Verify if a payment card number is active and valid before processing transactions, reducing declined payments and fraud risk
  • Merchant Search — Find Mastercard-accepting merchants near any GPS coordinates, filterable by business category (MCC codes)
  • Places Discovery — Discover nearby payment-accepting locations with digital wallet support (Apple Pay, Google Pay, contactless)
  • Address-Based Search — Search for merchants by street address instead of coordinates for user-friendly location queries
  • Merchant Details — Retrieve complete information about specific merchants including addresses, MCC codes, and accepted payment methods
  • MCC Code Reference — Access the complete Merchant Category Code database to understand business classifications
  • Fraud Reporting — Submit confirmed fraudulent transactions to Mastercard's Fraud and Loss Database to protect the network
  • Nearby Locations — Discover ATMs, merchants, and points of interest around any geographic location

How it works

  1. Subscribe to this server
  2. Enter your Mastercard Developers Client ID and Client Secret
  3. Start querying payment intelligence from Claude, Cursor, or any MCP-compatible client

Your AI acts as a payment infrastructure assistant — no more navigating complex payment portals or writing custom API integrations. Get instant answers about cards, merchants, and transactions.

Who is this for?

  • Fintech Developers — validate cards, identify BINs, and reduce transaction declines by verifying accounts before processing payments
  • Fraud Analysts — quickly look up card issuer details, submit confirmed fraud reports, and investigate suspicious transactions through conversational AI
  • Travel & Concierge Services — find nearby merchants, discover payment-accepting locations with Apple Pay support, and help travelers understand local payment infrastructure
  • E-commerce Operators — identify card types before checkout to optimize payment routing, detect prepaid/commercial cards, and reduce cross-border processing fees

Built-in capabilities (12)

bin_lookup

Returns comprehensive card information including: issuer bank name, card type (credit/debit/prepaid/commercial), card category (Standard/Gold/Platinum/World/World Elite), issuing country, currency, and special flags (healthcare, payroll, purchasing). Use this to identify unknown cards, validate card ranges before transactions, determine cross-border fees, or understand the cardholder profile. The accountNumberPrefix parameter must be 6-8 numeric digits. Optional parameters (currencyCode, paymentType, merchantCategoryCode) provide more precise results for specific transaction contexts. Identify card issuer, type, and details from the first 6-8 digits of a payment card number

bin_lookup_post

Returns identical card identification data: issuer bank, card type, category, country, and product flags. Use this method when handling sensitive payment data in compliance-focused applications. The accountNumberPrefix should be 6-8 digits. Optional context parameters (currency, payment type, MCC) refine results. Identify card issuer using POST method for enhanced security with sensitive card data

get_merchant

Returns full address, contact information, MCC code, operating hours, and accepted payment methods. Use this to get in-depth information about a specific merchant location after finding it via search. The merchant ID is a unique identifier returned by the search_merchants tool. Get detailed information about a specific Mastercard-accepting merchant

get_place_details

Returns full address, coordinates, MCC code, payment methods accepted, operating hours, and other merchant attributes. Use this after a places search to drill down into a specific location. The locationId is returned by search_places or search_places_by_address tools. Get complete details for a specific merchant place by its location ID

merchant_category_codes

MCC codes are 4-digit numbers that classify businesses by type (e.g., 5411 = Grocery Stores, 5812 = Restaurants, 4511 = Airlines). Use this to understand merchant classifications, filter searches by business type, or decode MCC values found in transaction data. Optional limit parameter controls how many codes to return. List all Merchant Category Codes (MCC) used to classify business types

merchant_industry_codes

Industry codes group related MCC codes into higher-level categories. Use this to understand the hierarchical classification of merchants, analyze industry-level spending patterns, or build category navigation interfaces. List all merchant industry codes for broader business classification

nearby_locations

Returns names, addresses, categories, and distances from the search point. Use this for "what is nearby" queries, travel planning, or finding payment infrastructure in an area. Latitude and longitude are required. Radius in meters defines the search area. Limit controls maximum results returned. Discover points of interest and payment locations near GPS coordinates

search_merchants

Returns merchant names, addresses, MCC codes, and precise coordinates. Use this to find nearby payment-accepting locations, analyze merchant density in an area, or build "find merchants near me" features. Latitude and longitude are required as strings (e.g., "-23.5505", "-46.6333"). Radius is in meters (e.g., 5000 for 5km). Optionally filter by MCC category code (e.g., "5411" for grocery stores, "5812" for restaurants). Limit controls result count (max 50). Find Mastercard-accepting merchants near specific GPS coordinates filtered by category

search_places

Returns detailed merchant information including whether they accept Apple Pay, Google Pay, contactless payments, and their MCC classification. Use this when users need to find payment-accepting locations with specific digital wallet support. Latitude and longitude are required as numbers. Distance is in kilometers. Optionally filter by country code (ISO 3166-1 alpha-2) and payment capabilities (hasApplePay, hasGooglePay). Search for merchant places using GPS coordinates with payment method filters

search_places_by_address

The API geocodes the address internally. Returns nearby merchants with payment capability details (Apple Pay, Google Pay, contactless). Use this when users provide an address rather than GPS coordinates. Required: address line 1, city, country code, and postal code. Optional: state/province code (countrySubdivisionCode) for more precise results. Example: addressLine1="1600 Amphitheatre Pkwy", city="Mountain View", countryCode="US", postalCode="94043". Search for merchant places using a street address instead of coordinates

submit_fraud_report

This is a critical tool for issuers and processors to flag fraudulent transactions in real-time. Required fields: accountNumber (card number), transactionAmount, transactionCurrency (ISO 4217), and fraudTypeCode. Fraud type codes: "01" = Stolen Card Fraud, "02" = Never Received Card, "03" = Fraudulent Application, "04" = Counterfeit Card Fraud. Optional: fraudAmount (if different from transaction amount), transactionDate (YYYY-MM-DD). Use this only for confirmed fraud cases — never for suspected or disputed transactions. This helps Mastercard improve fraud detection and reduce false positives across the network. IMPORTANT: This action should only be performed by authorized fraud management personnel. Report a confirmed fraudulent transaction to Mastercard Fraud and Loss Database

validate_account

Returns validation status (VALID/INVALID), account type, and issuer information. Use this to verify card validity before processing transactions, reduce declined transactions, or perform account verification during onboarding. Required: accountNumber (full card number). Optional: expiryDate (MMYY format), cardholderName for enhanced validation. Handle card numbers securely — never log or store full PANs. Validate a payment card account number to check if it is active and valid

Why LlamaIndex?

LlamaIndex agents combine Mastercard tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine Mastercard tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain Mastercard tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query Mastercard, a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what Mastercard tools were called, what data was returned, and how it influenced the final answer

L
See it in action

Mastercard in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run Mastercard with Vinkius?

The Mastercard connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 12 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

Mastercard
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect Mastercard using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

Mastercard and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect Mastercard to LlamaIndex through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures Mastercard for LlamaIndex

Every request between LlamaIndex and Mastercard is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I identify what bank issued a card just from the first few digits?

Yes! Use the bin_lookup tool with the first 6-8 digits of the card number (the BIN). Mastercard will return the issuer bank name, card type (credit/debit/prepaid), card category (Gold/Platinum/World), issuing country, and flags like whether it's a commercial or healthcare card. For example, BIN 542418 reveals the exact issuing bank and card tier.

02

How can I find merchants that accept Mastercard near a specific location?

Use the search_merchants tool with latitude, longitude, and a search radius in meters. You can optionally filter by MCC code (e.g., "5812" for restaurants, "5411" for grocery stores). For example, searching with coordinates -23.5505, -46.6333 (São Paulo) and radius 5000 will return all Mastercard-accepting merchants within 5km. Results include merchant names, addresses, categories, and coordinates.

03

Can I verify if a payment card is valid before processing a transaction?

Yes! Use the validate_account tool with the full card number. It checks Mastercard records to determine if the card is active and valid, returning the validation status (VALID/INVALID), account type (credit/debit/prepaid), and issuer information. Optionally include expiry date (MMYY format) and cardholder name for enhanced validation. This helps reduce declined transactions and fraud risk. Never store full card numbers — handle them securely.

04

How do I report a confirmed fraudulent transaction to Mastercard?

Use the submit_fraud_report tool with the card number, transaction amount, currency (ISO 4217), and fraud type code. Fraud types: "01" = Stolen Card, "02" = Never Received Card, "03" = Fraudulent Application, "04" = Counterfeit Card. Optionally include fraud amount and transaction date. This submits to Mastercard's Fraud and Loss Database (FLD) to help reduce false positives across the network. IMPORTANT: Only authorized fraud management personnel should use this tool for confirmed cases.

05

Can I find merchants that accept Apple Pay or Google Pay near me?

Yes! Use the search_places tool with GPS coordinates and set hasApplePay=true or hasGooglePay=true to filter for merchants with those payment capabilities. Returns detailed merchant information including names, addresses, MCC codes, and which digital wallets they accept. For example, searching near Times Square (40.7580, -73.9855) with hasApplePay=true will show all nearby Apple Pay-enabled merchants.

06

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

07

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query Mastercard tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

08

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

09

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →