Repository navigation
feat: add mcp registry proof record for witcc.dev - #11
Merged
Merged
Conversation
Contributor
octoDNS planwitcc.dev.cloudflare
Summary: Creates=0, Updates=2, Deletes=0, Existing=16, Meta=False Planned against |
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
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.
Adds one apex TXT value on
witcc.dev:The official MCP Registry reads this record to prove that the club controls the
dev.witcc.*namespace. WIT Calendar uses it to publish its MCP server asdev.witcc/calendar(WITCodingClub/calendar-backend,server.json). The registry reads the record on the apex only, not under a selector.The private key is the
MCP_PRIVATE_KEYsecret on themcp-registryenvironment ofWITCodingClub/calendar-backend. That environment deploys frommainonly.To rotate the key, replace this value. Do not keep the old value next to the new one: the registry tries a stale record first and fails.
Merge this before the calendar-backend PR, because that merge publishes and needs this record.