make-audit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_blueprintA | Overview of a Make.com scenario blueprint before importing it: modules, apps used, trigger, routers, error handlers, scenario settings. |
| trace_moduleA | One module in detail: type, parameters and mappings (credential-shaped values masked), which modules it references, and which modules reference it. |
| audit_blueprintA | Risk report before importing: hardcoded credential-shaped values, dangling module references, plain-http URLs, unfiltered router routes, missing error handling, log-retention settings. Secrets are masked in the output. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: inspect_blueprint provides a high-level overview, trace_module dives into a specific module, and audit_blueprint identifies risks. There is no overlap that would confuse an agent.
All tool names follow the verb_noun snake_case pattern (inspect_blueprint, trace_module, audit_blueprint), making the naming perfectly consistent and predictable.
With only 3 tools, the set is well-scoped for an audit-focused server. Each tool covers a necessary step in the workflow (overview, detail, risk assessment), and no tool feels extraneous.
The tools cover the full audit flow: inspect the blueprint for structure, trace modules for detail, and audit for risks. There are no obvious gaps, and the workflow is complete without dead ends.