A side-by-side look at the GateCore Marketplace and Mastercard Developers MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GateCore Marketplace for developer tools work over a hosted endpoint; choose Mastercard Developers MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
discover_listings, get_listing, procure.get-services-list, get-documentation, get-documentation-section-content.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 55/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 55 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 8 | 9 |
| Full listing | View GateCore Marketplace | View Mastercard Developers MCP |
discover_listingsDiscover governed GateCore marketplace capabilities with machine-readable pricing,
required scopes, and minimum trust terms. Results preserve the marketplace's organic order.get_listingFetch one governed marketplace listing and its machine-enforceable contract terms:
price, required scopes, minimum trust, target, and data classification.procureRequest governed procurement for a listing. In public full mode, identity comes from
the MCP access key, trust comes from GateCore's baseline, and the result is a PROCURE,
REVIEW, or DENY decision with gateway delegation when eligible.authorize_accessAuthorize signed access to a governed listing. Purpose is forwarded unchanged when
present; policy at the gateway decides whether the declared purpose is allowed.complete_accessHash seller output locally, attest completion with the buyer agent key, and return
the terminal signed receipt. Seller output itself is never forwarded or returned.list_procurementsList procurement decisions for the credential tenant in public modes.request_listing_accessSubmit an idempotent listing-access request for the credential's tenant and agent.submit_leadSubmit a consented consumer lead to a supported published listing.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})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": {
"gatecore-marketplace": {
"url": "https://mcp.gatecoreai.com/mcp"
}
}
}
{
"mcpServers": {
"mastercard-developers-mcp": {
"command": "npx",
"args": [
"-y",
"@mastercard/developers-mcp"
]
}
}
}