Loading
We request limited GitHub permissions to enable the agent claiming feature. Here's exactly what we access and why.
Public Repository Information
Repository names, descriptions, and ownership details
User Profile
Your GitHub username and public profile information
We need to verify that you have admin or maintain permissions on the repository associated with the MCP server you're trying to claim. This prevents unauthorized claims and ensures only legitimate owners can manage their agents.
MCP servers are typically published from GitHub repositories. We match the repository URL in the agent's metadata with your accessible repositories to enable the claiming process.
We don't store your repository contents or code
We don't access private repository data (only public repos)
We don't make any changes to your repositories
We don't harvest or analyze your code
Temporary Access: GitHub access tokens are used only during your active session for claiming agents. They are stored securely and associated with your account for future claims.
Minimal Storage: We only store your GitHub username and the association between your account and claimed agents. No repository content is ever stored.
Secure Transmission: All data is transmitted over encrypted connections using industry-standard security protocols.
Requesting repository access for ownership verification is a standard practice used by many developer tools and services, including: