WatchGuard MCP
WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer
Description from the maker (original English)
Secure grip for your agent's secrets - security-hardened MCP gateway with proxy token architecture
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PINCER_PROXY_TOKEN, OPENWEBUI_URL, OPENAI_COMPATIBLE_URL, AUDIT_LOG_PATHValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pincer": {
"command": "npx",
"args": [
"-y",
"pincer-mcp"
],
"env": {
"PINCER_PROXY_TOKEN": "your-value",
"OPENWEBUI_URL": "your-value",
"OPENAI_COMPATIBLE_URL": "your-value",
"AUDIT_LOG_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pincer --env PINCER_PROXY_TOKEN=your-value --env OPENWEBUI_URL=your-value --env OPENAI_COMPATIBLE_URL=your-value --env AUDIT_LOG_PATH=your-value -- npx -y pincer-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pincer": {
"command": "npx",
"args": [
"-y",
"pincer-mcp"
],
"env": {
"PINCER_PROXY_TOKEN": "your-value",
"OPENWEBUI_URL": "your-value",
"OPENAI_COMPATIBLE_URL": "your-value",
"AUDIT_LOG_PATH": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pincer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pincer-mcp"
],
"env": {
"PINCER_PROXY_TOKEN": "your-value",
"OPENWEBUI_URL": "your-value",
"OPENAI_COMPATIBLE_URL": "your-value",
"AUDIT_LOG_PATH": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
OPENWEBUI_URL envOPENAI_COMPATIBLE_URL envAUDIT_LOG_PATH envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account VouchlyAI, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PINCER_PROXY_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.5) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: WatchGuard MCP, ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Pincer-MCP is a security-hardened Model Context Protocol (MCP) gateway that eliminates the "Lethal Trifecta" vulnerability in agentic AI systems. By acting as a stateless intermediary, Pincer ensures agents never see your real API keys.
Current AI agents store long-lived API keys in plain-text .env files or local databases. If compromised via prompt injection or host intrusion, attackers gain direct access to your:
Pincer implements a "blindfold" security model:
pxr_abc123...)sequenceDiagram
participant Agent participant Pincer participant Vault (OS Keychain) participant External API
Agent->>Pincer: tools/call + proxy_token: pxr_abc123 Pincer->>Vault: Decrypt real API key Vault-->>Pincer: gemini_api_key: AIzaSy... Pincer->>External API: API call with real key External API-->>Pincer: Response Pincer->>Pincer: Scrub key from memory Pincer-->>Agent: Response (no credentials)
## 📦 Available Tools
gemini_generate: Secure Google Gemini API calls.openai_chat: Chat completions with OpenAI GPT models (gpt-4o, gpt-4-turbo, gpt-3.5-turbo, etc.).openai_list_models: List all available OpenAI models.openai_compatible_chat: Chat completions with any OpenAI-compatible API (Azure OpenAI, Ollama, vLLM, etc.).openai_compatible_list_models: List models from custom OpenAI-compatible endpoints.claude_chat: Chat completions with Anthropic Claude models (Claude 3.5 Sonnet, Opus, Haiku).openrouter_chat: Unified API access to 100+ models from multiple providers (OpenAI, Anthropic, Google, Meta, etc.).openrouter_list_models: List all available models across OpenRouter providers.openwebui_chat: OpenAI-compatible interface for self-hosted LLMs.openwebui_list_models: Discover available models on an OpenWebUI instance.gpg_sign_data: Sign data or files using a GPG/PGP private key stored in Pincer's vault. *(Keyless Execution — agent never sees the key)*gpg_decrypt: Decrypt PGP-encrypted data using a vault-stored private key.# Generate a new GPG keypair (private key stored in vault)
pincer key generate --name "Release Signing" --email dev@example.com
pincer key import ./my-key.asc --passphrase "my-passphrase"
pincer key list
pincer key export
pincer agent authorize mybot gpg_sign_data --key
*(More callers coming soon!)*
Option 1: Global Installation (Recommended)
npm install -g pincer-mcp
Option 2: Local Development
git clone https://github.com/VouchlyAI/Pincer-MCP.git
cd Pincer-MCP npm install npm run build npm link # Makes 'pincer' command available locally
# 1. Initialize vault (creates master key in OS keychain)
pincer init
pincer set gemini_api_key "AIzaSyDpxPq..." pincer set openai_api_key "sk-proj-..."
pincer agent add openclaw
pincer agent authorize openclaw gemini_generate
Store multiple keys for the same tool and assign them to different agents:
# Store two different Gemini API keys
pincer set gemini_api_key "AIzaSy_KEY_FOR_CLAWDBOT..." --label key1 pincer set gemini_api_key "AIzaSy_KEY_FOR_MYBOT..." --label key2
pincer list
pincer agent add clawdbot pincer agent authorize clawdbot gemini_generate --key key1
pincer agent add mybot pincer agent authorize mybot gemini_generate --key key2
pincer agent list
Result: clawdbot uses key1, mybot uses key2 - perfect for rate limiting or cost tracking!
npm run dev
Give your agent the proxy token (not the real API key):
export PINCER_PROXY_TOKEN="pxr_V1StGXR8_Z5jdHi6B-myT"
When storing secrets, you must use the correct secret name for each tool. See the [Tool Mappings Guide](docs/TOOL_MAPPINGS.md) for a complete reference.
When you run pincer agent authorize myagent gemini_generate, Pincer will inject the gemini_api_key secret when that tool is called.
Your agent sends requests with the proxy token in the body:
{
"jsonrpc": "2.0", "method": "tools/call", "params": { "name": "gemini_generate", "arguments": { "prompt": "Hello world", "model": "gemini-2.0-flash" }, "_meta": { "pincer_token": "pxr_V1StGXR8_Z5jdHi6B-myT" } } }
Pincer maps the proxy token to the real API key and executes the call securely.
Tier 1: Master Key (OS Keychain)
Tier 2: Encrypted Store (SQLite)
~/.pincer/vault.dbsecrets: Real API keys (AES-256-GCM encrypted)proxy_tokens: Proxy token → Agent ID mappingsagent_mappings: Agent ID → Tool authorizationRequest (_meta.pincer_token: pxr_xxx)
↓ Gatekeeper: Extract proxy token from body ↓ Vault: Resolve pxr_xxx → agent_id → tool_name → real_api_key ↓ Injector: JIT decrypt & inject real key ↓ Caller: Execute external API call ↓ Scrubber: Overwrite key in memory with zeros ↓ Audit: Log to tamper-evident chain
Pincer is built for enterprise-grade security:
pxr_ tokens; they never touch real credentials.Every tool call is logged to ~/.pincer/audit.jsonl with both UTC and Local timestamps, plus character counts and estimated token usage:
{
"agentId": "openclaw", "tool": "gemini_generate", "duration": 234, "status": "success", "input_chars": 156, "output_chars": 423, "estimated_input_tokens": 39, "estimated_output_tokens": 106, "timestamp_utc": "2026-02-05T08:32:00.000Z", "timestamp_local": "2/5/2026, 2:02:45 PM", "chainHash": "a1b2c3d4e5f6g7h8", "prevHash": "0000000000000000" }
Token Estimation: Pincer automatically estimates token usage using a 4:1 character-to-token ratio (~4 characters per token average). This provides consistent cost tracking across all AI providers without relying on provider-specific APIs.
Chain hashes provide tamper detection - any modification breaks the SHA-256 chain.
# Install dependencies
npm install
npm test
npm run dev
npm run build
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
BSL 1.1 (Business Source License) — See LICENSE for details. Converts to Apache 2.0 on 2028-04-01.
Built with ❤️ for a more secure AI future.