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.

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.

Mastercard MCP Server for AutoGen 12 tools — connect in under 2 minutes

Name: Mastercard
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 12 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Mastercard as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="mastercard_agent",
            tools=tools,
            system_message=(
                "You help users with Mastercard. "
                "12 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About 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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Mastercard tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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

The Mastercard MCP Server exposes 12 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Mastercard to AutoGen via MCP

Follow these steps to integrate the Mastercard MCP Server with AutoGen.

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 12 tools from Mastercard automatically

Why Use AutoGen with the Mastercard MCP Server

AutoGen provides unique advantages when paired with Mastercard through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Mastercard tools to solve complex tasks

Role-based architecture lets you assign Mastercard tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Mastercard tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Mastercard tool responses in an isolated environment

Mastercard + AutoGen Use Cases

Practical scenarios where AutoGen combined with the Mastercard MCP Server delivers measurable value.

Collaborative analysis: one agent queries Mastercard while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Mastercard, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Mastercard data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Mastercard responses in a sandboxed execution environment

Mastercard MCP Tools for AutoGen (12)

These 12 tools become available when you connect Mastercard to AutoGen via MCP:

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

Example Prompts for Mastercard in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with Mastercard immediately.

"What type of card is 542418 and which bank issued it?"

"Find restaurants near São Paulo city center that accept Mastercard within 3km."

"Validate card number 5123456789012346 before I process this payment."

Troubleshooting Mastercard MCP Server with AutoGen

Common issues when connecting Mastercard to AutoGen through the Vinkius, and how to resolve them.

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Mastercard + AutoGen FAQ

Common questions about integrating Mastercard MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Mastercard tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.