# MCP Surface Lint (remote · mcplint-web.vercel.app)

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

- Trust score: 88/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcplint-web.vercel.app`: 88/100 (this document), [markdown](https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp.md), [page](https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp)

## Channel facts

- Endpoint: `https://mcplint-web.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 206 tokens (~206/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MCP Surface Lint server?

MCP Surface Lint is a hosted endpoint at https://mcplint-web.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dleibner-mcp-surface-lint 'https://mcplint-web.vercel.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dleibner-mcp-surface-lint": {
      "url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.dleibner-mcp-surface-lint]
url = "https://mcplint-web.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dleibner-mcp-surface-lint": {
      "type": "remote",
      "url": "https://mcplint-web.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dleibner-mcp-surface-lint --url 'https://mcplint-web.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dleibner-mcp-surface-lint:
    url: "https://mcplint-web.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dleibner-mcp-surface-lint": {
      "Transport": "http",
      "Url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dleibner-mcp-surface-lint -t streamable-http -u 'https://mcplint-web.vercel.app/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-10 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-31 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (1)

### `check_mcp_server` (~206 tokens)

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.

Input parameters:

- `headers` (object): Optional HTTP headers sent only while reading the remote tools/list response.
- `snapshot`: A tools/list JSON response, mcplint snapshot, or client tool dump containing a tools array. Each tool needs `name`, or the Cursor-style `tool` alias. Forward another installed server's complete tool…
- `url` (string): Public HTTPS Streamable HTTP MCP endpoint to inspect.

Output parameters:

- `findingCounts` (object)
- `findings` (array)
- `grade` (string)
- `scores` (object)
- `server` (object)
- `source` (string)
- `staticAnalysis` (boolean)
- `stats` (object)
- `targetToolsInvoked` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp#diagnostics

## Score history

- 2026-09-20: 88
- 2026-09-19: 88
- 2026-09-18: 88
- 2026-09-17: 88
- 2026-09-16: 88
- 2026-09-15: 88
- 2026-09-14: 88
- 2026-09-13: 88
- 2026-09-12: 88
- 2026-09-11: 88
- 2026-09-10: 88
- 2026-09-09: 88
- 2026-09-08: 87
- 2026-09-07: 87
- 2026-09-06: 86
- 2026-09-05: 86
- 2026-09-04: 85
- 2026-09-03: 85
- 2026-09-02: 84
- 2026-09-01: 84
- 2026-08-31: 84
- 2026-08-30: 83
- 2026-08-29: 83
- 2026-08-28: 82
- 2026-08-27: 82
- 2026-08-26: 81
- 2026-08-25: 80
- 2026-08-24: 79
- 2026-08-23: 79
- 2026-08-22: 78

## Common questions

### What is the MCP Surface Lint server?

MCP Surface Lint is listed in the public MCP registry as io.github.DLeibner/mcp-surface-lint. Statically audits MCP tool surfaces for token cost, schema quality, and design issues. This page covers its hosted endpoint (https://mcplint-web.vercel.app/api/mcp).

### Is the MCP Surface Lint server safe to use?

MCP Surface Lint scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCP Surface Lint server expose?

MCP Surface Lint exposes 1 tool: check_mcp_server. Their descriptions and schemas cost roughly 206 tokens of context every time the server is loaded.

### Does the MCP Surface Lint server require authentication?

No. We connected to MCP Surface Lint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCP Surface Lint server still maintained?

MCP Surface Lint is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcplint-web.vercel.app/api/mcp
- Repository: https://github.com/DLeibner/mcp-surface-lint
- Website: https://mcplint-web.vercel.app/install
- Changelog RSS feed: https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dleibner-mcp-surface-lint/api-mcp