- Has a README
Repository has a README.md
- Has a LICENSE
The repository has a LICENSE file
- Has no glama.json
This repository doesn't have a valid glama.json. Add one by following these steps.
- Server can be inspected
View server inspector
- Has at least one toolViewserver schema
- Has no known vulnerabilities
Indicates that the server is safe to use.
- Claimed by the author
If you are the author,
- Has no related MCP servers
User-submitted related MCP servers help with discoverability.
How to claim the server?
If you are the author of the server, you simply need to authenticate using GitHub.
However, if the MCP server belongs to an organization, you need to first add glama.json to the root of your repository.
{
"$schema": "https://glama.ai/mcp/schemas/server.json",
"maintainers": [
"your-github-username"
]
}Then, authenticate using GitHub.
Browse examples.
How to add a LICENSE?
Please follow the instructions in the GitHub documentation.
Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear on the server after this time, you can manually trigger a re-scan through the MCP server admin interface.
How to sync the server with GitHub?
Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.
To manually sync the server, click the "Sync Server" button in the MCP server admin interface.
GitHub Badge
Glama performs regular codebase and documentation scans to:
- Confirm that the MCP server is working as expected.
- Confirm that there are no obvious security issues with dependencies of the server.
- Extract server characteristics such as tools, resources, prompts, and required parameters.
Our directory badge helps users to quickly assess that the MCP server is safe, server capabilities, and instructions for installing the server.
Copy the following code to your README.md file: