Mastercard Developers

Read Mastercard's API catalog, docs and integration guides.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Mastercard Developers connector does

The Mastercard Developers MCP server connects Mastercard's developer platform — its API catalog, documentation and integration guides — to Claude, ChatGPT and any MCP-compatible agent. All nine tools are read-only lookups against public documentation. None of them moves money, creates a transaction, or issues a payment credential. No sign-in is required.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Mastercard Developers tools (9)

  • 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
  • get-openfinance-integration-guide

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The hosted endpoint was down when we checked. Every request to https://developer.mcp.mastercard.com/ returned HTTP 504 from AkamaiGHost on 2026-08-22 — across the root, /mcp, /sse and /message, on three separate attempts, and on GET as well as POST. A nonsense control path returned the identical error, so this is an edge gateway failing to reach the origin, not a routing mistake on our side. The local npm package was unaffected.
  • We could not verify the auth posture over the wire. Because of that outage, no handshake succeeded and no RFC 9728 descriptor was readable. "No authentication" is Mastercard's documented instruction and the directory's is_authless flag — both are evidence about the posture, not our observation of it, so this page does not record the auth mode as verified.
  • No OAuth scopes exist, because there is no OAuth. There is no consent screen and no grant to narrow. That is not a boundary weakness here — with nine read-only tools against public documentation, there is nothing a scope would usefully separate.
  • Tool annotations come from source, not from a live handshake. We read readOnlyHint and destructiveHint in the published repository at commit 24df3ad, dated 2026-05-16. The deployed remote server may run a different build, and we could not confirm which.
  • The nominated documentation URL renders nothing to a fetcher. It returns a 1,629-byte JavaScript shell with no embedded payload — 2 words of text. The readable documentation lives at the same path with index.md appended. llms-full.txt is sign-in walled, and sitemap.xml returns 401.
  • The site-wide llms.txt does not mention MCP at all. It is a 21,000-word catalog of Mastercard's products and services with no reference to the agent toolkit or any tool name, so it is useless as a second enumeration despite being the largest doc route.
  • Documentation accuracy depends on Mastercard's published pages. The connector returns what developer.mastercard.com serves. Generated code samples should be verified against the API reference before use, particularly for OAuth 1.0a request signing.
  • We never called a tool. Every finding here comes from reading published source, documentation and the directory snapshot, plus unauthenticated probes of the endpoint.

Frequently asked questions

Can the Mastercard Developers MCP server move money or make a payment?

No. All nine tools read documentation and API specifications, and none initiates a transaction. Mastercard's published client source pins every request to the GET method against developer.mastercard.com, so no tool can write anywhere. The connector describes Mastercard's payment APIs; it does not call them.

Does the Mastercard connector touch cardholder data or PCI-scoped material?

No. The tools fetch public developer documentation, OpenAPI specifications and integration guides from developer.mastercard.com, which requires no sign-in. There is no account, no card number and no transaction record in the surface, so nothing it returns falls in PCI scope. It reads reference material, not production data.

Why does get-api-operation-details accept DELETE if nothing can be deleted?

Because the method is a lookup key, not a verb it will send. The tool takes an HTTP method and a path to identify which operation in an OpenAPI specification to describe. Mastercard's client forwards both as query-string filters on a GET request, so asking about DELETE /accounts returns that operation's schema.

Does the Mastercard Developers MCP server require authentication?

No. Mastercard's own setup documentation instructs users to select No Authentication when adding the connector, and the directory records the server as authless. We could not confirm this over the wire because the endpoint returned an Akamai gateway error on every request we made on 2026-08-22.

How many tools does the Mastercard Developers MCP server have?

Nine, and this is one of the rare cases where that count is firm. Mastercard publishes the tool registry in its open-source repository, and the nine exported names match Anthropic's directory listing exactly, character for character. The documentation table lists the same nine, with one typo.

What is the Mastercard Developers Agent Toolkit?

It is Mastercard's package for connecting AI assistants to its developer platform. It ships two things: a hosted remote MCP server, and an npm SDK that runs the same nine tools locally. Despite the name, it generates no per-account tools, so the reachable operation count equals the tool count.

Can the connector read Mastercard documentation that is not public?

No. Every request goes to developer.mastercard.com without credentials, so the server reaches exactly what an anonymous browser reaches. Pages behind Mastercard's developer sign-in return an authentication error to the connector as they would to anyone. It cannot widen its own access.

How do I limit the Mastercard MCP server to a single service?

Pass --service or --api-specification when running the local npm server. Mastercard documents that either flag scopes the agent to one service's documentation, that --api-specification wins when both are set, and that setting either disables get-services-list. The hosted remote server accepts no such flags.

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Mastercard Developers to work.

Connect Mastercard Developers once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.