MCP Surface Lint
REMOTE · MCPLINT-WEB.VERCEL.APP · SCANNED SEP 20
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcplint-web.vercel.app
claude mcp add --transport http dleibner-mcp-surface-lint 'https://mcplint-web.vercel.app/api/mcp'
{
"mcpServers": {
"dleibner-mcp-surface-lint": {
"url": "https://mcplint-web.vercel.app/api/mcp"
}
}
} {
"servers": {
"dleibner-mcp-surface-lint": {
"type": "http",
"url": "https://mcplint-web.vercel.app/api/mcp"
}
}
} [mcp_servers.dleibner-mcp-surface-lint] url = "https://mcplint-web.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dleibner-mcp-surface-lint": {
"type": "remote",
"url": "https://mcplint-web.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add dleibner-mcp-surface-lint --url 'https://mcplint-web.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
dleibner-mcp-surface-lint:
url: "https://mcplint-web.vercel.app/api/mcp" {
"McpServers": {
"dleibner-mcp-surface-lint": {
"Transport": "http",
"Url": "https://mcplint-web.vercel.app/api/mcp"
}
}
} assistant mcp add dleibner-mcp-surface-lint -t streamable-http -u 'https://mcplint-web.vercel.app/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
- 3 Sept 26 +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.
- 31 Aug 26 +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.
- 29 Aug 26 +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.
- 27 Aug 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcplint-web.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcplint-web.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcplint-web.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://mcplint-web.vercel.app/api/mcp | HTTPS enforced | 308 | https://mcplint-web.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_mcp_server Check MCP server ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| findingCounts | object | yes | – |
| findings | array | yes | – |
| grade | string | yes | – |
| scores | object | yes | – |
| server | object | yes | – |
| source | string | yes | – |
| staticAnalysis | boolean | yes | – |
| stats | object | yes | – |
| targetToolsInvoked | boolean | yes | – |
No examples provided.
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.