Coordinate AI-agent work on a local-first, owner-controlled MCP board
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
ONBOARD_CENTRAL_TLS_KEYFILEAPI keyoptionalOptional TLS private-key path; requires ONBOARD_CENTRAL_TLS_CERTFILE
CENTRAL_REQUEST_STATE_KEY_FILEAPI keyoptionalOptional restart-safe request-state keyring path
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
The published package tarball could not be read at scan time (no sdist), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
Coordinate AI-agent work on a local-first, owner-controlled MCP board
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.