Handover.tools vs Mastercard Developers… | AllMCPs
Handover.tools vs Mastercard Developers MCP
A side-by-side look at the Handover.tools 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 Handover.tools for developer tools work; choose Mastercard Developers MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
H
Choose Handover.tools when
You need dedicated capabilities in the domain.
Developer Tools
Its auth model fits you: No auth required.
You want tools like handoff_put, handoff_get, handoff_revoke.
handoff_putStore a piece of context and get back a short code. The person gives the link handover.tools/<code> to an agent on another device and it can fetch the content — no copy-paste of long text. The code is 8 letters, easy to type on a phone. NOT ENCRYPTED: the server can read what you store, so never put credentials, tokens, or private data in it. Content becomes unreadable after the TTL expires, and by default it can only be fetched once. The response also returns a revoke_key — keep it for the rest of this session so you can destroy the content immediately with handoff_revoke if the person changes their mind. Writes are limited to a small number per day; reads are not.
handoff_getFetch content stored by handoff_put using its 8-character code. The code is case-insensitive and hyphens are ignored, so 'kvmtrhxp' and 'KVMT-RHXP' are the same; the person may give it as a link like handover.tools/kvmtrhxp, and passing that is fine too. Return the content to the person verbatim and complete: it can be fetched only once. If the code is unknown, already fetched, or expired, content is null with a reason — these cases are deliberately indistinguishable.
handoff_revokeDestroy content stored by handoff_put right now, before its TTL runs out and whether or not it has been fetched. Requires the revoke_key returned by handoff_put — the person fetching with the short code cannot revoke, only the writer can. Use this the moment someone says they sent the wrong thing, or changed their mind. Revoking an already gone item is not an error: the outcome is reported as 'already_gone'.
channel_openStart pairing two agents on different machines for a multi-round exchange (e.g. one explores, the other studies and asks follow-up questions). Use the local client at https://handover.tools/client/channel.py — do not call this by hand. The client generates a secret password locally, and this call returns only a 3-character nameplate; the person gives nameplate + password (8 letters) to the other machine. The server never sees the password, so it cannot impersonate either side (SPAKE2). The person stays in the loop: send only after they approve, fetch only when they ask. Counts as one write against the daily write quota.
channel_joinSecond half of pairing, run by the local client at https://handover.tools/client/channel.py. Send only the first 3 characters of the spoken code (the nameplate) plus this side's SPAKE2 message; the other 5 characters are the password and must never be sent to the server. The nameplate is consumed on success. Returns this side's key and the peer's SPAKE2 message. Unknown, used, or expired nameplates are deliberately indistinguishable.
channel_sendRelay one ciphertext to the other side of a paired channel. The ciphertext must come from the local client at https://handover.tools/client/channel.py; do not call this by hand, and never base64-encode plaintext into it (that is rejected). Only send after the person has seen and approved the draft — the server cannot enforce this, the calling agent must. Returns the message's sequence number and how far the peer has read.
channel_fetchUse the local client at https://handover.tools/client/channel.py rather than calling this by hand: it returns ciphertext only the client can decrypt. Returns the peer's messages this side has not fetched yet, and marks them read so the peer can see they arrived. Call only when the person asks. peek=true reads without marking; after=N re-reads from sequence N (recovery). Side A also receives the peer's SPAKE2 message here to finish pairing. Large backlogs are paged: more=true means fetch again.
channel_closeEither side can close. Deletes the channel, both keys, and every stored message immediately. The other side's next fetch reports not_found_or_closed.
Mastercard Developers MCP tools 9
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-list
Ready-to-paste client configs
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.
Handover.tools
No confirmed install command for Handover.tools yet — follow the setup steps linked from its listing page rather than a guessed package name.
Handover.tools is categorized under Developer Tools and uses an install path we have not confirmed yet. Mastercard Developers MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Handover.tools for developer tools work and Mastercard Developers MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Handover.tools has no confirmed install command yet — follow its own setup instructions.
Handover.tools is listed as free. Auth: no auth required. Mastercard Developers MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add handover-tools and mastercard-developers-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Handover.tools has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Mastercard Developers MCP has 67/100 (Great) with 2 views, 0 installs and 55 GitHub stars.
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')
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})