About ToolHost

AI agents increasingly need to call tools — search engines, internal APIs, documentation, databases — through the Model Context Protocol (MCP). As the number of MCP servers an agent needs grows, so does the surface area an operator has to secure: separate credentials per server, no shared rate limiting, no consistent audit trail, and no single place to see what an agent actually did.

ToolHost is an MCP gateway that sits between configured agents and backend MCP servers. It presents one governed endpoint and applies controls at that boundary: client identity, per-principal rate limits, schema-change approval (TOFU pinning), SSRF-safe outbound requests, and operational evidence for governed decisions and tool activity.

ToolHost is vendor-neutral by design. It does not require a particular AI provider: configured MCP-speaking clients connect to configured MCP backends through the gateway. Compatibility belongs in the technical documentation and should be verified for each integration. The gateway is infrastructure, not a black box that intermediates your data.

We're early. The product is under active development, and this site, the docs, and the gateway itself will keep changing quickly. If something looks incomplete, it probably is — see the changelog for what's shipped recently.