Secure local MCP sidecar for Pandrator guidance and automation
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"pandrator-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Pandrator MCP Pandrator MCP connects your AI assistant to Pandrator. The assistant can inspect projects, help process text and media, and carry out the actions you authorize. It can work with Pandrator on the same computer or on a configured remote host. For a local installation, Manager runs an authenticated Streamable HTTP service on loopback. Stdio is also available for remote targets and hosts that start a separate MCP process for each connection. The sidecar talks only to Pandrator's versioned HTTP APIs. It does not import the application ORM or job queue, accept model-selected URLs, expose arbitrary files or commands, or store credentials in MCP arguments and results. For public workflow concepts, start with [passive dispatch](https://github.com/lukaszliniewicz/Pandrator/blob/main/docs/guides/passive-dispatch.md), [remote and headless operation](https://github.com/lukaszliniewicz/Pandrator/blob/main/docs/operations/remote-and-headless.md), and [privacy and security](https://github.com/lukaszliniewicz/Pandrator/blob/main/docs/security/privacy-and-security.md). This guide covers MCP installation, target configuration, permissions, enrollment, troubleshooting and protocol support. ## Optional workflow skill The repository includes the portable [`pandrator-workflows` skill](skills/pandrator-workflows/SKILL.md), with guidance for quick transcription, passive document/subtitle/speech processing, recording edits, generation, recovery, and verified output delivery. Copy the **whole** `skills/pandrator-workflows` directory, including its `references` folder, into your MCP host's skill directory. For Codex, the usual destination is `~/.codex/skills/pandrator-workflows`; use your configured location if different. Reload the host's skills as needed. Other hosts should use their documented `SKILL.md` installation mechanism. The skill does not install or authorize the MCP connection. Complete the host connection setup below first; an agent can also use the MCP's …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.