Skip to main content
Glama

mcp-audit

Server Details

Security audit for MCP servers: command injection, unsafe file access, secrets, prompt injection.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so an agent cannot misselect between competing options. Its purpose (security audit of a local MCP server project) is stated unambiguously.

Naming Consistency5/5

The single name scan_mcp_server follows a clear verb_noun snake_case convention that matches the server's domain. No mixed conventions exist to trip up an agent.

Tool Count3/5

A one-tool surface is thin even for a focused audit utility; there is no way to scope, configure, or follow up on a scan. The tool itself is non-trivial and earns its place, but the surface feels under-built.

Completeness3/5

The core operation (scan a path, return a structured risk list) exists, but there are no companion operations such as listing available rules, filtering by severity, or fetching/exporting detailed findings. Agents can complete the primary workflow but hit dead ends for anything beyond a single fire-and-forget scan.

Available Tools

1 tool
scan_mcp_serverCInspect

审计一个 MCP server 项目(本地路径)的安全风险,返回结构化风险清单

Inputs: path (required), include_tests. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources