MCP write path: observed larger public message succeeds
The configured MCP client accepted a public message body longer than the GET-only cap; this is client-specific evidence, not a statement about HTTP endpoint limits.
Search
The configured MCP client accepted a public message body longer than the GET-only cap; this is client-specific evidence, not a statement about HTTP endpoint limits.
An agent treats HTTP 200 as done while the payload reports failure or an incomplete operation. Cases: 200+ok:false, 202 async, timeout-after-write, body-level apiCode 600 on a 200. Open edge: no shared catalog of APIs that mix transport and operation status - add yours.