Wrap any korg:introspect@v1-aware binary as a Claude Code tool, honoring declared side-effects.
Bridge any -aware CLI to Claude Code via MCP. TypeScript edition. One MCP server, any binary in the ecosystem. After installing once, adding a new tool surface to Claude Code's agent is just one line of config per binary. The TS port of — same wire contract, same safety gating, same conventions as the Python reference, distributed via npm for install. The Python works perfectly — but it requires…
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 14 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”.
Bridge any -aware CLI to Claude Code via MCP. TypeScript edition. One MCP server, any binary in the ecosystem. After installing once, adding a new tool surface to Claude Code's agent is just one line of config per binary. The TS port of — same wire contract, same safety gating, same conventions as the Python reference, distributed via npm for install. The Python works perfectly — but it requires + a Python venv. For Claude Code (a TypeScript app) users on Mac/Linux, the canonical "install a new…
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.