§ CHANGELOG

What shipped

Every release of Kaiva Bridge, newest first. Kaiva Bridge is in active development, expect frequent additions.

LATEST 5 Sep 2026·15 RELEASES SINCE 8 AUG 2026
5 Sep 2026Tool integrity

A rewritten tool description waits for you instead of reaching your agents

An MCP client reads a server's tool definitions once, when someone approves the connection, and generally never shows them again. What the gateway serves is now a pinned revision rather than whatever the last introspection wrote, so a changed description or input schema on a tool that is already exposed waits for you to publish it. Connected agents keep receiving the definitions they had. New and removed tools are unaffected and still publish with no interaction. Every live server also publishes the fingerprint of what it serves, and the tool definitions behind it, so anyone can check without an account.

newChanged descriptions and schemas on exposed tools wait for a decision, with the tools namednewPublish or reject from the server page; rejecting restores what is being servednewAuto-publish per server, for workspaces that introspect from CInewPublic /fingerprint, /contract and /revisions on every live server, no key needednewEmail and a webhook when a change is waitingnewManagement API: list revisions, promote, reject and set auto-publishnewCLI 0.1.5: introspect, revisions, promote, reject and auto-publish; introspect exits 3 when a change is held
31 Aug 2026Console

Per-server views, live tool calls that link through, and errors that explain themselves

Servers opens as a list you scan and a server you work on, each with its own audit log. Live traffic entries link straight to the exact call in Tool calls, an expanded row shows which entry it belongs to, and a failed call reports the reason rather than only that it failed.

newPer-server view, with the audit log scoped to that servernewLive traffic entries open the exact matching call in Tool callsnewFailed calls report what went wrongchangeExpanded audit rows show which entry they belong tochangeUI pass across the console
29–30 Aug 2026OAuth 2.1

One policy model, whatever the client

Per-tool policies and require-approval apply to every caller, whether it authenticates with an API key or over OAuth 2.1. A policy governs a tool by the tool (not by how the client connected) and every call lands in the audit log the same way.

newPer-tool policies across API-key and OAuth 2.1 clientsnewRequire-approval across API-key and OAuth 2.1 clientsnewOAuth 2.1 calls in the audit logchangePolicy subjects can target OAuth clients directly
28 Aug 2026Free tier 4×

200,000 tool calls a month on Free, and what your tools cost the agent

The free tier is four times what it was: 200,000 tool calls a month, still with no card and no expiry. Alongside it, the console now shows what each tool definition costs your agent in context, and which tools it has never called, so you can switch them off.

changeFree tier raised to 200,000 tool calls / mo, up from 50,000newContext cost per tool definition, shown in the consolenewUnused tools flagged so you can unexpose them
27 Aug 2026Bundles

One endpoint for many servers

A bundle collapses several servers into a single MCP endpoint. tools/list merges across its members and tools/call routes to the server that owns the tool, so a client config has one entry and one key instead of one per server, and adding a server later needs no change to the client.

newBundles: one endpoint and one key across several serversnewMerged tool list, with calls routed to the owning servernewKeys are scoped to a bundle, re-checked on every call, so a server added later is not reachable by an older keychangeColliding tool names are prefixed on both sides, so a name never changes meaning as membership changeschangeOverview shows trends and sparklines, not four bare numbers
27 Aug 2026Teams + SSO

Teams on every plan, and single sign-on expanded

Free workspaces now include three members instead of one, so a small team can share a Bridge workspace without paying for it. Single sign-on now covers SAML 2.0 alongside OIDC, with email-domain verification and provider groups mapped to Bridge roles.

newFree plan now includes 3 team members, up from 1newTeam invitations, invite by email with a role, expiring after 7 days and cancellable at any timenewSingle sign-on now covers SAML 2.0 alongside OIDC, Okta, Entra ID, Google Workspace or any compliant providernewVerify your email domain and members sign in with their work emailnewProvider groups can now map directly to Bridge roles
24 Aug 2026CLI 0.1.4

Upstream compatibility

Some APIs refuse requests that arrive without a User-Agent. Bridge now identifies itself on every upstream call, which fixed introspection and tool execution against those hosts.

fixSend a User-Agent on all upstream requests, GitHub and others returned 403 without onenewListed on Glama
22–23 Aug 2026MCP 2026-07-28

Dual-era MCP, and Bridge as a connector

Full support for the 2026-07-28 MCP revision alongside the legacy handshake, so new and old clients both work against the same endpoint with no flag to set.

newBridge itself is an MCP connector, create and inspect servers from your agentnewTool annotations derived from the HTTP verb, so clients know what is read-onlynewoutputSchema generated from documented OpenAPI responseschangeDual-era protocol negotiation; legacy clients untouchedfixClosed a dynamic-client-registration bypass
20–21 Aug 2026CLI 0.1.0–0.1.2

Management API and a CLI on npm

Everything the console does is now an API, and the CLI is public on npm as @kaiva/bridge, MIT, source on GitHub.

newManagement API with scoped management keysnew@kaiva/bridge published to npm: tools command, invoke a tool by namenewemail-check source: MX, SPF and DMARC lookups with a verdictchangeRe-introspection is non-destructive and keeps OpenAPI descriptions and constraints
19–20 Aug 2026Registry

Remote MCP sources, playground, and a registry listing

A third source type: point Bridge at an existing remote MCP server and govern it the same way. Listed in the official MCP registry as ai.kaiv/bridge.

newMCP proxy source, bring a remote MCP server under BridgenewIn-console playground, shareable server links, and templatesnew/try sandbox and a live runner on the landing pagenewListed in the official MCP registry as ai.kaiv/bridge
17–19 Aug 2026OAuth 2.1

OAuth 2.1, end to end

Full authorization-code flow on Ory Hydra with dynamic client registration, so an MCP client can connect without anyone pasting a key.

newOAuth 2.1 authorization-code flow with PKCEnewDynamic client registration, rate limitednewRFC 9728 / RFC 8414 discovery at /.well-known, plus security.txtnewConsent screen with human-readable scope labelsnewConnected apps: view and revoke authorized clients yourselffixA token issued for one server can no longer be replayed against another
15–16 Aug 2026Demos

Try it without an account

An isolated public demo host, so anyone can call a real MCP tool before signing up for anything.

newKeyless public demos on an isolated hostnewEdge-only ingress, the origin refuses direct trafficnewAbuse auto-suspend, on by defaultnewIn-console bug reports and feedbacknewSign in with GooglefixOpenAPI connector: servers[] base URLs and $ref parameters
12–14 Aug 2026Plans

Plans, status, and isolation at the database layer

Row-Level Security so one workspace cannot see another's servers, keys or logs, enforced by Postgres, not by application code.

newRow-Level Security and org isolationnewFree / Pro / Enterprise plans with StripenewPublic status page with 90-day uptime, independently monitorednewPer-client connect tabs and current MCP protocol negotiationchangeConsole and site work properly on a phone
9–11 Aug 2026Hardening

Egress guard, RBAC, and a kill-switch

Nothing reaches a private network, nothing runs without a scoped key, and there is one switch that stops everything.

newSSRF egress guard, private ranges and cloud metadata addresses blockednewCSRF protection, RBAC, and a global kill-switchnewTOTP two-factor on adminnewDPA, plus Bridge sections in Terms and Privacy
8 Aug 2026v1.0

Kaiva Bridge, first build

Turn an OpenAPI spec or a Postgres database into a live MCP server. One endpoint, one key, upstream credentials kept server side.

newSources: OpenAPI documents and Postgres databasesnewLive MCP gateway with scoped API keysnewPolicies (allow, hold for review, or deny) with dry-run against recent trafficnewHuman-in-the-loop approvals with webhook deliverynewAudit log with tamper-evident verification and exportnewResponse DLP, per-key rate limits, and usage enforcementnewSCIM provisioning and SIEM streaming for teams