Skip to main content
Glama
correctover-audit

correctover-audit

Official

audit_mcp_server

Run a free, read-only security audit on an MCP endpoint to detect unauthenticated tool inventory exposure and return a re-verifiable verdict.

Instructions

Run a free, read-only session-security audit against an MCP server endpoint (3 probes, no handshake forgery). Returns a re-verifiable verdict such as "unauthenticated-surface". Use on endpoints you own or are authorized to test.

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": {
      "url": "<url>"
    },
    "name": "audit_mcp_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesMCP endpoint URL, e.g. https://your-server.example/mcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it usefully discloses read-only behavior, three probes, no handshake forgery, and a re-verifiable verdict such as "unauthenticated-surface". However, it leaves gaps around rate limits, failure behavior, and how the verdict is returned, which matters for a security probing tool. A 3 reflects that the core safety and output shape are stated, but not fully fleshed out.

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?

The description is three compact sentences and front-loads what the tool does before adding authorization guidance and verdict details. It is efficient, though splitting the core action and safety constraint into separate sentences slightly reduces density.

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

Completeness3/5

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

For a one-parameter read-only audit with no output schema, the description covers the action, safety posture, probe count, and example return value. It still omits operational details such as probe behavior, error modes, and output structure, leaving it adequate rather than fully complete.

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%, so the URL parameter and its format are already documented in the input schema. The description adds no further parameter meaning, such as URL constraints or format examples, beyond what the schema provides; 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?

The description states a specific verb and resource: run a read-only session-security audit against an MCP server endpoint. It also defines the scope, three probes and no handshake forgery, so the agent can tell exactly what the tool does without needing sibling differentiation.

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

Usage Guidelines4/5

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

It gives clear usage context by saying to use the tool on endpoints you own or are authorized to test. That establishes an important prerequisite, though there are no named alternatives or when-not scenarios beyond the authorization boundary.

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

Deploy Server

Other Tools