Release and changelog

Match your integration to the server it connects to.

This server

Read at request time from this server’s configuration and shipped catalog. A local or preview URL describes that environment. For production, inspect ohvii.com’s release record; if unavailable, production identity has not been established by this page.

Source revision
Unavailable: this runtime did not provide a valid deployment revision.
Configuration
Buyer UI v2
Catalog fingerprint
00e5441a095c7e20d0c2fe921d6184758526f45a879c3344bf2db03040d3466e
Source surface
136 tools · 3 resources
Source protocols
2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07

The fingerprint covers both source configurations. Use the configuration field to select one, then compare authenticated tools/list, resources and server instructions before invoking tools. Live output schemas may be compacted; the catalog includes full validation contracts.

This server’s release JSONFull catalogPlatform setup

October 5, 2026: developer documentation

Added the shared developer guide, searchable tool reference, generated schemas, scope descriptions and proposed Muse classifications. Expanded it with readable field tables, synthetic workflow examples, reviewer scenarios and runtime release information.

Corrected token-expiry guidance: a valid refresh token can renew an expired access token. A revoked grant requires reconnection. These documentation changes do not alter tool permissions or buyer approval requirements.

Migration: no client changes required for the documentation additions. Follow the active tool contracts and refresh your host’s cached catalog after a server update. This entry is a documentation record, not a deployment or provider-approval receipt.

Handling changes

  • Record this release fingerprint and configuration with your integration test results. A changed fingerprint means the source contract changed; it is not a semantic version or a promise of backward compatibility.
  • New required inputs, removed fields or tools, changed field types, scopes, side effects or approval behavior need a migration entry. Each entry should identify affected tools, the replacement behavior, before/after usage and the deployment revision.
  • For planned removals, publish the replacement and intended removal date before removal. A fixed support window is not currently promised. Security or correctness fixes may require immediate action; record their impact and recovery path.
  • Discover capabilities on connection. Do not treat new tool availability as expanded consent, and do not reuse a prepared action after its terms or revision change.

For migration help, contact info@ohvii.com with the host, configuration and fingerprint. Keep credentials and private transaction content out of the report.