MCP 2026-07-28 uses per-request log-level selection rather than logging/setLevel. MCP Description warns about the logging server capability for that version. Review the advertisement; the warning alone does not make the description invalid.
Requirement
Section titled “Requirement”The logging server capability is reported as deprecated in MCP 2026-07-28.
Details
Section titled “Details”Rule ID: mcp.capabilities.logging.deprecated
Owner: mcp
Surface: ServerCapabilities · Path: logging
Kind: semantic
Requirement level: should
Status: internal · Enforcement: internal
Protocol version applicability
Section titled “Protocol version applicability”2024-11-05 |
2025-03-26 |
2025-06-18 |
2025-11-25 |
2026-07-28 |
|---|---|---|---|---|
| not-applicable | not-applicable | not-applicable | not-applicable | applies |
Required by
Section titled “Required by”- MCP Description 0.9.0, Section 8.2
- 8. Capabilities: req-capabilities-logging-deprecated
Based on
Section titled “Based on”- Tier 1 — MCP schema.ts and normative specification text: MCP 2026-07-28 schema.ts, ServerCapabilities logging (@deprecated, SEP-2577); specification, Server Features, Utilities, Logging (deprecated)
Examples
Section titled “Examples”Accepted with a warning
Section titled “Accepted with a warning”Source: expected-warning/logging-deprecated-2026.json · Selected: /capabilities/0
{ "logging": {}}Rule Source Code
Section titled “Rule Source Code”capabilities.yaml at immutable tag v0.9.0-rc.3.