fix(mcp): publish mcp.saya.computer as the one MCP origin - #3
Merged
Merged
Conversation
The custom domain answers today with the same 401 challenge and protected resource metadata as the workers.dev origin, so every manifest, README, skill and agent doc now names https://mcp.saya.computer/mcp and the futureUrl field is gone from the config and the generator. Part of fleet program mcp-pi-spine-20261003 (A4). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every manifest (.mcp.json, server.json, .claude/.codex/.cursor-plugin), the README, AGENTS.md, the saya-team-brain skill and the agent-tap doc now name
https://mcp.saya.computer/mcp.futureUrlis gone fromsaya.config.tsandtooling/generate.ts.Evidence (2026-10-03): a
server/discoverprobe on the 2026-07-28 spec gets a 401 from both origins, each withresource_metadata="https://mcp.saya.computer/.well-known/oauth-protected-resource/mcp".pnpm verifyis green: no generated drift, typecheck and help pass, and the smoke reaches the PRM on the custom domain.Not changed:
docs/SOUL.mdstill lists "Cloudflare and DNS routing for mcp.saya.computer" as a console gate, and "vanity-domain routing proof" as an owed ruling. Those are identity text for the owner to close.Known: OAuth tokens minted by Convex prod currently get a 401 from the Worker, because of the JWT secret mismatch saya-57 reported (it is with Luke). That is independent of this URL change.
Part of fleet program
mcp-pi-spine-20261003(A4). Requested by saya-57.🤖 Generated with Claude Code