Saas Ai Webflow Website Datalog Template

Hermes

View IntegrationContact Support
Give supported Hermes Agent MCP connections and HTTP tools two stable source IPs for protected destinations. Use your existing QuotaGuard subscription and configure the process or tool runtime making the request.

Place QuotaGuard on the client that makes the IP-restricted request, whether that is Hermes or an MCP server's onward API client.

  • Remote MCP: Configure the Hermes process's documented proxy settings for supported HTTP and SSE connections. This changes the source IP seen by the MCP endpoint, not the source IP of the remote server's onward API calls.
  • Local MCP: Keep the local connection on stdin/stdout. Explicitly pass the required proxy values through the server entry's env mapping and configure its onward HTTP client; Hermes filters child environments, so parent-process variables are not automatically passed through.
  • Other runtimes: Containers, SSH backends and browser providers need their own supported routing controls.
  • Both addresses: Keep both dashboard IPs allowlisted and check the actual protected request path.
  • Separate authentication: Keep the destination's credentials and scopes. Shield adds TLS on the proxy hop for compatible clients.

Read the complete Hermes Agent setup guide for configuration and troubleshooting.

Comparing platforms? See the complete guide to static IPs on any PaaS platform.

Reliability Engineered for the Modern Cloud

For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.

Get the fixed identity and security your application needs today.

Start Free TrialTalk to an Engineer