Authoryze vs Mastercard Developers MCP
Authoryze is an MCP server published by authoryze.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Mastercard Developers MCP is an MCP server published by Mastercard. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Authoryze |  Mastercard Developers MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Downloads/month (npm): 332 Downloads/week (npm): 62 Forks (GitHub): 37 Stars (GitHub): 55 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Authoryze | Mastercard Developers MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 55 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 37 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (authoryze.ai/api/mcp) | On your machine (@mastercard/developers-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kevinfee3/authoryze-mcp | github.com/mastercard/developers-agent-toolkit |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Authoryze
Give your AI agent a spending limit: approval controls and single-use virtual cards.
Mastercard Developers MCP
Access Mastercard Developers APIs, documentation, and API specifications through MCP.
How to run each
Authoryze As a remote MCP server
claude mcp add --transport http authoryze https://authoryze.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Mastercard Developers MCP As a local MCP server: npm package
claude mcp add --transport stdio developers-mcp -- npx -y @mastercard/developers-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Authoryze has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Authoryze · What it can do: Mastercard Developers MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.