walletmcppass: Apple Wallet passes MCP server
com.walletmcppass/wallet-mcpwalletmcppass.comstreamable-httpv1.2.0Scanned
Create signed Apple Wallet passes (.pkpass), singly or in bulk: boarding passes, tickets, coupons.
4 tools: 2 can delete or cancel things and 2 do something that can't be undone.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the walletmcppass: Apple Wallet passes MCP server can do
The walletmcppass: Apple Wallet passes MCP server is published by walletmcppass.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (2 tools: update_wallet_pass and update_wallet_pass_batch) and do things that cannot be undone, such as sending, paying or publishing (create_wallet_pass and create_wallet_pass_batch). None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Deletes or cancels 2Claude Code: deny
update_wallet_passChange a pass made with create_wallet_pass(updatable=True); every iPhone that added it refreshes.No findings
Why it is in this group
- The name "update_wallet_pass" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change a pass made with create_wallet_pass(updatable=True); every iPhone that added it refreshes. Takes the serial_number and edit_token returned when the pass was created, the required contact_email and x402_ready, plus any of create_wallet_pass's parameters (x402_payment included), with the same meanings. Each parameter given replaces the stored value completely (a fields list replaces the whole list, so resend unchanged fields too); parameters left out keep their current values. Clear a text value with "" and a list with []. To cancel a pass, set voided=True: Wallet marks it void on every iPhone. Wallet asks the server for the new version as soon as Apple delivers the push, usually within seconds. A field's changeMessage is shown on the lock screen when that field's value changes. Only works until the pass's updatable_until time (set by updatable_hours at creation). Returns {download_url, expires_in_seconds, serial_number, pass_type_identifier, notified_devices, updatable_until}. notified_devices counts the iPhones the push was sent to, not ones that have already refreshed. The download_url (valid 1 hour) is only needed to add the pass to a new device. With x402_ready=False the result also has x402_setup, as for create_wallet_pass.
Annotations the server declares
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
- title: Update Apple Wallet pass
update_wallet_pass_batchChange every pass in a batch made with create_wallet_pass_batch (e.g.No findings
Why it is in this group
- The name "update_wallet_pass_batch" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Change every pass in a batch made with create_wallet_pass_batch (e.g. a new time or venue); every iPhone that added one refreshes within seconds. Paid: $0.01 per pass in the batch, as one x402 payment (refused first with the exact amount; retry unchanged with x402_payment). Nothing is charged if the change doesn't build. Each field list given replaces that list in the design (resend unchanged fields too; strings may use {name} {ticket} {type} {email}). change_message (e.g. "Doors now open at %@") is shown on the lock screen for fields whose value changed. contact_email and x402_ready are required. Returns {batch_id, updated, notified_devices, charged, payment}.
Annotations the server declares
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Update Apple Wallet passes in bulk
Can't be undone 2Claude Code: ask
create_wallet_passCreate a signed Apple Wallet pass (.pkpass) and return a link to download it.1 finding
Why it is in this group
- The name "create_wallet_pass" says "create": a word for a change.
- The description says "can't be recovered".
Findings
- Info
The description is 13,547 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...let connector's sign/pay tool. Same as sending it in _meta["x402/payment"]."
Description, as the server wrote it Create a signed Apple Wallet pass (.pkpass) and return a link to download it. Builds one pass in one of the five Wallet styles -- boardingPass, eventTicket, coupon, storeCard or generic -- from the text fields, colors, barcode and optional PNG images given below, signs it with this service's Apple Pass Type ID certificate, and returns an https download_url valid for 1 hour. Opening the link on an iPhone shows "Add to Apple Wallet". Passes install on any iOS version; the iOS 26/27 layouts fall back to the classic style on older iPhones. Barcodes: QR, PDF417, Aztec and Code128 on every iOS version; Code39, Codabar, EAN13 and ITF on iOS 27+. The barcode encodes exactly barcode_message. Gate and till scanners read that data, so a copy of an existing boarding pass, ticket or loyalty card only scans if barcode_message is the original barcode's content (airline boarding passes are usually PDF417 or Aztec, holding an IATA BCBP string such as "M1DOE/JANE ..."). This tool does not issue tickets, check anyone in, or contact airlines or venues. The link must be opened in Safari on the iPhone: Wallet adds a pass from Safari, but not from a .pkpass file handed over by another app. Google Wallet on Android also imports these files. Not supported: NFC passes. With updatable=True the pass can be changed later with update_wallet_pass, and copies already in Wallet refresh themselves. Its contents are then stored on this server for updatable_hours (1 hour by default, at most 30 days), then deleted. Returns {download_url, expires_in_seconds, serial_number, pass_type_identifier}, plus edit_token and updatable_until when updatable=True. With x402_ready=False and 3 or fewer free passes left today, also free_passes_left_today and x402_setup (how to set up x402 payments): pass that on to the user. Pricing: a call is one create or one update. The first 10 successful calls each day per caller (IP address or contact_email) are free (while a shared pool of 500 free calls a day lasts); failed calls don't count (up to 20 failures a day per caller), and counts reset at 00:00 UTC. Every call after them costs $0.01 in USDC on Base, paid with x402: the refusal carries the payment requirements; have the user's wallet tool sign them and retry the same call with the result as x402_payment. A paid result includes the payment receipt. Payment is settled only after the pass is built, so a failed build is never charged. Args: style: one of "boardingPass", "eventTicket", "coupon", "generic", "storeCard". organization_name: shown as the pass issuer. description: accessibility description (required by Wallet, not usually shown). logo_text: text shown next to the logo image. transit_type: only for style="boardingPass" -- "Air", "Boat", "Bus", "Generic", or "Train" (default "Air"). barcode_message: raw text/data encoded into the barcode. Omit for no barcode. barcode_format: a format name or an ordered list of them; each becomes a barcode with the same message, and Wallet shows the first one the device supports. Nothing is added that you don't list. Formats: "QR" (default), "PDF417", "Aztec", "Code128" (all iOS versions), and iOS 27+ only: "Code39", "Codabar", "EAN13", "ITF" -- older iPhones skip these, so e.g. ["EAN13", "Code128"] shows EAN13 on iOS 27 and Code128 before it. EAN13 needs 12-13 digits, ITF an even number of digits, Code39 uppercase letters/digits. barcode_alt_text: human-readable text shown under the barcode (e.g. the card number). background_color / foreground_color / label_color: hex colors, e.g. "#1a1a19". relevant_date / expiration_date: ISO 8601 timestamps. locations: up to 10 places where the pass appears on the lock screen when the iPhone is nearby, each {"latitude": float, "longitude": float, "altitude": optional float, "relevantText": optional str shown on the lock screen, e.g. "Your gym card"}. Look up the coordinates of the actual branch, not just the brand. For boardingPass and eventTicket the pass is relevant near a location around relevant_date if one is set; the other styles use location alone. Wallet only shows a pass within its own default radius of a location, which is small for store cards and coupons. max_distance: meters; shrinks the default radius around every location (Wallet uses the smaller of the two, so it cannot enlarge it). Requires locations. voided: mark the pass voided/used (shows a "VOID" stamp). primary_fields / secondary_fields / auxiliary_fields / header_fields / back_fields: lists of {"key": optional str, "label": optional str, "value": str, "changeMessage": optional str} shown on the pass. changeMessage only matters on updatable passes: when an update changes that field's value, the iPhone shows it as a lock-screen notification, with %@ replaced by the new value (e.g. "You now have %@ points"); without %@ Wallet shows a generic message. Updates match fields by key, so give fields that will change an explicit key (auto keys are by position). serial_number: unique id for this pass; auto-generated if omitted. icon_color / icon_text: control the auto-generated icon (a colored square with initials) when icon_png_b64 is not supplied. logo_color: color of the auto-generated logo image, a wordmark of logo_text (or organization_name) drawn on a transparent background over background_color. Defaults to icon_color. Wallet also renders logo_text as text beside the logo image, so the generated wordmark repeats it -- set generate_logo=False to show only the text. icon_png… [7547 more characters not shown]
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create Apple Wallet pass
create_wallet_pass_batchCreate one Apple Wallet pass per attendee from a single design, e.g.1 finding
Why it is in this group
- The name "create_wallet_pass_batch" says "create": a word for a change.
- The description says "can't be recovered".
Findings
- Info
The description is 2,096 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...links_csv_url (all links as a CSV, also secret), updatable_until, payment}."
Description, as the server wrote it Create one Apple Wallet pass per attendee from a single design, e.g. tickets for a guest list. Paid, with no free tier: each new pass costs $0.01 in USDC on Base via x402, charged as one payment for the whole call ($0.01 x the number of new passes). The first call is refused with the exact amount; retry it unchanged with the signed payment in x402_payment. Nothing is charged unless every pass builds. A row whose ticket is already in the batch is not charged again and gets the same link. Each pass gets a permanent https link (not the 1-hour download link of create_wallet_pass) that always serves the latest version, and stays installable and updatable until event_end + 7 days. Send the links to attendees yourself (email, WhatsApp, a form); this service sends nothing. Args: rows: up to 1000 attendees per call (5000 per batch), each {"name": str, "ticket": str, "type": optional str (default "General admission"), "email": optional str}. ticket is the unique id within the batch (and the default barcode message). Parse a CSV into these rows yourself. design: for a new batch, create_wallet_pass's parameters (style, organization_name, description, colors, fields, images, ...; not serial_number/updatable/contact_email) whose strings may contain {name} {ticket} {type} {email}, filled in per attendee. Defaults: style "eventTicket", barcode_message "{ticket}". Leave out with batch_key. event_end: for a new batch, when the event ends (ISO 8601, within a year). Leave out with batch_key. batch_key: to add attendees to a batch made earlier, the batch_key it returned. contact_email, x402_ready, x402_payment: as for create_wallet_pass (all calls are paid here). Returns {batch_key (new batch only: it can't be recovered, give it to the user), batch_id, passes: [{name, ticket, type, email, link, new}], created, reused, issued_total, charged, links_csv_url (all links as a CSV, also secret), updatable_until, payment}.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
- title: Create Apple Wallet passes in bulk
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:50 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 2 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://walletmcppass.com/mcp: tools/list returned 4 tools to an anonymous client, including update_wallet_pass (destructive), update_wallet_pass_batch (destructive), create_wallet_pass (irreversible), create_wallet_pass_batch (irreversible)
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 2 to 4
Findings
Matches of fixed checks, with the text they matched.
The description is 13,547 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...let connector's sign/pay tool. Same as sending it in _meta["x402/payment"]."
The description is 2,096 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...links_csv_url (all links as a CSV, also secret), updatable_until, payment}."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 4.View diff
- Tools that change things, listed without credentials: 2 to 4
Tools2 added.+2 addedView diff
- Added:create_wallet_pass_batchCan't be undone
- Added:update_wallet_pass_batchDeletes or cancels
Tools2 changed.~2 changedView diff
- Changed:create_wallet_passCan't be undonedescriptioninputSchema
- Changed:update_wallet_passDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http wallet https://walletmcppass.com/mcpclaude mcp add --transport http wallet https://walletmcppass.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__wallet__create_wallet_pass",
"mcp__wallet__create_wallet_pass_batch"
],
"deny": [
"mcp__wallet__update_wallet_pass",
"mcp__wallet__update_wallet_pass_batch"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wallet. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.walletmcppass/wallet-mcp/verify?hash=fc177e6eda5b1a4abe30b02a54c88c0e89da485b380a96761e67b32cc4b7747c" | jq -e '.changed == false'Pinned hash fc177e6eda5b, from Nov 13, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.walletmcppass/wallet-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.walletmcppass/wallet-mcp)Source: MCP Registry · repository. Synced Nov 13, 2026, 17:17 UTC.
walletmcppass: Apple Wallet passes MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the walletmcppass: Apple Wallet passes MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the walletmcppass: Apple Wallet passes MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: update_wallet_pass and update_wallet_pass_batch.
Can the walletmcppass: Apple Wallet passes MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: create_wallet_pass and create_wallet_pass_batch.
What tools does the walletmcppass: Apple Wallet passes MCP server have?
- 4 tools: 2 destructive, 2 irreversible. update_wallet_pass, update_wallet_pass_batch, create_wallet_pass and create_wallet_pass_batch.
Does the walletmcppass: Apple Wallet passes MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the walletmcppass: Apple Wallet passes MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the walletmcppass: Apple Wallet passes MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.