Pincer

Name: Pincer
Author: VouchlyAI

作者：VouchlyAI版本 0.1.5i★ –i在你的电脑上运行

注册名称io.github.VouchlyAI/pincer

安装

概览

作者提供的说明（英文原文）

Secure grip for your agent's secrets - security-hardened MCP gateway with proxy token architecture

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 网络安全
你需要填写：PINCER_PROXY_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PINCER_PROXY_TOKEN, OPENWEBUI_URL, OPENAI_COMPATIBLE_URL, AUDIT_LOG_PATH

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PINCER_PROXY_TOKEN 机密必填 env
Proxy token for agent authentication (generated via 'pincer agent add')
OPENWEBUI_URL env
Optional: Base URL for OpenWebUI instance
OPENAI_COMPATIBLE_URL env
Optional: Base URL for OpenAI-compatible instance
AUDIT_LOG_PATH env
Optional: Custom path for audit logs (default: ~/.pincer/audit.jsonl)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 VouchlyAI 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网络安全”中的其他服务器比较i

星标数多于此分类中其他 995 个服务器的 0%
发布到注册中心的时间比此分类中其他 995 个服务器的 3% 更新
基础检查结果等于或优于此分类中其他 995 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Pincer 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：PINCER_PROXY_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.5）于9个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：QNSQY, EchelonGraph CVE & Exposure, WatchGuard MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

QNSQY

作者：quantumsequrity

Linux only, local: post-quantum CBOM scan, encrypt to public keys, verify. Takes no secrets

在你的电脑上运行今天更新

安装

EchelonGraph CVE & Exposure

作者：echelongraph

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

电脑或云端今天更新

安装

WatchGuard MCP

作者：servosity

WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Pincer MCP 🦀

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.

🔒 The Problem

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:

Database passwords
Third-party API keys

✨ The Solution: Proxy Token Architecture

Pincer implements a "blindfold" security model:

Agent knows: Only a unique proxy token (pxr_abc123...)
Pincer knows: Mapping of proxy tokens → real API keys (encrypted in OS keychain)
Agent never sees: The actual credentials

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.

🔑 GPG Key Management

# Generate a new GPG keypair (private key stored in vault)

pincer key generate --name "Release Signing" --email dev@example.com

Import an existing PGP private key

pincer key import ./my-key.asc --passphrase "my-passphrase"

List all stored GPG keys

pincer key list

Export public key (safe to share)

pincer key export

Authorize an agent for signing

pincer agent authorize mybot gpg_sign_data --key

*(More callers coming soon!)*

🚀 Quick Start

Prerequisites

Node.js 18+
macOS, Windows, or Linux with native keychain support

Installation

Option 1: Global Installation (Recommended)

npm install -g pincer-mcp

Now 'pincer' command is available system-wide

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

Setup Vault

# 1. Initialize vault (creates master key in OS keychain)

pincer init

2. Store your real API keys (encrypted)

pincer set gemini_api_key "AIzaSyDpxPq..." pincer set openai_api_key "sk-proj-..."

3. Register an agent and generate proxy token

pincer agent add openclaw

Output: 🎫 Proxy Token: pxr_V1StGXR8_Z5jdHi6B-myT

4. Authorize the agent for specific tools

pincer agent authorize openclaw gemini_generate

Multi-Key Support

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

View all stored keys

pincer list

Assign specific keys to each agent

pincer agent add clawdbot pincer agent authorize clawdbot gemini_generate --key key1

pincer agent add mybot pincer agent authorize mybot gemini_generate --key key2

View agent permissions

pincer agent list

Result: clawdbot uses key1, mybot uses key2 - perfect for rate limiting or cost tracking!

Run the Server

npm run dev

Configure Your Agent

Give your agent the proxy token (not the real API key):

export PINCER_PROXY_TOKEN="pxr_V1StGXR8_Z5jdHi6B-myT"

Tool-to-Secret Name Mappings

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.

Make a Tool Call

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.

🏗️ Architecture

Two-Tiered Vault System

Tier 1: Master Key (OS Keychain)

Stored in macOS Keychain, Windows Credential Manager, or GNOME Keyring
Never touches the filesystem
Accessed only for encryption/decryption

Tier 2: Encrypted Store (SQLite)

Database at ~/.pincer/vault.db
Three tables:
secrets: Real API keys (AES-256-GCM encrypted)
proxy_tokens: Proxy token → Agent ID mappings
agent_mappings: Agent ID → Tool authorization

Authentication Flow

Request (_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

🔐 Security & Compliance

Pincer is built for enterprise-grade security:

Hardware-Backed Cryptography: Master encryption keys never leave the OS-native keychain.
Proxy Token Isolation: Agents only handle ephemeral pxr_ tokens; they never touch real credentials.
JIT Decryption: Secrets are decrypted only for the duration of the API call.
Zero-Footprint Memory: Sensitive data is scrubbed (zeroed out) from memory immediately after use.
Fine-Grained Authorization: Strict per-agent, per-tool access control policies.
Tamper-Evident Audit Log: Append-only tool call history with SHA-256 chain-hashing.
Hardened Execution: Schema validation on all inputs and protected environment execution.
Stdio Compatible: Fully compatible with the standard Model Context Protocol transport.

🔍 Audit Logs

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.

🧪 Development

# Install dependencies

npm install

Run tests

npm test

Run with watch mode

npm run dev

Build for production

npm run build

📚 Documentation

[Setup Guide](docs/SETUP.md) - Getting started with Pincer-MCP
[IDE Integration](docs/IDE_INTEGRATION.md) - Use Pincer with VSCode, Claude Desktop, Cursor, and more
[OpenClaw Integration](docs/OPENCLAW_INTEGRATION.md) - Integrate Pincer with OpenClaw agents
[Testing Guide](docs/TESTING.md) - Comprehensive test suite documentation
[Capabilities Reference](docs/CAPABILITIES.md) - Full API and feature documentation
[Security Policy](SECURITY.md) - Vulnerability reporting and security best practices
[CHANGELOG](CHANGELOG.md) - Version history and release notes

🤝 Contributing

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

📄 License

BSL 1.1 (Business Source License) — See LICENSE for details. Converts to Apache 2.0 on 2028-04-01.

Model Context Protocol - The standard for AI tool integration.
keytar - Secure cross-platform keychain access.
better-sqlite3 - High-performance local persistence.

Built with ❤️ for a more secure AI future.