Incultnitollc/mcp-probe: MCP server diagnostics — CLI + TypeScript library. Tests every tool, resource, and prompt, then scores health. Published on npm as @incultnitollc/mcp-probe. (opens in new tab)

Before you publish an MCP server, run 10 checks. Most servers fail at least three — and the failures are invisible until an agent picks the wrong tool, hallucinates an argument, or silently drops your server on connect. This is the checklist we built mcp-probe to enforce, distilled to what actually breaks in the wild. TL;DR — A publishable MCP server connects cleanly, names tools unambiguously, describes every argument, validates inputs, and ships install metadata. The single most common fail...