MCP Surface Lint

io.github.DLeibnerPublished by GitHub account DLeibnerv0.4.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant statically audit an MCP tool surface for token cost, schema quality and design issues.

What you can do
It exposes one tool that statically audits an MCP tool surface from a public HTTPS URL or a tools/list snapshot. It returns deterministic scores and findings without invoking any target tool or making LLM calls. When asked to check another installed MCP server, it reads that server's complete tool definitions.
When to use it
Use it when you want to check an MCP server's tool definitions for token cost, schema quality and design issues before installing or publishing it, or to compare results after editing tool descriptions.
Requirements
Network access to the remote endpoint at the audited target must be a public HTTPS URL or a tools/list snapshot. No accounts, API keys or environment variables are declared.
Before you install
The tool definitions of the audited server, which may include descriptions and parameter schemas, are sent to a third-party remote endpoint, so check that they contain nothing sensitive. The audit is read-only and does not call the target's tools.

Installation

In SourceWeft

  1. Open MCP Surface Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.DLeibner%2Fmcp-surface-lint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "surface-lint": {
      "type": "http",
      "url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

1

check_mcp_server

Check MCP server

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.

Parametersurlheaderssnapshot

Version history

2
  1. v0.4.0LatestSep 21, 2026
  2. v0.3.3Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.