MCP Registry Server
Server Details
Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- modelcontextprotocol/registry
- GitHub Stars
- 6,314
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 3 of 3 tools scored.
Each tool has a clearly distinct purpose: listing all servers, listing versions for a specific server, and getting details for a specific server version. The hierarchical structure (servers → server → version) eliminates any ambiguity, making it easy for an agent to select the right tool based on the required granularity.
All tool names follow a consistent pattern: they start with 'getV01Servers' and use a hierarchical path structure (e.g., 'ServerNameVersions', 'ServerNameVersionsVersion'). This reflects a RESTful API design with clear, predictable naming that matches the resource hierarchy, making it easy to infer functionality from the name alone.
With 3 tools, the server is well-scoped for its purpose of querying an MCP registry. It covers the essential operations: listing servers, listing versions, and getting version details. This count is appropriate as it provides complete coverage without unnecessary complexity, fitting typical registry use cases efficiently.
The tool set offers complete coverage for querying an MCP registry, with no obvious gaps. It supports listing all servers, drilling down to versions for a specific server, and retrieving detailed information for a specific version (including the latest). This covers the full lifecycle of registry lookup operations without dead ends.
Available Tools
3 toolsgetV01ServersList MCP serversRead-onlyInspect
List MCP servers - Returns a list of all registered MCP servers
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | ||
| search | No | ||
| version | No | ||
| updated_since | No |
getV01ServersServerNameVersionsList all versions of an MCP serverRead-onlyInspect
List all versions of an MCP server - Returns all available versions for a specific MCP server, ordered by publication date (newest first)
| Name | Required | Description | Default |
|---|---|---|---|
| serverName | Yes |
getV01ServersServerNameVersionsVersionGet specific MCP server versionRead-onlyInspect
Get specific MCP server version - Returns detailed information about a specific version of an MCP server. Use the special version latest to get the latest version.
| Name | Required | Description | Default |
|---|---|---|---|
| version | Yes | ||
| serverName | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!