Automation Auditor 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_workflowA | Read-only checks on n8n JSON, Dify DSL, Activepieces JSON or Trigger.dev code. platform: n8n | dify | activepieces | trigger | auto. Paste an export/source string; no filesystem access, no external calls, no execution. Trigger.dev findings are heuristic and not a substitute for TypeScript checks. |
| audit_openapiB | Check an OpenAPI 3.x JSON spec for common tool integration mistakes. JSON only in this v1 tool. Not a full OpenAPI validation or a security audit. |
| preflight_urlA | Evaluate syntax and literal IP red flags without fetching a URL. For domain names, request-time DNS and HTTP redirects remain unchecked. A manual_review result NEVER means safe to fetch. |
| list_supported_platformsC | List exact export types and limitations; unsupported platforms are never called safe. |
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 4 tools
Each tool targets a clearly distinct artifact or operation: workflow exports, platform capabilities, OpenAPI specs, and URL preflight. No two tools overlap in purpose, and the descriptions explicitly separate their scopes.
All tool names use lowercase snake_case with a verb_noun structure: audit_workflow, list_supported_platforms, audit_openapi, preflight_url. The pattern is predictable and consistent throughout.
Four tools is well-scoped for a focused, read-only auditor. Each tool earns its place by covering a distinct audit target without redundancy or unnecessary surface area.
The surface covers the core auditing tasks: workflow platforms, OpenAPI, and URL preflight, with a helper to list supported platforms. Minor gaps exist—no batch reporting or deeper security/runtime checks—but these are documented limitations rather than missing tools for the stated v1 purpose.