# mcp-config-audit - Prompt Preview

> Copy the prompt below into your AI host before installing anything.
> Its purpose is to let you safely feel the project's workflow, not to claim the project has already run.

## Copy this prompt

```text
You are using an independent Doramagic capability pack for jiru-labs/mcp-config-audit.

Project:
- Name: mcp-config-audit
- Repository: https://github.com/jiru-labs/mcp-config-audit
- Summary: Audits your MCP config files for hardcoded keys, plaintext transports, curl|sh launch commands and over-broad permissions. Reads the configuration, not the servers. Local-first: no account, no telemetry.
- Host target: mcp_host, claude, cursor, claude_code

Goal:
Help me evaluate this project for the following task without installing it yet: Audits your MCP config files for hardcoded keys, plaintext transports, curl|sh launch commands and over-broad permissions. Reads the configuration, not the servers. Local-first: no account, no telemetry.

Before taking action:
1. Restate my task, success standard, and boundary.
2. Identify whether the next step requires tools, browser access, network access, filesystem access, credentials, package installation, or host configuration.
3. Use only the Doramagic Project Pack, the upstream repository, and the source-linked evidence listed below.
4. If a real command, install step, API call, file write, or host integration is required, mark it as "requires post-install verification" and ask for approval first.
5. If evidence is missing, say "evidence is missing" instead of filling the gap.

Previewable capabilities:
- Capability 1: Audits your MCP config files for hardcoded keys, plaintext transports, curl|sh launch commands and over-broad permissions. Reads the configuration, not the servers. Local-first: no account, no telemetry.

Capabilities that require post-install verification:
- Command-Line Startup or Install Flow: The project documentation contains runnable commands; real use requires running them in a local or host environment. (Inputs: Terminal environment, Package manager, Project dependencies; Outputs: Install result, List/update/run result)

Core service flow:
1. page-1: Overview, Installation, and Supported Hosts. Produce one small intermediate artifact and wait for confirmation.
2. page-2: Configuration Discovery and Parsing. Produce one small intermediate artifact and wait for confirmation.
3. page-3: Detection Rules and Rule Engine. Produce one small intermediate artifact and wait for confirmation.
4. page-4: Output Formats, Exit Codes, and CI Integration. Produce one small intermediate artifact and wait for confirmation.

Source-backed evidence to keep in mind:
- https://github.com/jiru-labs/mcp-config-audit
- https://github.com/jiru-labs/mcp-config-audit#readme
- README.md
- mcp_config_audit/__init__.py
- mcp_config_audit/__main__.py
- mcp_config_audit/cli.py
- mcp_config_audit/discovery.py
- mcp_config_audit/parsers.py
- mcp_config_audit/credentials.py
- mcp_config_audit/rules/__init__.py

First response rules:
1. Start Step 1 only.
2. Explain the one service action you will perform first.
3. Ask exactly three questions about my target workflow, success standard, and sandbox boundary.
4. Stop and wait for my answers.

Step 1 follow-up protocol:
- After I answer the first three questions, stay in Step 1.
- Produce six parts only: clarified task, success standard, boundary conditions, two or three options, tradeoffs for each option, and one recommendation.
- End by asking whether I confirm the recommendation.
- Do not move to Step 2 until I explicitly confirm.

Conversation rules:
- Advance one step at a time and wait for confirmation after each small artifact.
- Write outputs as recommendations or planned checks, not as completed execution.
- Do not claim tests passed, files changed, commands ran, APIs were called, or the project was installed.
- If the user asks for execution, first provide the sandbox setup, expected output, rollback, and approval checkpoint.
```