Cloudflare MCP 分析接口：response_status 默认值改为 success
Access, Cloudflare One - Filter MCP tool-call analytics by response status
这是典型的破坏性变更，API 默认返回值逻辑发生反转。依赖此接口的监控或自动化脚本若不显式添加 response_status=all，将丢失失败与缓存数据的统计，导致误判。请务必检查并更新相关代码。
MCP tool-call analytics support a response_status query parameter on the account, portal, and server timeseries endpoints. Use success, error, or cached to count one status, or all to include every status.
MCP 工具调用分析支持在账户、门户和服务器时序端点上使用 response_status 查询参数。使用 success、error 或 cached 可统计单一状态，或使用 all 以包含所有状态。
The default is success. Previously, counts included failed and cached calls. If you need the previous all-status counts, set response_status=all explicitly:
默认值为 success。此前，计数包含失败和缓存的调用。如需之前的全状态计数，请显式设置 response_status=all：
GET /accounts/{account_id}/access/ai-controls/mcp/analytics/tool-calls/timeseries?response_status=allThe response includes the selected response_status. Invalid values, including an empty value, return 400.
响应中包含所选的 response_status。无效值（包括空值）将返回 400。
For all query parameters and scoped endpoints, refer to View tool-call analytics.
有关所有查询参数和作用域端点，请参阅查看工具调用分析。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力