docs-ai-search@0.5.02026-10-22
这版把旧的 /sse 入口彻底下线:任何访问都会在鉴权前返回 410 Gone,错误体直接给出服务器的 /mcp 地址。它不是重定向——跟随重定向的 OAuth 客户端会因 /mcp 保护资源元数据报错,且错误信息里根本不提 /mcp。还在用 /sse 的客户端需手动改配 /mcp。
OAuth 资源随之统一为 <origin>/mcp,令牌按此绑定。原先绑在 /sse 或裸源站上的授权,下次刷新会拿到 invalid_grant,客户端需在 /mcp 重新登录;绑在 /mcp 的不受影响。
授权页改用 provider 自带的 consent 助手,服务端持有完整授权请求,页面只提交与浏览器绑定的一次性句柄。取消会向 MCP 客户端回传 access_denied;页面还会显示重定向 URI、Client ID 元数据文档客户端的发布域名,令牌指向本地应用时给出警示。Cloudflare 登录改用 beginUpstream() / finishUpstream(),替代手写的 KV 状态和会话 cookie,支持双标签页同时授权。记忆式授权走 isConsentRemembered(),此前的同意记录不迁移,每个浏览器会再看一次授权页。
另外,Cloudflare 直连令牌现在按 /mcp 资源校验;被判定过期或未知(403 9109)时返回规范要求的 401 invalidtoken,此前误判为 403 insufficientscope,会把客户端引向提权而非重新认证。令牌有效但权限不足,仍返回 403 insufficient_scope。
dns-analytics@0.3.02026-10-22
Minor Changes
- dfd49e5: Retire the /sse URL and upgrade to @cloudflare/workers-oauth-provider 1.2.4.
- Every request to /sse now returns 410 Gone with an application/problem+json body naming the server's /mcp URL, before any authentication. /sse used to serve Streamable HTTP as an alias of /mcp; clients configured with it must switch to /mcp. MCP SDK v1 and v2 clients show the message in their connection error. It is not a redirect, because OAuth clients that follow one reject the /mcp protected resource metadata with an error that never mentions /mcp.
- The OAuth protected resource is now <origin>/mcp, and every token is bound to it. Grants bound to /mcp keep working. Grants bound to /sse, or to the bare origin that 0.x advertised at the root metadata URL, fail their next refresh with invalid_grant (workers-oauth-provider 1.2.4), and the client signs in again at /mcp.
- The consent page uses the provider's consent helpers. The authorization request stays server-side and the page posts only a single-use handle bound to the browser. Cancel now sends access_denied back to the MCP client. The page shows the redirect URI, the publishing domain of a Client ID Metadata Document client, and a warning when the tokens go to a local app.
- Cloudflare sign-in uses beginUpstream() / finishUpstream() in place of the hand-rolled KV state and session cookie. Two tabs can authorize at once, and declining at Cloudflare sends access_denied back to the MCP client.
- Remembered consent uses isConsentRemembered(). Approvals made before this change aren't carried over, so each browser sees the consent page once more.
- Direct Cloudflare API tokens are validated for the /mcp resource.
Patch Changes
- 0702829: A direct Cloudflare credential that Cloudflare rejects as expired or unknown (403 9109: Invalid access token) now gets 401 invalidtoken, as the MCP authorization spec requires for invalid or expired tokens. Before, it got 403 insufficientscope, which sends clients through a scope step-up instead of re-authenticating. A valid token that lacks access still gets 403 insufficient_scope.
- Updated dependencies [0702829]
- Updated dependencies [dfd49e5]
- @repo/mcp-common@0.21.0
containers-mcp@0.4.02026-10-22
/sse 端点正式下线:任何请求都会在鉴权前返回 410 Gone,并以 application/problem+json 告知客户端新的 /mcp 地址,仍配置 /sse 的客户端需尽快切换。OAuth 受保护资源统一为 <origin>/mcp,令牌随之绑定;绑定 /sse 或旧版根地址的授权将在下次刷新时报 invalid_grant,客户端会自动回 /mcp 重新登录。
授权同意页改用官方同意组件,授权请求留在服务端,页面只回传一次性句柄;取消、在 Cloudflare 拒绝授权都会向客户端返回 access_denied。Cloudflare 登录也换成 beginUpstream() / finishUpstream(),支持多标签页同时授权。因同意记忆方式改变,此前的授权不再延续,各浏览器需重新确认一次。
另外修复了直连 Cloudflare API Token 的报错:令牌过期或无效时改为返回 401 invalidtoken,避免客户端误走提权流程;权限不足仍返回 403 insufficientscope。
workers-bindings@0.6.02026-10-22
本次更新退役了 /sse 路径:任何访问都会在鉴权前返回 410 Gone 及 application/problem+json 响应体,指明服务器的 /mcp 地址——之所以不做重定向,是因为跟随重定向的 OAuth 客户端会因 /mcp 的受保护资源元数据报错,且错误信息里根本不提 /mcp。仍在用 /sse 的客户端需要直接切换到 /mcp;绑定到 /sse 或裸源的旧授权会在下次刷新时报 invalid_grant,客户端需在 /mcp 重新登录,绑定 /mcp 的授权不受影响。
授权流程同时换用 @cloudflare/workers-oauth-provider 1.2.4 提供的助手:授权请求留在服务端,页面只回传一次性句柄;取消授权会向 MCP 客户端返回 access_denied,页面也会展示重定向 URI、客户端元数据文档的发布域名,以及令牌流向本地应用时的警告。Cloudflare 登录改用 beginUpstream() / finishUpstream(),支持多标签页并行授权。由于改用 isConsentRemembered(),此前已记住的授权不继承,每个浏览器会再看到一次同意页。
补丁版还修正了错误码:Cloudflare 拒绝的过期或未知凭证(403 9109: Invalid access token)现按 MCP 授权规范返回 401 invalidtoken,不再误报 403 insufficientscope 引导客户端走提权流程;有效但权限不足的令牌仍返回 403 insufficient_scope。
cloudflare-radar-mcp-server@0.3.02026-10-22
Minor Changes
- dfd49e5: Retire the /sse URL and upgrade to @cloudflare/workers-oauth-provider 1.2.4.
- Every request to /sse now returns 410 Gone with an application/problem+json body naming the server's /mcp URL, before any authentication. /sse used to serve Streamable HTTP as an alias of /mcp; clients configured with it must switch to /mcp. MCP SDK v1 and v2 clients show the message in their connection error. It is not a redirect, because OAuth clients that follow one reject the /mcp protected resource metadata with an error that never mentions /mcp.
- The OAuth protected resource is now <origin>/mcp, and every token is bound to it. Grants bound to /mcp keep working. Grants bound to /sse, or to the bare origin that 0.x advertised at the root metadata URL, fail their next refresh with invalid_grant (workers-oauth-provider 1.2.4), and the client signs in again at /mcp.
- The consent page uses the provider's consent helpers. The authorization request stays server-side and the page posts only a single-use handle bound to the browser. Cancel now sends access_denied back to the MCP client. The page shows the redirect URI, the publishing domain of a Client ID Metadata Document client, and a warning when the tokens go to a local app.
- Cloudflare sign-in uses beginUpstream() / finishUpstream() in place of the hand-rolled KV state and session cookie. Two tabs can authorize at once, and declining at Cloudflare sends access_denied back to the MCP client.
- Remembered consent uses isConsentRemembered(). Approvals made before this change aren't carried over, so each browser sees the consent page once more.
- Direct Cloudflare API tokens are validated for the /mcp resource.
Patch Changes
- 0702829: A direct Cloudflare credential that Cloudflare rejects as expired or unknown (403 9109: Invalid access token) now gets 401 invalidtoken, as the MCP authorization spec requires for invalid or expired tokens. Before, it got 403 insufficientscope, which sends clients through a scope step-up instead of re-authenticating. A valid token that lacks access still gets 403 insufficient_scope.
- Updated dependencies [0702829]
- Updated dependencies [dfd49e5]
- @repo/mcp-common@0.21.0
cloudflare-autorag-mcp-server@0.3.02026-10-22
这版把 /sse 这条旧入口彻底下线:任何请求都会在鉴权前收到 410 Gone,响应体是 application/problem+json,并直接告知服务端的 /mcp 地址。之所以不做重定向,是因为 OAuth 客户端跟随跳转后会因 /mcp 的受保护资源元数据报错,错误信息里反而不提 /mcp。仍配置着 /sse 的客户端需手动切换。
配套升级了 @cloudflare/workers-oauth-provider 1.2.4,OAuth 受保护资源统一绑定为 <origin>/mcp。原本绑定 /sse 或裸源地址的授权无法续期,客户端会以 invalidgrant 失败,需在 /mcp 重新登录;绑定 /mcp 的授权不受影响。同意页改用官方 helper,授权请求留在服务端,页面只提交与浏览器绑定的一次性句柄;取消授权会向 MCP 客户端回传 accessdenied,并展示重定向 URI 与元数据文档客户端的发布域名,令牌发往本地应用时另有警告。Cloudflare 登录改用 beginUpstream() / finishUpstream(),两个标签页可同时授权,放弃登录同样返回 access_denied。记忆同意状态走 isConsentRemembered(),此前的批准不继承,每个浏览器会再看一次同意页。
另修复了凭据报错:Cloudflare 判定令牌过期或未知(403 9109: Invalid access token)时,现在按 MCP 授权规范返回 401 invalidtoken,避免客户端误走权限提升流程;有效但权限不足的令牌仍返回 403 insufficientscope。
workers-builds@0.3.02026-10-22
Minor Changes
- dfd49e5: Retire the /sse URL and upgrade to @cloudflare/workers-oauth-provider 1.2.4.
- Every request to /sse now returns 410 Gone with an application/problem+json body naming the server's /mcp URL, before any authentication. /sse used to serve Streamable HTTP as an alias of /mcp; clients configured with it must switch to /mcp. MCP SDK v1 and v2 clients show the message in their connection error. It is not a redirect, because OAuth clients that follow one reject the /mcp protected resource metadata with an error that never mentions /mcp.
- The OAuth protected resource is now <origin>/mcp, and every token is bound to it. Grants bound to /mcp keep working. Grants bound to /sse, or to the bare origin that 0.x advertised at the root metadata URL, fail their next refresh with invalid_grant (workers-oauth-provider 1.2.4), and the client signs in again at /mcp.
- The consent page uses the provider's consent helpers. The authorization request stays server-side and the page posts only a single-use handle bound to the browser. Cancel now sends access_denied back to the MCP client. The page shows the redirect URI, the publishing domain of a Client ID Metadata Document client, and a warning when the tokens go to a local app.
- Cloudflare sign-in uses beginUpstream() / finishUpstream() in place of the hand-rolled KV state and session cookie. Two tabs can authorize at once, and declining at Cloudflare sends access_denied back to the MCP client.
- Remembered consent uses isConsentRemembered(). Approvals made before this change aren't carried over, so each browser sees the consent page once more.
- Direct Cloudflare API tokens are validated for the /mcp resource.
Patch Changes
- 0702829: A direct Cloudflare credential that Cloudflare rejects as expired or unknown (403 9109: Invalid access token) now gets 401 invalidtoken, as the MCP authorization spec requires for invalid or expired tokens. Before, it got 403 insufficientscope, which sends clients through a scope step-up instead of re-authenticating. A valid token that lacks access still gets 403 insufficient_scope.
- Updated dependencies [0702829]
- Updated dependencies [dfd49e5]
- @repo/mcp-common@0.21.0
dex-analysis@0.6.02026-10-22
MCP 服务端完成一次接口收敛:/sse 正式下线,后续一律走 /mcp。访问 /sse 会在鉴权前直接返回 410 Gone,正文用 application/problem+json 说明服务器的 /mcp 地址,MCP SDK v1/v2 客户端能在连接报错里看到这句话——故意不做重定向,因为跟随跳转的 OAuth 客户端会因 /mcp 的受保护资源元数据报错。仍在用 /sse 的客户端需手动改配置。
OAuth 受保护资源现在是 <origin>/mcp,令牌随之绑定:绑在 /mcp 上的授权照常工作,绑在 /sse 或裸源上的下次刷新会拿到 invalidgrant,客户端需在 /mcp 重新登录。授权页改用 provider 自带的 consent helpers,授权请求留在服务端,页面只提交一个绑定浏览器的一次性句柄;取消会向 MCP 客户端回传 accessdenied,并展示重定向 URI、Client ID Metadata Document 客户端的发布域名,令牌发往本地应用时给出警示。Cloudflare 登录换用 beginUpstream() / finishUpstream(),支持多标签页同时授权。此前的「记住授权」不迁移,每个浏览器需再确认一次。另修一处认证细节:Cloudflare 判定令牌过期或未知(403 9109)现在按规范返回 401 invalidtoken,而非触发 scope 提升流程;权限不足仍为 403 insufficientscope。
workers-observability@0.6.02026-10-22
/sse 正式退役:请求一律返回 410,报文指明服务器的 /mcp 地址,客户端需手动切换。不做重定向,是因为跟随重定向的 OAuth 客户端会以不提及 /mcp 的错误拒绝受保护资源元数据。OAuth 受保护资源改为 <origin>/mcp 并绑定所有令牌:原先绑定 /sse 或裸源的授权下次刷新即报 invalidgrant,客户端需重新登录,绑定 /mcp 的照常工作。授权页改用 provider 提供的 consent helpers,授权请求留在服务端,页面只回传一次性 handle;取消会向客户端回送 accessdenied,页面会显示重定向 URI、客户端发布域名,令牌流向本地应用时给出警告。Cloudflare 登录改用 beginUpstream()/finishUpstream(),替代手写 KV 状态与会话 cookie,支持双标签页同时授权。记住授权改用 isConsentRemembered(),旧批准不迁移,每个浏览器会再看到一次授权页。补丁版将被 Cloudflare 判为过期或无效的凭证(403 9109)改为返回 401 invalidtoken,符合 MCP 授权规范,避免客户端误走权限提升而非重新认证;权限不足的有效令牌仍返回 403 insufficientscope。
@repo/mcp-common@0.21.02026-10-22
v0.x 的 /sse 入口正式退役:现在任何对 /sse 的请求都会在鉴权前返回 410 Gone,并在 application/problem+json 正文里指明新的 /mcp 地址——之所以不做重定向,是因为跟随重定向的 OAuth 客户端会因 /mcp 受保护资源元数据报错。仍在用 /sse 的客户端需改配 /mcp;OAuth 受保护资源随之改为 <origin>/mcp,令牌也绑定到它,绑定 /sse 或旧版裸源的授权下次刷新会拿到 invalid_grant,客户端会自动在 /mcp 重新登录。
同期升级到 @cloudflare/workers-oauth-provider 1.2.4,授权页改用官方 consent helpers:授权请求留在服务端,页面只提交一次性 handle,取消会向 MCP 客户端回传 access_denied,页面还会显示重定向 URI、Client ID Metadata Document 客户端的发布域名,并在令牌发往本地应用时给出警告。Cloudflare 登录改用 beginUpstream() / finishUpstream(),支持多标签页同时授权;记住同意改用 isConsentRemembered(),此前的同意记录不继承,每个浏览器需再过一次授权页。
补丁版还修正了错误码:Cloudflare 判定凭证过期或未知(403 9109: Invalid access token)时,按 MCP 授权规范返回 401 invalidtoken,而非误导客户端走 scope 提升流程的 403 insufficientscope;令牌有效但权限不足仍返回后者。