Sandboxed workspace MCP: file ops, argv-only run_command, list_files; BYO LLM prompts.
Workspace-scoped MCP tools for building Cursor-style agents: readfile, writefile, editfile, runcommand, listfiles. Includes strict, versioned system prompts () and OpenAI-style tool definitions so your app can wire any LLM with one import. The LLM and API keys stay in your app. This package provides tool execution, sandboxing, and prompts—not a hosted model. OpenAI + in-process tools: the Tier B…
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 0 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”.
Workspace-scoped MCP tools for building Cursor-style agents: readfile, writefile, editfile, runcommand, listfiles. Includes strict, versioned system prompts () and OpenAI-style tool definitions so your app can wire any LLM with one import. The LLM and API keys stay in your app. This package provides tool execution, sandboxing, and prompts—not a hosted model. OpenAI + in-process tools: the Tier B section below is self-contained—copy the Python into a script, module, or REPL; no separate artifact…
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.