Secure LLM Proxy
About
OpenAI-compatible proxy with PII scrubbing, audit logging, and model routing. Drop-in replacement — set OPENAI_BASE_URL to point to this server. Supports GPT-4o, Claude, Gemini, and Llama via single endpoint.
Details
- Author
- wootock
- Downloads
- 371
- Categories
- AI
Jump to
- PII scrubbing removes emails, phone numbers, SSNs, and credit card numbers.
- Audit logging records every request with a hash of the original content.
- OpenAI-compatible endpoint — just change OPENAI_BASE_URL.
- Model routing supports GPT-4o, Claude, Gemini, and Llama via a single endpoint.
- Rate limit pooling spreads load across multiple upstream keys.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Secure LLM ProxyCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Set OPENAI_BASE_URL to https://nexus.exchange-secure.com/v1 and provide your API key. For MCP integration, configure the server with that URL and a Bearer token in your client’s settings. Use the chat_completion tool to send messages through the proxy.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"secure llm proxy": {
"secure-llm-proxy": {
"url": "https://nexus.exchange-secure.com/mcp",
"headers": {
"Authorization": "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"
}
}
}
}
}McpServers
{
"secure-llm-proxy": {
"url": "https://nexus.exchange-secure.com/mcp",
"headers": {
"Authorization": "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"
}
}
}Secure LLM Proxy — MCP Server
An OpenAI-compatible proxy with enhanced privacy controls, PII scrubbing, and audit logging.
Features
- PII scrubbing — strips emails, phone numbers, SSNs, and credit card numbers before forwarding
- Audit logging — every request logged with hash of original content
- OpenAI-compatible — drop-in replacement, just change OPENAI_BASE_URL
- Model routing — supports GPT-4o, Claude, Gemini, and Llama via single endpoint
- Rate limit pooling — spreads load across multiple upstream keys
Quick Start
export OPENAI_BASE_URL=https://nexus.exchange-secure.com/v1
export OPENAI_API_KEY=your-key # forwarded after PII scrub
Or with the MCP tool:
{
"mcpServers": {
"secure-llm-proxy": {
"url": "https://nexus.exchange-secure.com/mcp",
"headers": {
"Authorization": "Bearer your-key"
}
}
}
}
Available Tools
chat_completion
Generate a chat completion via the privacy-preserving proxy.
Input:
{
"messages": [{"role": "user", "content": "Hello"}],
"model": "gpt-4o"
}
Response includes audit ID, scrub report, and completion.
Privacy
Keys are never stored. Requests are hashed for audit purposes only. PII is removed before any data leaves your network perimeter.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
