Files
jhonny-editor/code/docs/recommendations/2026-08-18-round-2/24-request-capability-envelope.md
T
João Henrique b541f502ba feat: initial commit - Jhonny Editor
- Adicionado estrutura completa do projeto
- Configurado MCP server para Premiere Pro
- Adicionado documentação e skills
- Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00

1.0 KiB
Executable File

Recommendation 24: per-request capability envelope

Evidence

In stateless MCP, every request carries protocol version and client capabilities in _meta; servers publish their identity and capabilities through discovery and result metadata.

Proposed improvement

Create one validated request envelope used by tool, prompt, and resource handlers. It should normalize protocol version, client capabilities, client identity, auth scope, request ID, and advertised response features before business logic runs.

Acceptance criteria

  • Missing required capabilities fail before any bridge call.
  • Unknown optional capabilities are ignored and recorded with bounded cardinality.
  • Result metadata reports the actual server version handling the call.
  • Fuzz tests cover malformed and adversarial _meta objects.

Client metadata is self-asserted unless independently authenticated.