Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Make Audit MCP

by arose26version 0.1.0i★ –iRuns on your computer
Registry nameio.github.arose26/make-audit-mcp

Install

Overview

Description from the maker (original English)

Audit Make.com blueprints before importing: hardcoded secrets, dangling refs, risky settings.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Cybersecurity

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "make-audit": {
      "command": "npx",
      "args": [
        "-y",
        "make-audit-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add make-audit -- npx -y make-audit-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "make-audit": {
      "command": "npx",
      "args": [
        "-y",
        "make-audit-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "make-audit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "make-audit-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account arose26, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Cybersecurityi

  • More stars than 0% of the other 995 servers in this category
  • Published to the registry more recently than 35% of the other 995 servers in this category
  • Basic checks equal to or better than 100% of the other 995 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Make Audit MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCPProxy, ConnectSecure MCP, EchelonGraph CVE & Exposure

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCPProxy

by smart-mcp-proxy

Local-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savings

Updated today
Install

ConnectSecure MCP

by servosity

Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots

Runs on your computerUpdated today
Install

CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

make-audit-mcp

An MCP server that audits Make.com (Integromat) scenario blueprints before you import them. Blueprints are shared everywhere — template galleries, forums, "1000 automation" bundles — and importing one means importing its webhooks, HTTP calls, and whatever credential-shaped strings the author left inside.

  • *"What's in this blueprint?"* — modules, apps, trigger, routers, error handling, scenario settings
  • *"Is it safe to import?"* — hardcoded tokens (masked in output), plain-http:// calls, dangling module references, unfiltered router routes, missing error handling, log-retention settings
  • *"What feeds module 5?"* — mapping-reference tracing in both directions

Make's official MCP runs your scenarios; this one reviews the files before they become scenarios. Local files only.

Quick start

Claude Code

claude mcp add make-audit -- npx -y make-audit-mcp

Claude Desktop — add to claude_desktop_config.json:

{

"mcpServers": { "make-audit": { "command": "npx", "args": ["-y", "make-audit-mcp"] } } }

Then: *"Audit C:\\Downloads\\lead-intake.blueprint.json before I import it."*

Tools

ToolWhat it does
inspect_blueprintScenario overview: modules, apps, trigger, routers, error handlers, settings
trace_moduleOne module in detail — parameters/mappings (secrets masked), references out and in
audit_blueprintFindings report: errors / warnings / info

What the auditor checks

  • Credential-shaped literals in parameters or mappings (api_key, token, Authorization, Bearer …) — connections are stripped on export, so any literal secret is exactly what shouldn't be in a shared file. Values are masked (supe… (18 chars)) everywhere, including in findings — the auditor never amplifies a leaked token into the model's context.
  • Dangling references — mappings like {{99.output}} pointing at modules that don't exist (common after hand-editing or merging blueprints). The extractor understands Make's expression syntax: {{formatDate(2.date; "X")}} references module 2, while {{parseNumber(3.14)}} references nothing.
  • Plain-http:// URLs, webhook triggers (anyone with the URL can invoke), routers where no route is filtered, disabled-but-present modules, no error handlers with DLQ off, confidential=false log retention.

Known limitation: execution-order validation across router branches is not attempted — reference checks are existence-only.

Development

npm install

npm test # offline tests — synthetic blueprints built in-suite npm run build # tsc → dist/ node scripts/smoke.mjs # end-to-end: generates a blueprint, drives the server over stdio

Architecture: src/blueprint.ts (recursive module walk, reference extraction, secret masking) and src/audit.ts (checks) are pure logic; src/index.ts is the MCP wiring. Zero runtime deps beyond the MCP SDK.

Not affiliated with or endorsed by Make / Celonis.

License

MIT

Ask PopNx