Skip to main content
Glama

Moltline Agent Governance & MCP Auditor

This connector has been deprecated

Superseded listing, not a dead server. This entry was imported from an early Glama registration under com.moltlinestudio.mcp; the same server is listed under its official MCP Registry name — use com.moltlinestudio/govern. Endpoint unchanged: https://mcp.moltlinestudio.com/govern — still live, still free on the free tier. Only this duplicate entry is deprecated.

Audit Mcp Config

audit_mcp_config
Read-onlyIdempotent

Audit an MCP server config for risk-ranked posture findings. FREE.

Flags exposed machine credentials in the config, required inputs that aren't gated/optional, unpinned versions, over-broad env access, dangerous auto-run flags, whole-disk or home-folder roots, wildcard allow-lists and remote servers over plain HTTP. In a client config (mcpServers or servers block) each server is checked on its own: unpinned packages and credentials written into the file are named. It never echoes any matched secret value back. Typical input {"config": "<mcpize.yaml, mcp.json, or a Claude/Cursor servers block>"} returns {"posture_score": 0-100, "verdict": "...", "findings": [{"line": N, "severity": 1-5, "issue": "...", "fix": "..."}], "note": "..."}.

Use on a server configuration document. Not for a skill or instruction file (audit_skill_file) and not for untrusted content an agent is about to read (injection_scan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "config": "<config>"
    },
    "name": "audit_mcp_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesThe MCP config to audit, pasted as text or JSON (mcpize.yaml, mcp.json, or a Claude/Cursor servers block).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / config / description
      Previous value: -"The MCP config to audit, pasted as text or JSON —\nmcpize.yaml, mcp.json, or a Claude/Cursor servers block."New value: +"The MCP config to audit, pasted as text or JSON\n(mcpize.yaml, mcp.json, or a Claude/Cursor servers block)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive and closed-world, yet the description still adds real value: it never echoes matched secret values, never raises a protocol error, returns {error: ...} on bad input, and states retry is always safe after correction. The enumeration of what it flags (unpinned versions, credentials in file, wildcard allow-lists, plain HTTP) tells the agent what it will surface before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and scope, then checks, then error behavior; every section is functional. Slightly inflated by the trailing marketing token "FREE." and the redundant return-shape block given an output schema exists, but no sentence is genuinely wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers scope, disambiguation, output shape, failure semantics, and retry safety for a single-parameter audit tool. Even without the output schema the agent would know what comes back and how errors appear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already documents accepted formats, so the schema does the heavy lifting. The description's inline {"config": ...} example largely restates the schema text and adds little new meaning beyond the list of accepted file types, which the schema also names. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Audit an MCP server config") plus the output character ("risk-ranked posture findings"), and explicitly names the two sibling tools it is not (audit_skill_file, injection_scan). An agent can route between them without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use ("Use on a server configuration document") and two explicit when-not-to-use cases, each paired with the correct alternative tool. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources