Connection String Secret Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.4Updated Oct 27, 2026

26 rules and 32 safe-replacement snippets for hardcoded connection strings, keys and kubeconfigs acr

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that audits code for hardcoded connection strings, keys and kubeconfigs, offering 26 rules and 32 safe-replacement snippets.

What you can do
  • Audit code for hardcoded connection strings, keys and kubeconfigs using 26 detection rules.
  • Suggest safe replacement snippets from a set of 32 patterns.
  • The manifest lists no individual tools, so the exact operations are not documented.
When to use it
When you want an assistant to check a codebase or configuration for embedded credentials and to propose safer replacements before committing or sharing it.
Requirements
Runs locally as an npm package via npx, so Node.js and network access for the package download are needed. No authentication, environment variables or headers are declared.
Before you install
The README does not match the described purpose and gives no usage details, so verify what the package actually does before running it. It inspects code that may contain live secrets; review any suggested replacements before applying them.

Installation

In SourceWeft

  1. Open Connection String Secret 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

2
  1. v0.1.4LatestSep 23, 2026
  2. v0.1.1Sep 18, 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