Supply Audit

by kimmawlaio.github.kimmawla/mcp-supply-auditv0.1.0

How the score works

Audits MCP servers as software artifacts: registry entries, packages, configs, tool definitions.

  • Runs on your machine

Version checks

  • Available on PyPI, latest 0.1.0 · checked

It runs from a package on your machine, so we install and start its newest version every week, resolving its dependencies afresh each time.

Checked on 1 day of the last 90, started on 1 day.

  • Started
  • Not run
  • Failed
  • No check that day
VersionResultChecked
0.1.0 Starts, 6 tools again

How we check

Run it on your machine

Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

{
  "amp.mcpServers": {
    "mcp-supply-audit": {
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server `io.github.kimmawla/mcp-supply-audit`

Its page: https://plug.directory/servers/io.github.kimmawla/mcp-supply-audit

It runs on the person's machine and needs uv installed.

Use the section for the person's client.

## Claude Desktop, Cursor, Devin Desktop, Cline, LM Studio, Gemini CLI, mcp-client-cli, oterm, TUUI, BoltAI, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Claude Desktop: claude_desktop_config.json (Settings › Developer › Edit Config)
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- mcp-client-cli: ~/.llm/config.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- TUUI: resources/assets/config/mcp.json in the installed app
- BoltAI: ~/.boltai/mcp.json
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "mcp-supply-audit": {
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport stdio mcp-supply-audit -- uvx mcp-supply-audit==0.1.0
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "mcp-supply-audit": {
      "type": "stdio",
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "mcp-supply-audit": {
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "mcp-supply-audit"
    type: stdio
    command: "uvx"
    args:
      - "mcp-supply-audit==0.1.0"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "mcp-supply-audit":
    type: stdio
    name: "mcp-supply-audit"
    enabled: true
    cmd: "uvx"
    args: ["mcp-supply-audit==0.1.0"]
    env_keys: []
    envs: {}
    timeout: 300
```

## Codex

Run in a terminal:

```sh
codex mcp add mcp-supply-audit -- uvx mcp-supply-audit==0.1.0
```

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "mcp-supply-audit": {
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "mcp-supply-audit": {
      "command": "uvx",
      "args": ["mcp-supply-audit==0.1.0"]
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem