Mastercard MCP. Validate cards, find merchants, and detect fraud with one call.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Mastercard MCP Server lets your AI client read and act on complex payment data. You can identify unknown cards using `bin_lookup`, validate account status before transactions via `validate_account`, or pinpoint nearby merchants that accept specific digital payments using `search_places`.
It gives you immediate access to fraud reporting, merchant classifications (`MCC`), and location intelligence without building custom API wrappers.
What your AI agents can do
Bin lookup
Identifies a payment card's issuer, type, and details from the first 6-8 digits of its number.
Bin lookup post
Performs the same card identification lookup as bin_lookup but uses a POST method for enhanced security when handling sensitive data.
Get merchant
Retrieves detailed information, including MCC codes and operating hours, for a specific merchant ID found through search.
Determines a payment card's issuer bank, type (credit/debit), category, country, and special flags using just the first 6-8 digits of the card number.
Checks if a full payment card number is currently active and valid for immediate transaction processing.
Searches nearby GPS coordinates to locate merchants that accept Mastercard, filtering results by specific business types (MCC codes).
Locates payment spots near GPS that specifically accept digital wallets like Apple Pay or Google Pay.
Files confirmed fraudulent transactions directly to Mastercard's database for network protection and risk mitigation.
Retrieves the full list of Merchant Category Codes, allowing you to classify businesses by industry type.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Mastercard: 12 Tools for Payments and Location Search
These twelve tools cover every aspect of payment intelligence—from identifying unknown BINs to locating specific merchants that accept digital wallets.
019d75d0bin lookup
Identifies a payment card's issuer, type, and details from the first 6-8 digits of its number.
019d75d0bin lookup post
Performs the same card identification lookup as `bin_lookup` but uses a POST method for enhanced security when handling sensitive data.
019d75d0get merchant
Retrieves detailed information, including MCC codes and operating hours, for a specific merchant ID found through search.
019d75d0get place details
Gets complete location details—address, coordinates, accepted payments—for a place identified by its unique location ID.
019d75d0merchant category codes
Lists all standard Merchant Category Codes (MCC) to classify businesses across various industries.
019d75d0merchant industry codes
Provides broader industry codes that group related MCCs for high-level business classification.
019d75d0nearby locations
Finds general points of interest and payment locations near given GPS coordinates, returning names, addresses, and distances.
019d75d0search merchants
Locates Mastercard-accepting merchants near specific GPS coordinates, optionally filtering by MCC code or distance radius.
019d75d0search places
Searches for merchant places using GPS with filters to find locations that support Apple Pay or Google Pay.
019d75d0search places by address
Finds nearby merchant places by accepting a street address (line 1, city, country) instead of requiring GPS coordinates.
019d75d0submit fraud report
Files confirmed fraudulent transactions directly to Mastercard's Fraud and Loss Database using required card details and type codes.
019d75d0validate account
Checks a full payment card number against the network to determine if it is active, valid, and ready for use.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Mastercard, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI client uses this server to handle everything related to Mastercard payments—from figuring out what a sketchy card is to locating legit merchants that take Apple Pay. You don't need a developer writing custom API wrappers just to check if a payment method works or where the nearest bodega is.
It gives your agent immediate access to fraud reporting, merchant types, and location data.
Card Intelligence & Validation
You wanna know what kind of card you're dealing with? Use bin_lookup or bin_lookup_post. You punch in just the first six to eight digits of a payment number, and it tells you the issuer bank, whether it's debit, credit, prepaid, and even what country it came from.
If security's your main gig, use the POST method with bin_lookup_post; it handles sensitive data better. Before you process anything, run validate_account with a full card number. This checks the network live to confirm if the account is actually active and ready for a transaction. It saves you from wasting time on a declined payment.
Location & Merchant Discovery
Need to find where to spend that cash? You've got three ways to search. If you know the coordinates, search_merchants finds spots near those GPS points that accept Mastercard. You can even filter those results by specific business types using MCC codes or narrow down a radius.
But what if you only care about digital wallets? Use search_places with GPS coordinates; it zeroes in on locations accepting Apple Pay or Google Pay. If you don't have GPS, no sweat. Just give your agent the street address—line 1, city, country—and let search_places_by_address do the heavy lifting to find those spots.
Once you find a place ID, you can get deep on the details. Use get_place_details to pull everything about that location: the full address, exact coordinates, and all accepted payment methods. If you found a merchant via search, use get_merchant with its specific ID to grab detailed info like operating hours or its official MCC code.
To keep your business smart, you can check out the classification tools first. Run merchant_category_codes to see the complete list of standard industry codes used across all types of businesses. If you need a higher-level view, merchant_industry_codes groups those smaller MCCs into broader sectors.
Risk Mitigation & Reporting
When fraud hits, time is money. Use submit_fraud_report to file confirmed fraudulent transactions directly into Mastercard's Fraud and Loss Database using the necessary card details and type codes. This protects the network and helps mitigate risk immediately.
How Mastercard MCP Works
- 1 Subscribe to the Mastercard server and provide your developer credentials.
- 2 Your AI client calls a tool (e.g.,
search_merchants) with input parameters like GPS coordinates and desired MCC code. - 3 The tool executes the API call, retrieves structured data (names, addresses, acceptance details), and passes that clean result back to your agent.
The bottom line is, you treat complex payment logic as a simple conversation with your AI client. No manual API calls are necessary.
Who Is Mastercard MCP For?
Fintech developers who can't afford to build out 12 separate APIs. Fraud analysts drowning in raw transaction data. E-commerce operators needing to optimize payment routing. If your job involves knowing 'what card type is this?' or 'where can I find a specific kind of store nearby?', this is for you.
Uses bin_lookup to quickly determine an issuer's profile and runs submit_fraud_report when suspicious activity hits, keeping the network clean.
Implements pre-transaction checks using validate_account or identifying card types via bin_lookup to reduce payment failure rates in new systems.
Uses search_places and search_merchants to guide clients to nearby locations that accept specific digital payments like Google Pay or Apple Pay.
What Changes When You Connect
- Saves time on payments by running
validate_accountfirst. Instead of processing a transaction only to get declined error codes, your agent confirms the card status upfront, improving conversion rates. - Stops guesswork about location search. You don't just find 'stores'; you use
search_placesto confirm if they actually accept Apple Pay or Google Pay at that specific spot. - Handles complex compliance tasks easily. Instead of manually querying MCC databases, the
merchant_category_codestool gives you instant access to global business classifications. - Reduces development effort by grouping tools. You get location search (
search_merchants), details retrieval (get_place_details), and category lookup all in one server, eliminating the need for multiple endpoints. - Strengthens security posture. Use
submit_fraud_reportto file confirmed fraud cases instantly. This helps protect both your client's funds and the entire payment network.
Real-World Use Cases
The Onboarding Check
A new e-commerce platform needs to verify if a user's card is usable before completing checkout. Instead of failing, your agent first calls validate_account using the full PAN. If it returns 'VALID,' you proceed with payment routing; otherwise, you prompt the user for different credentials.
The Tourist Guide
A travel app needs to guide users to restaurants in a new city that accept contactless payments. The agent first uses search_places_by_address with the hotel's address, then filters results using search_places to show only those confirming digital wallet support.
The Fraud Investigation
A compliance team gets an alert about a suspicious transaction. The agent runs bin_lookup on the card prefix to find out if it's a prepaid or commercial card, then uses that information to draft and submit the necessary report via submit_fraud_report.
The Inventory Planner
A retail chain needs to know where their competitors are located. The agent uses search_merchants near a specific radius, filtering by MCC codes (like '5812' for restaurants) to map out competitor density in an area.
The Tradeoffs
Treating location search as generic
Asking the agent: "Find me a store nearby." The result is vague, giving general points of interest but no payment acceptance data.
→
You must be specific. Use search_places and provide GPS coordinates AND specify that you need digital wallet support (e.g., Apple Pay). This guarantees the location accepts modern payment methods.
Ignoring card type checks
Attempting to process a transaction without checking if the account is active or what kind of card it is, leading to unnecessary failure handling.
→
Always run validate_account first. This gives you the status (VALID/INVALID) and card type (Credit/Debit) before any money changes hands.
Using wrong search input
Trying to find a merchant by coordinates when only the street address is available, causing the API call to fail.
→
If you have an address but no GPS points, use search_places_by_address. It handles the geocoding for you. If you have both, use search_merchants.
When It Fits, When It Doesn't
Use this server if your core business logic revolves around payment validation or location discovery (e-commerce, travel tech, fraud detection). The key is that you need to know why a card fails or if a physical store accepts modern payments. Don't use it if you just need general geographic data—use standard mapping APIs for simple point-to-point routing. However, don't rely on one tool alone; the true value comes from sequencing them: Start with search_places (location) -> Run get_place_details (confirmation) -> Check card status with validate_account (transaction safety). If you skip validation or search by address when coordinates are available, your integration will be brittle.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Mastercard. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 12 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Finding payment details used to feel like a massive manual chore today.
Currently, checking local commerce is a nightmare of tabs. You find an area on Google Maps, then you have to open the merchant's specific website (or even call them) just to confirm they accept Apple Pay or if their card type matches your processing requirements. Then you start another search just to see what other businesses are nearby.
With this Mastercard MCP Server, that process collapses into a single query. You ask for merchants near coordinates and specify payment capabilities. The agent runs `search_places` and gives you an immediate, structured list of locations that meet your exact criteria—no clicking through pages required.
The Mastercard MCP Server: Find Merchants by Location
Before this server, mapping out a service area meant juggling multiple specialized APIs: one for general merchant location, another for specific payment types (like contactless), and yet another to look up the business type (`MCC`). Each required custom endpoint setup.
Now, you let your AI agent handle the sequence. You ask for nearby merchants, and it orchestrates calls across `search_merchants`, `get_place_details`, and even `merchant_category_codes` if needed—all within one conversational flow. It’s built-in orchestration.
Common Questions About Mastercard MCP
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.
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.
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.
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.
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.
How do I use `merchant_category_codes` to understand business types? +
It lists every standardized Merchant Category Code (MCC). You can decode transaction data or filter searches by industry type. The codes classify businesses, like 5812 for restaurants or 4511 for airlines.
What if I only have a street address? How does `search_places_by_address` help? +
It finds merchants by using an address instead of GPS coordinates. You supply the address line 1, city, and country code; the tool handles the geocoding for you. This is useful when users don't know exact coordinates.
After I find a merchant ID, how do I use `get_merchant` to get all their contact info? +
You pass the unique Merchant ID to the tool. It returns full details including operating hours, complete addresses, and all accepted payment methods. This lets you go beyond basic search results.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Zenvia Conversion
Manage your Zenvia Conversion (Sirena) leads and messages directly through AI.
Salesforce Marketing Cloud
Manage campaigns, track member engagement, measure marketing ROI, and optimize lead generation through natural conversation.
Salesforce
Connect your Salesforce CRM to any AI agent — query records with SOQL, manage accounts, contacts, opportunities, run reports, and perform CRUD operations.
You might also like
Federal Register API
Access US public documents — audit rules and agencies via AI.
SendGrid Email Sender
This MCP does exactly one thing: it sends transactional emails using Twilio SendGrid. That's its only function, and nothing else. Incredible for giving your AI agents the ability to dispatch email reports.
IP Address Parser
Validate, parse, and classify any IPv4 or IPv6 address. Detect private vs public ranges, parse CIDR notation, and convert between IPv4 and IPv6. Powered by ipaddr.js — the engine behind Express.js.