Mcp Config Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026

Audit one mcp.json for what an agent config gives away — inline API keys, unpinned npx launches, pla

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local stdio MCP server that audits an mcp.json agent configuration for exposed secrets, unpinned npx launches and similar risks.

What you can do
Audit a single mcp.json file for what an agent configuration gives away, such as inline API keys and unpinned npx launch commands. Report findings back to the assistant so the configuration can be reviewed and tightened. No tool list is published, so the exact operations are not documented beyond this audit purpose.
When to use it
Useful when you maintain MCP or agent configuration files and want a quick check for inline credentials or loosely pinned package launches before sharing or committing them.
Requirements
Runs as a local process on the user's machine via npx from the npm package @readystack/mcp-config-audit. Desktop only; no authentication, environment variables or headers are declared.
Before you install
The audit reads a configuration file that may itself contain inline API keys, so treat any reported findings as sensitive. The README content does not match the audit description, so verify the package before running it.

Installation

In SourceWeft

  1. Open Mcp Config Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 19, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Audit integrations