@trusty-squire/mcp 1.1.5 → 1.1.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -45,6 +45,13 @@ new card is encrypted in your browser with a passkey-derived key and bound to
45
45
  that purchase before approval; if you add it but do not approve in time, it
46
46
  remains saved for a faster retry.
47
47
 
48
+ Recognized Visa, Mastercard, Amex, Discover, Diners Club, and JCB cards show
49
+ their network mark in the Vault while keeping the full bank/network label. Open
50
+ a card row to see its masked number; `reveal` runs the passkey ceremony in your
51
+ browser before showing the number, name, expiry, and billing address. The CVV is
52
+ never shown, even after reveal. The Activity page also records card additions
53
+ and removals, payments, and app-grant changes without storing a PAN or CVV.
54
+
48
55
  `operate_pay` reads the checkout total, sends you a short-lived approval link,
49
56
  and submits only after you approve the exact purchase. The approval page shows
50
57
  the venue, item, amount, requesting agent, and reason; one passkey prompt both
@@ -58,6 +65,11 @@ timeout. `three_ds_wait_seconds` accepts whole seconds from 0 to 600; set it to
58
65
  `0` on `operate_pay` to skip the notification and waiting and receive the
59
66
  handoff immediately.
60
67
 
68
+ Connect Telegram under Vault Settings to receive secret-free alerts for
69
+ credential, card, payment, and app-grant lifecycle changes. Routine credential
70
+ retrieval and proxy access stay in Activity instead of sending a push for every
71
+ request.
72
+
61
73
  ## Install
62
74
 
63
75
  ```bash
@@ -732,7 +732,7 @@ export async function launchSelfManagedLoginContext(params) {
732
732
  // `navigator.webdriver` — all separately ruled out). The connect claim doesn't
733
733
  // need to drive the browser: the USER signs in over noVNC, completion is read
734
734
  // from the API (`installPoll`), and provider seeding is read from the profile's
735
- // on-disk cookie store (`profileHasProviderCookies`). So we spawn Chrome and
735
+ // SQLite cookie store (`profileHasProviderCookies`). So we spawn Chrome and
736
736
  // only ever kill it — never attach.
737
737
  //
738
738
  // Persistent profile is preserved (--user-data-dir=profileDir) so the Google/