Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.
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.
JANUSCOPE_SESSIONAPI keyoptionalOptional client-side correlation id stamped onto every audit record. Useful for cross-process tracing.
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.
Forge read 62 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.