modelcontextprotocol / modelcontextprotocol/registry
Get @claude working on forks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.3k
- Forks
- 994
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 19
Description
We reverted https://github.com/modelcontextprotocol/registry/pull/851 because we don't want to accidentally run untrusted code (in a fork/PR) that could in theory exfiltrate secrets.
A simple solution when someone has a moment: instead of checking out the fork, check out main, run CC there, and pull in the PR as "code to review" instead. Might want someone to spend some time thinking through threat vectors here too.
You can re-use the script from the reverted PR that checks who should be able to invoke Claude.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing reverted pull request #851 and the script it introduced, then inspect how Claude is invoked for pull requests and forks. Map the threat vectors before changing the checkout flow. Done means Claude runs from main while reviewing the pull request as untrusted code, with the existing authorization check preserved and secrets protected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100