The rule engine behind the mcpready CLI: probe an MCP server over stdio or Streamable HTTP and build a graded, spec-cited readiness report.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.
Hyperscale Product reads and contract operations over MCP.