Kind: Server-side
The MCP Proxy tool connects Infersec to any external Model Context Protocol server. When the model calls the tool, the Infersec API forwards the request to your MCP server's URL and returns its response to the model. No Conduit agent is required - the tool is resolved and executed entirely server-side.
Use this when you already run an MCP server (your own or a third-party one) and want to expose its tools to models hosted on Infersec.
How it works
- The Infersec API fetches the tool list from your MCP server's
url. - Those tools are advertised to the model alongside any others on the endpoint.
- When the model invokes one, Infersec proxies the call to the same
urland streams the result back.
Configuration
| Field | Required | Description |
|---|---|---|
url |
yes | The MCP server endpoint URL |
headers |
no | Static headers (e.g. auth tokens) sent with every proxied request |
The URL must be reachable from the Infersec API. For authenticated MCP servers, put the credential in headers rather than embedding it in the URL where possible.
Connecting
Server-side tools need no Conduit connection. Create the tool in the console, add it to a tool service, and attach that tool service to an inference endpoint.