Passbolt MCP 0.4.0

• Safe readiness diagnostics: request-local, closed-vocabulary stage/reason logs without exception text or secret
  material; metadata key trust, metadata decryption, secret fetch and secret decryption are reported separately without
  relaxing any trust predicate. The three-boolean passbolt_status contract is unchanged.
• Passbolt 5.12 PIN code resources (v5-pin-code) are listed by name and description instead of failing the whole
  search. The PIN is never returned, and passbolt_use_secret refuses to deliver it.
• Type-preserving passbolt_update_resource: the type comes from resource_type_id and is never converted.
  v5-pin-code entries accept only name and description and the PIN secret is not read, re-encrypted or sent;
  other or unknown types (TOTP, custom fields, notes, v4) are refused before any write.
• v5-default updates keep every uri, the icon and custom fields; uri replaces only the primary uri, and a password
  rotation keeps the secret's description and custom fields inside server custody. Data outside the v5 schema is
  refused before any encryption or write instead of being dropped.
• A new uri on update follows the same domain policy as create and is checked before any approval, secret read,
  decryption or write; new uris are limited to 1024 characters. Read mode accepts up to 32 uris per v5 resource.
• Search and select results carry resource_type (Passbolt slug or unknown).
• MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) on every tool;
  passbolt_select is readOnlyHint: false because it authorises a later passbolt_use_secret.
• Suggest-only update checker passbolt_check_update: anonymous GitHub API, 3 s timeout, 24 h cache, plain vX.Y.Z
  tags only, 30-minute back-off after a failure, never auto-updates or touches the vault. A cached hint appears in
  server instructions and passbolt_status; opt out with PASSBOLT_DISABLE_UPDATE_CHECK=1.
• Tests: passwords, PINs, secure notes and encrypted payloads never appear in search, select or use results;
  concurrent/cancelled probes, malformed key envelopes, real-GPG diagnostic refusal and approved encrypted password
  updates with disposable keys.
• Docs: embedded composition, registered authentication handlers, and updating a vault record versus rotating a
  website password.

English setup · Описание по-русски

Download the wheel or source archive below and verify SHA256SUMS. The installed setup
command generates local JSON/TOML client configuration; a source checkout is optional.
Your own provider credentials and API permissions remain required.

Verified on Python 3.12, 3.13 and 3.14 on Linux and Windows: existing contracts,
synthetic functional tests, clean wheel installation and real MCP stdio checks.
Live provider accounts and production deployment were outside this release verification.
GitHub verification · Source commit b93031a6a22ad76e87345b55891b614b1cedb4b3.

ZAI.ONE is a digital agency for websites, SEO, advertising and analytics.
ZAI.ONE — интернет-агентство: сайты, SEO, реклама и аналитика.
Contact / Написать в Telegram about setup and integration.

LicenseRef-ZAI-ONE permits installation and internal use on your own or authorized
accounts; it is not an open-source license. Third-party rights remain unchanged.
Stars are welcome. Request changes through Issues.