Manufact

mastercard-developers-mcp

developer.mcp.mastercard.com

Connect your AI assistant to Mastercard's developer platform. This server gives AI agents live access to Mastercard's full API catalog, including endpoint specs, request and response details, authentication guides for OAuth 1.0a, OAuth 2.0, and Open Finance, and structured documentation with code samples. Agents can discover services, retrieve integration guides, and generate accurate code without relying on stale training data.

Protocol: MCP 2025-11-25
Server version: 1.0.14
Supports: Tools

Overall score

Last reviewed at Oct 6, 2026, 14:17:15 UTC

Server metadata

3 of 8 fields30/1003 / 10 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

mastercard-developers-mcp

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.0.14

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools.

10/10Source

Protocol

Pass100/10020 / 20 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 1731ms

Source

Tools list returns results

9 tool(s) returned

Source

Resources list responds

0 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Pass100/10030 / 30 pts

Tool definitions, annotations, and client compatibility.

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

All tools have a display title

Source

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

All tools declare the three OpenAI behavior hints as booleans

Source

Tool names use valid characters

All tool names use valid characters

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Not applicable-Optional

App resources, metadata, and rendering requirements.

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

Tool invocation metadata present

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

View resource metadata complete

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

Tool documentation quality

9 tools reviewed80/10032 / 40 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

get-services-listTitles 99Descriptions 92Inputs 100Annotations 100Outputs 088/100

Title99/100

Get Services List

The title clearly communicates the tool’s action and subject. Keep it concise.

Description92/100

Lists all available Mastercard Developers Products and Services with their basic information including title, description, and service id. IMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use "serviceId" for each service for any tools that require serviceId as the parameter.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-services-list",
  "title": "Get Services List",
  "description": "Lists all available Mastercard Developers Products and Services with their basic information\nincluding title, description, and service id.\nIMPORTANT: The response contains both 'Products' (business offerings) and 'Services' (technical APIs with serviceIds). Use \"serviceId\" for each service for any tools that require serviceId as the parameter.\n",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-documentationTitles 95Descriptions 83Inputs 91Annotations 100Outputs 082/100

Title95/100

Get Documentation

The title clearly communicates the tool’s action and subject. Keep it concise.

Description83/100

Provides an overview of all available documentation for a specific Mastercard service including section titles, descriptions, and navigation links. It takes one argument: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')

Describe the returned information so the agent knows whether it will answer the request.

Inputs91/100

Input documentation gives an agent enough context to populate the arguments.

serviceId

The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')

Clear enough to supply this argument.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-documentation",
  "title": "Get Documentation",
  "description": "Provides an overview of all available documentation for a specific Mastercard service\nincluding section titles, descriptions, and navigation links.\n\nIt takes one argument:\n- serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "serviceId"
    ],
    "properties": {
      "serviceId": {
        "type": "string",
        "minLength": 1,
        "description": "The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-documentation-section-contentTitles 99Descriptions 72Inputs 75Annotations 100Outputs 076/100

Title99/100

Get Documentation Section Content

The title clearly communicates the tool’s action and subject. Keep it concise.

Description72/100

Retrieves the complete content for a specific documentation section. IMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together. It takes two arguments: - serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations') - sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

serviceId

The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

sectionId

The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-documentation-section-content",
  "title": "Get Documentation Section Content",
  "description": "\nRetrieves the complete content for a specific documentation section.\nIMPORTANT: A section is not a single page, but rather a collection of pages that are grouped together.\n\n\nIt takes two arguments:\n- serviceId (str): The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')\n- sectionId (str): The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')\n",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "serviceId",
      "sectionId"
    ],
    "properties": {
      "sectionId": {
        "type": "string",
        "minLength": 1,
        "description": "The specific section identifier within the service documentation (e.g., 'getting-started', 'api-reference')"
      },
      "serviceId": {
        "type": "string",
        "minLength": 1,
        "description": "The unique identifier of the Mastercard service (e.g., 'send', 'loyalty', 'locations')"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-documentation-pageTitles 100Descriptions 74Inputs 75Annotations 100Outputs 076/100

Title100/100

Get Documentation Page

The title clearly communicates the tool’s action and subject. Keep it concise.

Description74/100

Retrieves the complete content of a specific documentation page. Takes one argument: - pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

pagePath

The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-documentation-page",
  "title": "Get Documentation Page",
  "description": "Retrieves the complete content of a specific documentation page.\n\nTakes one argument:\n- pagePath (str): The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "pagePath"
    ],
    "properties": {
      "pagePath": {
        "type": "string",
        "pattern": "^\\/",
        "minLength": 1,
        "description": "The full path to the documentation page (e.g., '/send/documentation/use-cases/index.md')"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-oauth10a-integration-guideTitles 99Descriptions 84Inputs 75Annotations 100Outputs 079/100

Title99/100

Get OAuth 1.0a Integration Guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description84/100

Retrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

language

Programming language for language-specific examples and guidance

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-oauth10a-integration-guide",
  "title": "Get OAuth 1.0a Integration Guide",
  "description": "Retrieves the comprehensive OAuth 1.0a integration guide including step-by-step instructions,\ncode examples, and best practices for Mastercard APIs. Optionally specify a programming language\nto get language-specific examples and guidance.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "language": {
        "enum": [
          "java",
          "kotlin",
          "c#",
          "python",
          "javascript",
          "typescript",
          "golang",
          "others"
        ],
        "type": "string",
        "description": "Programming language for language-specific examples and guidance"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-oauth20-integration-guideTitles 100Descriptions 85Inputs 75Annotations 100Outputs 079/100

Title100/100

Get OAuth 2.0 Integration Guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description85/100

Retrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions, code examples, and best practices for Mastercard APIs. Optionally specify a programming language to get language-specific examples and guidance.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

language

Programming language for language-specific examples and guidance

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-oauth20-integration-guide",
  "title": "Get OAuth 2.0 Integration Guide",
  "description": "Retrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions,\ncode examples, and best practices for Mastercard APIs. Optionally specify a programming language\nto get language-specific examples and guidance.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "language": {
        "enum": [
          "java",
          "kotlin",
          "javascript",
          "typescript",
          "others"
        ],
        "type": "string",
        "description": "Programming language for language-specific examples and guidance"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-openfinance-integration-guideTitles 99Descriptions 82Inputs 100Annotations 100Outputs 085/100

Title99/100

Get Open Finance Integration Guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description82/100

Retrieves the comprehensive Open Finance (previously known as Open Banking) integration guide including setup instructions, API usage examples, and implementation best practices.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-openfinance-integration-guide",
  "title": "Get Open Finance Integration Guide",
  "description": "Retrieves the comprehensive Open Finance (previously known as Open Banking) integration\nguide including setup instructions, API usage examples, and implementation best practices.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-api-operation-listTitles 99Descriptions 78Inputs 75Annotations 100Outputs 077/100

Title99/100

Get API Operation List

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

Provides a summary of all API operations for a specific Mastercard API specification including HTTP methods, request paths, titles, and descriptions. It takes one argument: - apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

apiSpecificationPath

The path to the API specification file (e.g., /open-finance-us/swagger/openbanking-us.yaml)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-api-operation-list",
  "title": "Get API Operation List",
  "description": "Provides a summary of all API operations for a specific Mastercard API\nspecification including HTTP methods, request paths, titles, and descriptions.\n\nIt takes one argument:\n- apiSpecificationPath (str): The path to the API specification file e.g., '/open-finance-us/swagger/openbanking-us.yaml')",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "apiSpecificationPath"
    ],
    "properties": {
      "apiSpecificationPath": {
        "type": "string",
        "pattern": "^\\/",
        "description": "The path to the API specification file (e.g., /open-finance-us/swagger/openbanking-us.yaml)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

get-api-operation-detailsTitles 99Descriptions 81Inputs 75Annotations 100Outputs 078/100

Title99/100

Get API Operation Details

The title clearly communicates the tool’s action and subject. Keep it concise.

Description81/100

Provides detailed information about a specific API operation including parameter definitions, request and response schemas, and technical specifications for successful API calls. It takes three arguments: - apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for https://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml, https://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml, or /open-finance-us/swagger/openbanking-us.yaml) - method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE) - path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

apiSpecificationPath

The path to the API specification (e.g., /open-finance-us/swagger/openbanking-us.yaml)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

method

The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

path

The API endpoint path from the specification (e.g., /payments, /accounts/{id})

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-api-operation-details",
  "title": "Get API Operation Details",
  "description": "Provides detailed information about a specific API operation including parameter definitions,\nrequest and response schemas, and technical specifications for successful API calls.\n\nIt takes three arguments:\n- apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for\nhttps://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml,\nhttps://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml,\nor /open-finance-us/swagger/openbanking-us.yaml)\n- method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)\n- path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "apiSpecificationPath",
      "method",
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "pattern": "^\\/",
        "description": "The API endpoint path from the specification (e.g., /payments, /accounts/{id})"
      },
      "method": {
        "type": "string",
        "description": "The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)"
      },
      "apiSpecificationPath": {
        "type": "string",
        "pattern": "^\\/",
        "description": "The path to the API specification (e.g., /open-finance-us/swagger/openbanking-us.yaml)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Get Documentation Section ContentRetrieves the complete content for a specific documentation section.
02Get DocumentationProvides an overview of all available documentation for a specific Mastercard service
03Get Documentation PageRetrieves the complete content of a specific documentation page.
04Get OAuth 2.0 Integration GuideRetrieves the comprehensive OAuth 2.0 integration guide including step-by-step instructions,
05Get Services ListLists all available Mastercard Developers Products and Services with their basic information

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

About this server

Overview

Author: Mastercard
Verification: partner
Auth: None (public endpoint)
Category: Finance
Works with: claude
claude-desktop
claude-code
Docs: Documentation

Tools (9)

get-services-listget-documentationget-documentation-section-contentget-documentation-pageget-api-operation-listget-api-operation-detailsget-oauth10a-integration-guideget-oauth20-integration-guideget-openfinance-integration-guide

FAQ

mastercard-developers-mcp setup, tools, quality score, publishing readiness, and alternatives.

How do I add mastercard-developers-mcp to Claude, ChatGPT, or Cursor?

Add mastercard-developers-mcp to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://developer.mcp.mastercard.com/.

Is mastercard-developers-mcp MCP ready for ChatGPT and Claude?

As of October 6, 2026, mastercard-developers-mcp scores 100/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is mastercard-developers-mcp's MCP tool documentation?

As of October 6, 2026, mastercard-developers-mcp scores 80/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 9 of 9 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What tools does the mastercard-developers-mcp MCP server provide?

mastercard-developers-mcp provides these MCP tools: get-services-list, get-documentation, get-documentation-section-content, get-documentation-page, get-api-operation-list, get-api-operation-details, get-oauth10a-integration-guide, get-oauth20-integration-guide, and get-openfinance-integration-guide.

What are the best alternatives to mastercard-developers-mcp?

As of October 20, 2026, alternatives to mastercard-developers-mcp in financial-services on the Manufact MCP leaderboard include Contract-Factory — Sociétés & SIREN, Coverage Cat Insurance, Kavara Kirk, Perps Pulse, and CeylonCharts.

Does mastercard-developers-mcp MCP require authentication?

mastercard-developers-mcp does not require authentication. It is a public MCP endpoint you can connect without logging in.

How can mastercard-developers-mcp improve its MCP documentation?

get-documentation-section-content is the lowest-scoring reviewed tool at 76/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Who develops mastercard-developers-mcp?

mastercard-developers-mcp is developed by Mastercard. It is listed as partner on the Claude connector directory.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…

Title99/100

Get API Operation Details

The title clearly communicates the tool’s action and subject. Keep it concise.

Description81/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

apiSpecificationPath

The path to the API specification (e.g., /open-finance-us/swagger/openbanking-us.yaml)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

method

The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

path

The API endpoint path from the specification (e.g., /payments, /accounts/{id})

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations100/100

All four behavior hints are declared.

{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get-api-operation-details",
  "title": "Get API Operation Details",
  "description": "Provides detailed information about a specific API operation including parameter definitions,\nrequest and response schemas, and technical specifications for successful API calls.\n\nIt takes three arguments:\n- apiSpecificationPath (str): The path to the API specification file (e.g. The path would be /open-finance-us/swagger/openbanking-us.yaml for\nhttps://static.developer.mastercard.com/content/open-finance-us/swagger/openbanking-us.yaml,\nhttps://developer.mastercard.com/open-finance-us/swagger/openbanking-us.yaml,\nor /open-finance-us/swagger/openbanking-us.yaml)\n- method (str): The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)\n- path (str): The API endpoint path from the specification (e.g., /payments, /accounts/{id})",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "apiSpecificationPath",
      "method",
      "path"
    ],
    "properties": {
      "path": {
        "type": "string",
        "pattern": "^\\/",
        "description": "The API endpoint path from the specification (e.g., /payments, /accounts/{id})"
      },
      "method": {
        "type": "string",
        "description": "The HTTP method of the operation (e.g., GET, POST, PUT, DELETE)"
      },
      "apiSpecificationPath": {
        "type": "string",
        "pattern": "^\\/",
        "description": "The path to the API specification (e.g., /open-finance-us/swagger/openbanking-us.yaml)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  }
}

Manufact

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title99/100

Description92/100

Inputs100/100

Annotations100/100

Output schema0/100

Title95/100

Description83/100

Inputs91/100

Annotations100/100

Output schema0/100

Title99/100

Description72/100

Inputs75/100

Annotations100/100

Output schema0/100

Title100/100

Description74/100

Inputs75/100

Annotations100/100

Output schema0/100

Title99/100

Description84/100

Inputs75/100

Annotations100/100

Output schema0/100

Title100/100

Description85/100

Inputs75/100

Annotations100/100

Output schema0/100

Title99/100

Description82/100

Inputs100/100

Annotations100/100

Output schema0/100

Title99/100

Description78/100

Inputs75/100

Annotations100/100

Output schema0/100

Title99/100

Description81/100

Inputs75/100

Annotations100/100

Output schema0/100

Put your MCP to the test

About this server

Overview

Related MCP servers

FAQ

Not your MCP?

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title99/100

Description92/100

Inputs100/100

Annotations100/100

Output schema0/100

Title95/100

Description83/100

Inputs91/100

Annotations100/100

Output schema0/100

Title99/100

Description72/100

Inputs75/100

Annotations100/100

Output schema0/100

Title100/100

Description74/100

Inputs75/100