Skip to main content
Glama

Server Details

Statically audits MCP tool surfaces for token cost, schema quality, and design issues.

If you are the author of this connector, you can claim ownership. 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
Repository
DLeibner/mcp-surface-lint
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusing it with another. The tool's purpose is clear and singular: auditing an MCP tool surface.

Naming Consistency5/5

The single tool follows a clean verb_noun pattern (check_mcp_server) with no competing conventions or inconsistent naming styles.

Tool Count3/5

A single tool is below the typical well-scoped range and feels thin for a server, even though the tool itself is substantive and self-contained. It is not trivial, but the surface is minimal.

Completeness5/5

The tool covers the full apparent domain: auditing an MCP server via URL or tools/list snapshot without invoking targets. No obvious dead ends or missing core operations exist for the stated purpose.

Available Tools

1 tool
check_mcp_serverCheck MCP serverA
Read-onlyIdempotent
Inspect

Statically audit an MCP tool surface from a public HTTPS URL or tools/list snapshot. Returns deterministic scores and findings without invoking any target tool or making LLM calls. When the user asks to check another installed MCP server, read that server's complete tool definitions from client context and pass them as snapshot (MCP name or Cursor-style tool both work; do not use file paths or $ref). If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.

Inputs: url, headers, snapshot. Returns: grade, stats, scores, server, +5 more

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

    • A
      license
      A
      quality
      B
      maintenance
      Checks the MCP server you're building the way clients and agents meet its tool list. It flags what agents misread (vague parameters, writes marked read-only), what breaks clients or prompt caches (tools that appear mid-session, schemas that change on every call), and breaking changes between releases with the version bump they need. Same input, same answer: no LLM involved.
      6
      409 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Performs explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift without executing tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Scores MCP tool definitions and tool lists from 0-100, flagging vague descriptions, missing parameter docs, non-verb-first naming, oversized enums, and nested schemas with severity, rationale, and concrete fixes. It also validates marketplace listings against platform character caps such as MCPize's 500-character short-description limit before deploy.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents and CI workflows to audit instruction files, skill definitions, MCP configurations, tool schemas, and prompt-cache call sites for broken references, token-budget drift, security hazards, and payload waste. It surfaces structured findings so teams can enforce context-layer health before changes ship.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.