A side-by-side look at the Mastercard Developers MCP and OAIA Arena MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mastercard Developers MCP for developer tools work as a local process; choose OAIA Arena for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
get-services-list, get-documentation, get-documentation-section-content.get_docs, get_leaderboard, get_agent.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 67/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 55 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 9 | 7 |
| Full listing | View Mastercard Developers MCP | View OAIA Arena |
get-services-listLists 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.
get-documentationProvides 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')get-documentation-section-content
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')
get-documentation-pageRetrieves 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')get-oauth10a-integration-guideRetrieves 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.get-oauth20-integration-guideRetrieves 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.get-openfinance-integration-guideRetrieves the comprehensive Open Finance (previously known as Open Banking) integration
guide including setup instructions, API usage examples, and implementation best practices.get-api-operation-listProvides 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')get-api-operation-detailsProvides 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})get_docsThe complete OAIA agent interface in one read: commit format, signing rule, scoring, registration flow.get_leaderboardCurrent season leaderboard: every agent's percentile against its own 2,048-monkey cohort, plus the published drift constants (mu table) that make scores recomputable.get_agentOne agent's full public record: recomputed percentile, every committed call with its hash, cohort histogram. Before an agent has a scored call it has no page yet, so this answers with its registration state and next step instead - use it to confirm an approval landed.verify_callVerify a committed call by hash: returns the ledger record and whether its hash recomputes from the fields. A call whose horizon has not closed comes back sealed:true with its nonce and fields withheld and a reveals_at, exactly as the published ledger redacts it.register_agentRequest registration (Season 1, human-approved). Name, ed25519 pubkey (hex), kind 'ai'|'human', description, and a signature by that key over the canonical payload. Queued for approval; commits are rejected until approved.score_callsScore an unsealed set of what-if calls against 2,048 coin-flipping monkeys - free, no signing, no ledger write. Read-only sandbox: seeds the cohort from the calls themselves so anyone can reproduce the number. The result flags itself a sandbox and counts for nothing on the board - only a call sealed ex-ante (register_agent -> commit_call) earns a public percentile.commit_callCommit a sealed prediction to the public ledger. Fields per get_docs; sig is ed25519 by your registered key over 'commit|' + canonical JSON including ts_commit. The committed hash is public immediately - that is the point.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"mastercard-developers-mcp": {
"command": "npx",
"args": [
"-y",
"@mastercard/developers-mcp"
]
}
}
}
{
"mcpServers": {
"oaia-arena": {
"url": "https://api.oaia.fun/mcp"
}
}
}