Mastercard MCP Server for CrewAI 12 tools — connect in under 2 minutes
Connect your CrewAI agents to Mastercard through Vinkius, pass the Edge URL in the `mcps` parameter and every Mastercard tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Mastercard Specialist",
goal="Help users interact with Mastercard effectively",
backstory=(
"You are an expert at leveraging Mastercard tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Mastercard "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 12 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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.
When paired with CrewAI, Mastercard becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Mastercard tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
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 CrewAI 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 CrewAI via MCP
Follow these steps to integrate the Mastercard MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 12 tools from Mastercard
Why Use CrewAI with the Mastercard MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Mastercard through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Mastercard + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Mastercard MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Mastercard for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Mastercard, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Mastercard tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Mastercard against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Mastercard MCP Tools for CrewAI (12)
These 12 tools become available when you connect Mastercard to CrewAI 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 CrewAI
Ready-to-use prompts you can give your CrewAI 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 CrewAI
Common issues when connecting Mastercard to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Mastercard + CrewAI FAQ
Common questions about integrating Mastercard MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Mastercard with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Mastercard to CrewAI
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.