{
  "id": 72152,
  "title": "The MCP 2026-07-28 spec is final - check your server in one command!",
  "url": "https://urgent.news/2026/08/03/the-mcp-2026-07-28-spec-is-final-check-your-server-in-one-command",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-03T05:24:56.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mcpscore/the-mcp-2026-07-28-spec-is-final-check-your-server-in-one-command-438k"
  },
  "original_language": "en",
  "account": "The Model Context Protocol's 2026-07-28 revision went final on July 28, marking a significant change as the lifecycle moves to stateless requests. For those maintaining an MCP server, there are two key questions to consider: is the server still well-built and is it ready for the new spec? The mcpscore tool answers both questions in a single command, uvx mcpscore https://your-server.example/mcp. This command requires no installation or API key and provides a quality score between 0 and 100, along with a list of specific fixes required. The audit consists of 72 deterministic rules, each referencing the relevant spec section, categorized into four areas: Protocol (version negotiation, transport correctness, error shapes), Tools (names, titles, descriptions, input/output schemas), Security & Auth (TLS, auth posture, safe error handling), and Readiness (preparation for the new lifecycle). The results remain consistent for the same server, making it stable for continuous integration (CI) processes and read-only, listing tools while probing behavior without calling them. This tool can audit local servers in any language via stdio, including those behind OAuth, providing a partial audit with a token or a partial audit with no credentials, including checks for auth-posture rules, WWW-Authenticate challenge, RFC 9728 protected-resource metadata, authorization server's RFC 8414 metadata, and PKCE support. The token remains concealed in logs or reports. CI users can utilize mcp-box/mcpscore-action@v1 with a minimum score of 90, which comments on the PR and fails the check if the threshold is not met. Additionally, a live score badge can be added to a project's README from the report page at mcpscore.dev, reflecting the server's latest score. Mcpscore is distinct from an official conformance suite, focusing instead on assessing a server's quality, akin to how Lighthouse scores a web page's quality instead of just its validity. The tool is built on the official MCP Python SDK v2, open source under the MIT license, and its methodology is publicly available at https://docs.mcpscore.dev/methodology.",
  "summary": "The Model Context Protocol's 2026-07-28 revision went final on July 28. It's a meaningful one: the lifecycle moves to stateless requests. If you maintain an MCP server, the two questions are: is my server still well-built, and is it ready for the new spec? mcpscore answers both in one command: uvx mcpscore https://your-server.example/mcp No install, no API key. In a few seconds you get a 0–100…",
  "key_points": [],
  "editors_take": null,
  "illustration": "https://urgent.news/ill/72152.png",
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}