Mcp Codeaudit

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 24, 2026

Security audit for AI agents — scan code/diffs for leaked secrets, check deps via OSV.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local MCP server that gives an AI assistant security auditing tools to scan code and diffs for leaked secrets and check dependencies against OSV.

What you can do
Scan code and diffs for leaked secrets as part of a security audit workflow for AI agents. Check project dependencies for known vulnerabilities through OSV. Intended to be run locally by an assistant during code review or audit tasks.
When to use it
Useful when you want an assistant to audit code changes or a repository for exposed secrets and vulnerable dependencies before committing or shipping.
Requirements
Runs as a local process on the user's machine via the npm package @infoinlet/mcp-codeaudit over stdio. Desktop only; no authentication, environment variables or headers are declared. Dependency checks via OSV imply network access.
Before you install
It reads your code and diffs, so audit output may expose source content to the assistant. Dependency lookups are sent to OSV, a third-party service. Review what it scans before running it on private repositories.

Installation

In SourceWeft

  1. Open Mcp Codeaudit 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

This repository has no README.

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 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.