x=hub

your toolset

    build deployment
    sign in

    PrivacyFence

    mcpother official scan blocked
    io.github.privacyfence/privacyfence · v6.3.0
    deploy just this

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

    run it

    blocked by the security scan
    Blocked by the security scanThe worker scanned github.com/privacyfence/privacyfence at fbd8407204dd for v6.3.0 with [email protected][email protected] on 2026-10-17, before building it, and found code that looks malicious: threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1376, threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1201, threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1205. It built nothing, and the hub offers no way to run this version: no package, no image, no build, no web service. An operator can look at the findings and let it run; a new version is scanned again.

    connect to it

    copy what your client needs
    {
  "mcpServers": {
    "privacyfence": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add privacyfence -- CHANGE_ME

    {
  "mcpServers": {
    "privacyfence": {
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    {
  "servers": {
    "privacyfence": {
      "type": "stdio",
      "command": "CHANGE_ME",
      "args": []
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.privacyfence/privacyfence
    • not probed yet: tools unpinned, ingest lists them
    • blocked: the worker's security scan of github.com/privacyfence/privacyfence at fbd8407204dd on v6.3.0 found code that looks malicious (threat-filesystem-autostart); nothing is deployed for it

    tools

    Probe result: faileddocker: security scan: github.com/privacyfence/privacyfence at fbd8407204dd has code that looks malicious: threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1376, threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1201, threat-filesystem-autostart in tests/integration/test_macos_packaged_smoke.py:1205

    runs · 1

    the latest tests of this entry by the hub and its workers, newest first
    dateworkermethodstatussandboxreason
    2026-10-17 13:25 local-mac-vm docker failed gvisor docker: security scan: github.com/privacyfence/privacyfence at fbd8407204dd has code that looks malicious: threat-filesystem-autostart in tests/integration/test…