MCP.Market

PrivacyFence MCP server

by privacyfence·io.github.privacyfence/privacyfence·v7.0.1·1 stars

Needs the PrivacyFence app from privacyfence.eu: human approval and audit for AI access to your data

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed PrivacyFence yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PrivacyFence tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How PrivacyFence compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 15 versions in the registry since 2026-09-30, latest 2026-11-02, typically one every 1 day.

Install PrivacyFence in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the PrivacyFence repository's README, as published. We do not edit it. Read it on GitHub

PrivacyFence

AI access without giving AI the keys. Approve the sensitive. Automate the routine.

PrivacyFence is an open-source privacy and approval gateway between AI assistants and your business systems. It connects MCP-compatible assistants such as Claude Desktop and Claude Code to Gmail, Google Drive, Calendar, Slack, Salesforce, Jira, Confluence, Telegram, and more.

PrivacyFence enforces, independently of the AI, what an assistant may see and do. Sensitive reads and consequential actions require human approval, while routine requests can be automated by policy. Optional PII detection runs locally before personal data reaches the AI, and every decision is audited.

PrivacyFence runs on an employee’s own computer (macOS, Windows, or Linux) or as a central deployment on infrastructure the organization controls, allowing web clients such as claude.ai to connect as well. Connector credentials stay with PrivacyFence, never with the AI client, and no data passes through PrivacyFence-operated servers — there are none.

Website: privacyfence.eu · Download: privacyfence.eu/download · Docs: privacyfence.eu/docs

Why

Giving an AI assistant access to Gmail, Drive, Slack or Salesforce usually means giving it a standing permission and trusting it to use that permission well. Being allowed to read a record is not the same as wanting it sent to an AI, and a tool name in a client's prompt says little about what is about to change. PrivacyFence puts an independent control point between the assistant and your systems: the AI asks, PrivacyFence decides, and you see what is at stake before it happens.

What it does

change, who is asking and why — not a raw tool name or JSON payload.

  • Human approval for sensitive reads and for writes, on cards that show the actual content or

sends the request to a card even when a rule would have let it through.

  • Local PII detection before a read reaches the AI: likely personal data is highlighted, and it

channel, a Jira project) let routine requests run without a card.

  • Policy-based automation: narrow always-allow rules (a sender domain, a Drive folder, a Slack

an edit made without its key is detected.

  • An audit log of every accepted, denied and automatically approved request, chained so that

account, so the AI client, which runs as you, cannot read them or approve its own request.

  • Credentials stay with PrivacyFence. On a packaged install it runs under its own service

generic proxy for arbitrary MCP tools.

  • A defined set of connectors, each tool with a gate fixed in code. PrivacyFence is not a

How it works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PrivacyFence: common questions

Is PrivacyFence MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the PrivacyFence safety report
Does PrivacyFence need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PrivacyFence maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v7.0.1.
What can I use instead of PrivacyFence?
Servers from other publishers that do the same job: SSH — policy-gated remote access MCP server and SSH Manager MCP server.
How does PrivacyFence compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

Alternatives to PrivacyFence

Same job from other publishers: the closest match first, then the best rated.

  • SSH — policy-gated remote access
    Policy-gated, audited SSH for Linux and Windows hosts: roles, approvals, and an audit log.
    B
  • SSH Manager
    SSH for AI agents: commands, files, backups and health, with approval, a vault and an audit trail
    A