2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 12 Tools SDK

Mastra AI is a TypeScript-native agent framework built for modern web stacks. Connect Mastercard through the Vinkius and Mastra agents discover all tools automatically — type-safe, streaming-ready, and deployable anywhere Node.js runs.

Vinkius supports streamable HTTP and SSE.

typescript
import { Agent } from "@mastra/core/agent";
import { createMCPClient } from "@mastra/mcp";
import { openai } from "@ai-sdk/openai";

async function main() {
  // Your Vinkius token — get it at cloud.vinkius.com
  const mcpClient = await createMCPClient({
    servers: {
      "mastercard": {
        url: "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
      },
    },
  });

  const tools = await mcpClient.getTools();
  const agent = new Agent({
    name: "Mastercard Agent",
    instructions:
      "You help users interact with Mastercard " +
      "using 12 tools.",
    model: openai("gpt-4o"),
    tools,
  });

  const result = await agent.generate(
    "What can I do with Mastercard?"
  );
  console.log(result.text);
}

main();
Mastercard
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.

Mastra's agent abstraction provides a clean separation between LLM logic and Mastercard tool infrastructure. Connect 12 tools through the Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution — deployable to any Node.js host in one command.

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 Mastra AI 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 Mastra AI via MCP

Follow these steps to integrate the Mastercard MCP Server with Mastra AI.

01

Install dependencies

Run npm install @mastra/core @mastra/mcp @ai-sdk/openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.ts and run with npx tsx agent.ts

04

Explore tools

Mastra discovers 12 tools from Mastercard via MCP

Why Use Mastra AI with the Mastercard MCP Server

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

01

Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure — add Mastercard without touching business code

02

Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

03

TypeScript-native: full type inference for every Mastercard tool response with IDE autocomplete and compile-time checks

04

One-command deployment to any Node.js host — Vercel, Railway, Fly.io, or your own infrastructure

Mastercard + Mastra AI Use Cases

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

01

Automated workflows: build multi-step agents that query Mastercard, process results, and trigger downstream actions in a typed pipeline

02

SaaS integrations: embed Mastercard as a first-class tool in your product's AI features with Mastra's clean agent API

03

Background jobs: schedule Mastra agents to query Mastercard on a cron and store results in your database automatically

04

Multi-agent systems: create specialist agents that collaborate using Mastercard tools alongside other MCP servers

Mastercard MCP Tools for Mastra AI (12)

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

01

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

02

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

03

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

04

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

05

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

06

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

07

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

08

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

09

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

10

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

11

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

12

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 Mastra AI

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

01

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

02

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

03

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

Troubleshooting Mastercard MCP Server with Mastra AI

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

01

createMCPClient not exported

Install: npm install @mastra/mcp

Mastercard + Mastra AI FAQ

Common questions about integrating Mastercard MCP Server with Mastra AI.

01

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
02

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
03

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

Connect Mastercard to Mastra AI

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.