WalletWallet: Apple and Google Wallet passes vs io.github.ivangr1/walletap
WalletWallet: Apple and Google Wallet passes is an MCP server published by walletwallet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ivangr1/walletap is an MCP server published by ivangr1. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  WalletWallet: Apple and Google Wallet passes |  io.github.ivangr1/walletap |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (npm): 323 Downloads/week (npm): 26 Forks (GitHub): 1 Stars (GitHub): 0 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 | WalletWallet: Apple and Google Wallet passes | io.github.ivangr1/walletap |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.walletwallet.dev/mcp) | On your machine (@walletap/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/ivangr1/walletap-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | 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
WalletWallet: Apple and Google Wallet passes
Create, update, and revoke Apple Wallet and Google Wallet passes from any MCP client.
io.github.ivangr1/walletap
Issue and manage Apple Wallet & Google Wallet passes from any AI assistant.
How to run each
WalletWallet: Apple and Google Wallet passes As a remote MCP server
claude mcp add --transport http wallet-passes https://api.walletwallet.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.ivangr1/walletap As a local MCP server: npm package
claude mcp add --transport stdio walletap -- npx -y @walletap/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only WalletWallet: Apple and Google Wallet passes 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
The marketplaces of WalletWallet: Apple and Google Wallet passes publish no settings it asks for, so we do not compare settings.
What it can do: WalletWallet: Apple and Google Wallet passes · What it can do: io.github.ivangr1/walletap · 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.