MCP Server 1.0.5 — security update

Security update: authenticated tool scope bypass fixed.

MCP Server 1.0.4 and earlier installations should update before relying on client scope isolation. Under legacy protocol sessions, JSON-RPC batches could bypass the gateway's envelope-level scope checks and audit recording. A valid bearer credential was required; impact depends on installed provider tools. Reported by MrSnoozles.

• Enforce the authenticated client's scope for the actual registered tool immediately before every provider invocation.
• Audit invocation success, tool errors, exceptions and dispatch denials using the individual request identity.
• Reject JSON-RPC batch bodies for all protocol revisions before SDK dispatch, with bounded audit evidence for denied tool attempts. Single-message legacy clients remain supported.

Validation: 42 contract, 27 behavioral, 41 security, 21 ProcessWire and 29 real HTTP checks passed. Regressions exercise a real bundled-SDK 2025-03-26 handshake and batch dispatch, all scope combinations, audit persistence and denial before execution. PHP 8.2 and PHP 8.5 are checked in GitHub Actions.

Install the attached complete runtime ZIP and refresh ProcessWire modules. Existing tokens keep their format and scopes; no database migration or token rotation is required. Clients using batches must send one message per HTTP request. If immediate upgrade is unavailable, keep the remote endpoint disabled. Do not roll back to an earlier runtime with the endpoint enabled.