mcpbeat

mcplint MCP Server

io.github.DLeibner/mcplint
not responding

mcplint is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 27 Jul 2026.

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

Uptime history 40 hours of history · worst hour 0%
40 hours agonow
44.0%
Uptime 24h
40 of 91 checks
1
Tools
read from the server
497 ms
Response time
average over 24h
0
Stars
last commit 27 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcplint --transport http https://mcplint-web.vercel.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcplint": {
      "url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcplint]
url = "https://mcplint-web.vercel.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcplint": {
      "url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcplint": {
      "url": "https://mcplint-web.vercel.app/api/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mcp
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, forward that server's complete tool definitions from client context as snapshot. If those definitions are unavailable, ask the user for its public endpoint or tools/list JSON instead of inventing an audit.

Endpoints

URLTransportStateLatencyChecked
https://mcplint-web.vercel.app/api/mcp streamable-http answering 77 ms 11 min ago

mcplint — questions

Answers built from our own checks of this server.

What can mcplint do?
It exposes 1 tools, read directly from the server on our last check. Among them: check_mcp_server. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is mcplint working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 40 of 91 checks got a reply (44.0%), average response time 497 ms. The bar chart above shows every period we have measured.
The registry lists mcplint as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect mcplint?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does mcplint need an API key?
No. mcplint completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is mcplint?
It answers our handshake in 497 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is mcplint open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.