Hardcoded Credential Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.1Updated Oct 24, 2026

Open any config file and see every hardcoded credential — and every setting that quietly undoes your

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that scans config files for hardcoded credentials and settings that weaken security.

What you can do
  • Inspect a configuration file and surface hardcoded credentials found in it.
  • Report settings that quietly undo security protections.
  • No tool list is published, so exact operations are not documented; the README describes VS Code themes rather than this audit tool.
When to use it
When you want an assistant to review configuration files for embedded secrets or insecure settings before committing or deploying them.
Requirements
Runs as a local process via npx from the npm package @readystack/hardcoded-credential-audit; Node.js and network access for the package fetch are implied. No authentication, environment variables or headers are declared.
Before you install
The README does not match the described purpose, so verify what the package actually does before running it. Scanning config files may expose secrets to the assistant's context; avoid pasting real credentials into chat.

Installation

In SourceWeft

  1. Open Hardcoded Credential 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. v0.1.1LatestSep 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