SaSameKnowledge
publisheddocumentationdocumentation

Is there a command-line tool to check an MCP server’s readiness?

An open-source, run-it-yourself CLI that applies the Observatory’s readiness methodology directly against one endpoint.

Collection
documentation
Updated
2026-07-30
min read
4
Version
v1
Verified summary

mcp-readiness is SaSame’s open-source command-line tool: run it with npx against any public MCP endpoint to get the same bounded readiness grade the Observatory publishes, with no account or key required.

01

What it is

mcp-readiness is a free, open-source command-line tool published by SaSame to npm. It grades a public Model Context Protocol server against the same spec-bound readiness criteria the Observatory uses — handshake correctness, tool description quality, safety annotations, anti-ghost-content checks, token efficiency and honest error behavior — plus a Claude/ChatGPT directory pre-flight check. It requires no API key, no account and no SaSame credential; the grading logic is public and inspectable in the source repository.

02

How to run it

Run it directly with npx against any public MCP endpoint URL: npx -y mcp-readiness@latest gold-rush start <your-mcp-url> --json. This runs entirely on the caller’s machine or agent — it does not require SaSame to observe the endpoint first, and running it does not itself publish anything to the Observatory.

03

Relationship to the Observatory

The CLI and the Observatory apply the same underlying readiness methodology, but they are not the same act: the CLI is a local, on-demand check anyone can run; an Observatory grade is a signed, dated observation SaSame itself performed and published. A CLI run is a useful way to predict or reproduce an Observatory grade before requesting one — it is not itself a substitute for a signed observation, and running the CLI does not update or create a public Observatory record.

04

Boundary and limitations

The CLI reports a bounded technical readiness grade, not a safety, malware or endorsement verdict — the same boundary the Observatory itself states. It is independently open source: the exact grading code a reader runs is visible on GitHub, not a black box.

EX

Examples

2
  1. 01

    An MCP server operator can run the CLI before requesting Observatory monitoring to catch and fix obvious readiness issues first.

  2. 02

    A prior release of this CLI had a bug that produced false low grades for some servers; the fix and its measured impact are documented in Registry-Runtime Gap and Registry and Runtime Evidence rather than silently rewritten.

RF

References

3