MCP.Market

PLwC Personal MCP server

by mhoedt-ai·io.github.mhoedt-ai/plwc-gateway·v1.0.1-rc.1·3 stars

Windows x64/Python 3.12 MCPB preview: governed local tools and persistent profiles.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

not scanned yet

Adoption
New

3 stars

Reviews

Write one

Nobody has reviewed PLwC Personal yet.

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

PLwC Personal 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 PLwC Personal compares

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

Safety score
83/100
higher than 65% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers

Release history: 2 versions in the registry since 2026-07-13, latest 2026-10-12, typically one every 91 days.

Install PLwC Personal in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

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

PLwC — Personality Layer with Conscience

PLwC is a local, model-independent governance gateway for AI tool access, persistent context and controlled memory. It is not the agent and it is not the language model. It is the independent control layer between the AI host, the model and local tools.

AI host / model
       |
       v
PLwC governance gateway
       |
       v
tools, files, profiles, memory and sandbox

PLwC exposes one visible MCP server, routes all capabilities through policy and governance checks, and provides workspace, document, sandbox, profile, reflection and audit-oriented controls. The gateway is designed for MCP-capable hosts in general. Claude Desktop is a packaged and smoke-tested route, but the boundary remains useful when a host, such as ChatGPT Work, Claude or another MCP client, also offers its own file access or agent features.

Status

until the external browser Store gates pass.

  • Current product version: PLwC 1.0.0; distribution remains a pre-release

development history, local evidence, real profiles and workspace data are intentionally not included.

  • This repository retains a privacy-filtered public release boundary. Private

PLwC Chat Bridge 1.0 integration for Chrome, Brave and Edge.

  • Version 1.0.0 contains the complete eight-tool governed Gateway and the

PLwC-Setup-1.0.0-installer-r24.exe, SHA-256 b00c5298bf6faa76c5910ecbb36497a8aa4764a8a3720f73a450851a3fc3e4d0. It is available from the versioned GitHub pre-release.

  • The explicit unsigned Windows candidate is

pass. On 2026-08-30, the private Chrome submission entered pending review with automatic publication disabled, and the hidden/link-only Edge submission entered review. Store approval, controlled availability and Store-signed live-browser acceptance remain separate gates.

  • Internal source, installed-update, Bridge, extension and installer gates
  • The current Windows Setup and packaged MCPB are not signed.

PLwC is not production-certified. It is local infrastructure under active development.

What PLwC is - and what it is not

PLwC is:

reflection and Governor flows;

  • an MCP gateway, not its own agent;
  • a local governance boundary between model requests and tool execution;
  • model- and host-independent policy for MCP-capable hosts;
  • controlled memory, profile and persona management through explicit profile,
  • a single public MCP boundary named plwc-gateway.

PLwC is not:

outside PLwC;

  • a standalone AI platform;
  • a desktop agent;
  • the language model or a replacement for the user's chosen AI host;
  • a full proxy for all model traffic;
  • protection for data that a user or host sends directly to a cloud model

gateway.

  • permission to expose raw PLfC/PBA or Desktop Commander MCP servers beside the

What PLwC does

/ exact replace / batch read).

  • Exposes exactly one visible MCP server: plwc-gateway.
  • Provides exactly eight public facade tools (see below).
  • Controls workspace operations (read / write / search / move / rename

limits.

  • Creates and reads DOCX, XLSX, PPTX and PDF artifacts.
  • Inspects, extracts, merges, splits and rotates PDFs.
  • Inspects, extracts and creates ZIP archives with bounded safety

blocks (PNG, JPEG, WEBP, first-frame GIF).

  • Reads workspace raster images and returns them as MCP image content

silent fallback to a host shell.

  • Runs sandboxed Python and Shell snippets through Docker, with no

and Governor plan / apply flows including reflectioncondensation with planid apply.

  • Manages profiles, reflection writes, memory and persona governance,

writes.

  • Blocks protected profile and governance paths from direct workspace
  • Emits structured local audit events for high-risk operations.

Public tools

Shortened. The full README is on GitHub.

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

PLwC Personal: common questions

Is PLwC Personal MCP server safe?
Mostly: it is graded B (83/100). Read the PLwC Personal safety report
Does PLwC Personal need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PLwC Personal maintained?
The last commit was 41 days ago (2026-09-24). The latest release is v1.0.1-rc.1.
How does PLwC Personal compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.