TAR Engine MCP Server

Listed on the official Model Context Protocol Registry and published to PyPI - one-click install into any MCP-compatible agent. It runs locally over stdio via the published package.

People connecting this server to Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-07-23 · ★ 2 · #521 OF 848 MAINTAINED OTHER · VERIFIED 2026-08-25

Apache-2.0 · Python servers · how we verify → /methodology

01 · Install TAR Engine

before you install - you'll need

Set TAR_ENGINE_BYOK_OPENAI_KEY, TAR_ENGINE_URL before connecting.

Claude Code

claude mcp add qingxuantang-tar-engine -- uvx tar-engine

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "qingxuantang-tar-engine": {
      "command": "uvx",
      "args": [
        "tar-engine"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

pypi package tar-engine - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.qingxuantang is GitHub-verified and matches the repo owner

03 · What TAR Engine can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v0.3.0 · 2026-06-16

Adds SARIF 2.1.0 output for GitHub Security tab integration, optional wrappers around shellcheck / semgrep / trufflehog / gitleaks, a --strict severity gate, and a check-tools discovery subcommand. Zero overlap with…

v0.2.0 · 2026-06-16

New tar-engine scan CLI for CI usage. Drop into GitHub Actions / pre-commit hooks to audit AI skill safety before you ship. · What's new · CLI (new tar-engine console script) · scan <path> and list <path> subcommands…

04 · Who maintains TAR Engine

TAR Engine is maintained by qingxuantang. It's the only MCP server we track from this author; the repo dates to Jun 2026.

05 · Facts

category
other - ranked #521 of 848 actively-maintained other servers as of 2026-08-25.
release cadence
2 releases in the last 90 days (latest 2026-06-16)
registry
io.github.qingxuantang/tar-engine (active, first published 2026-07-12 · 2 versions)
packages
pypi:tar-engine

06 · TAR Engine FAQ

What is TAR Engine?

Listed on the official Model Context Protocol Registry and published to PyPI - one-click install into any MCP-compatible agent. It runs locally over stdio via the published package.

Is TAR Engine still maintained?

Yes - as of 2026-08-25, its last commit was 2026-07-23 and it shipped 2 releases in the last 90 days. We re-verify nightly.

How do I install TAR Engine?

Run `uvx tar-engine`. The README documents 2 environment variables (TAR_ENGINE_BYOK_OPENAI_KEY, TAR_ENGINE_URL) to set first. Set TAR_ENGINE_BYOK_OPENAI_KEY, TAR_ENGINE_URL before connecting. You can also paste the ready-made client config above.

Does TAR Engine run locally?

Yes - it's a stdio server: it runs on your machine (via uvx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to TAR Engine