Mcp Probe
Score and inspect your own MCP server for publishability, schema, and protocol compliance before you ship it to a registry.
Overview
MCP Probe is a Ship-phase MCP server that inspects and scores any MCP server 0–100 on publishability, schema, and protocol before publish.
What is this MCP server?
- Inspect any MCP server and produce a 0–100 publishability score
- Checks schema and protocol conformance before registry publish
- npm package @incultnitollc/mcp-probe v1.1.2 with npx serve entry
- stdio transport for local agent-driven audits
- Purpose-built for MCP authors, not end-user app integrations
- Scoring scale: 0–100 on publishability, schema, and protocol
- npm package version 1.1.2
- Invocation pattern: npx with positional argument serve
What problem does it solve?
Publishing an MCP server blindly leads to registry rejections and broken protocol edges you only discover after users connect.
Who is it for?
Solo devs authoring MCP servers who want agent-assisted preflight checks against schema and protocol expectations.
Skip if: Teams only consuming third-party MCPs with no intent to author or publish their own servers.
What do I get? / Deliverables
After running MCP Probe, you get a scored readiness picture and clearer fixes before you publish or share your MCP server.
- 0–100 publishability score for the target MCP server
- Schema and protocol inspection feedback via MCP tools
- Clearer pre-publish fix list before registry upload
Recommended MCP Servers
Journey fit
How it compares
MCP packaging inspector and scorer, not a production observability stack or pentest suite.
Common Questions / FAQ
Who is MCP Probe for?
MCP server authors and indie builders preparing to publish who need structured inspection and a 0–100 readiness score.
When should I use MCP Probe?
Use it in ship review (and late build agent-tooling) immediately before registry publish or after major server.json changes.
How do I add MCP Probe to my agent?
Add stdio MCP config for @incultnitollc/mcp-probe via npx with the serve positional argument, then point probe tools at the server you are validating.