grim-mcp

io.github.AbduljabbarBXRPublished by GitHub account AbduljabbarBXRv0.6.2Updated Oct 24, 2026

Security audit for AI agents: code, deps, exposure, secrets, drift, SBOM, and IoC.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant run security audits of code, dependencies, exposure, secrets, drift, SBOM, and indicators of compromise.

What you can do
grim-mcp is a security audit server for AI agents. According to its registry description, it covers code, dependencies, exposure, secrets, drift, SBOM, and IoC checks. No tool list is published, so the exact commands and outputs are not documented here.
When to use it
Consider it when you want an assistant to help audit a codebase or project for security issues such as vulnerable dependencies, exposed secrets, configuration drift, or indicators of compromise. It is aimed at security review workflows rather than general development tasks.
Requirements
Runs as a local process on the user's machine over stdio, available as the npm package grim-mcp or the PyPI package grim-mcp, so a Node.js or Python runtime is needed. No authentication, environment variables, or headers are declared. Desktop only; not available as a web executable.
Before you install
It performs security auditing, which typically means reading source code, dependency manifests, and configuration, and may surface secrets found in those files. No credentials or write actions are declared, but the published description does not document what data is read or sent anywhere, so review the package before running it on sensitive repositories.

Installation

In SourceWeft

  1. Open grim-mcp 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.

Tools

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

Version history

3
  1. v0.6.2LatestSep 19, 2026
  2. v0.5.0Sep 19, 2026
  3. v0.2.2Sep 18, 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.