Changelog
Notable changes to the gateway, console, and developer portal. ToolHost ships frequently — this is a curated summary, not every commit.
Tighter credential and scope handling for OAuth-connected agents
Credentials issued to a specific tool are now bound to the tool that requested them, and step-up authorization (asking for broader access mid-session) accumulates scopes correctly instead of overwriting them.
Split developer-portal API keys into MCP and admin-scoped keys
Signing up through the developer portal now issues two distinct keys — one scoped to calling MCP tools through the gateway, one scoped to admin operations — so a leaked MCP key can't be used to change gateway configuration.
Public status page
A minimal status page at status.toolhost.online now reports gateway and API availability.
Principal → view preview in the console
The operator console's Views page now shows exactly which tools a given principal (agent, client, or API key) will see before you save a policy change.
Devportal accepts Neon-authenticated sessions on admin routes
Signing in through the developer portal now works as a first-class credential for admin API routes, alongside gateway API keys and bearer tokens.
Per-tool credential audience and scope claims on gw_ API keys
Gateway-issued API keys now carry audience and scope claims, tightening what a given key is valid for.
Separate SSRF trust levels for static vs. self-serve backends
Backends added through self-serve onboarding are now held to a stricter outbound-request allowlist than backends configured directly by the operator.
Redacted capture mode for debugging
Operators can now enable a redacted capture mode that records tool-call shapes for debugging without storing raw argument or response content by default.
Self-serve MCP server onboarding in the console
Connect a new MCP backend from the console without editing a config file — including OAuth-based backends via the devportal connect flow.