Publisher note
Glama is one of the strongest MCP discovery surfaces in the source pack because it combines directory search with maintainer signals, inspection, scoring, gateway concepts, hosted/private deployments, connectors, and tool search.
What Glama does
Glama positions itself as an MCP registry/search surface, inspector, gateway, hosting layer, connector directory, and tool search experience. The important copy distinction is that directory and inspection claims should be separated from gateway and hosting claims, especially if some features are commercial or plan-dependent.
2026-05-23 snapshot
The Research source pack records that Glama showed 23,968 MCP servers, 3,981 connectors, and 168,936 tools on May 23, 2026, with a servers page timestamped as last updated on the same date. These numbers can be used only as dated snapshot claims.
Maintainer and scoring signals
Glama methodology claims maintainer verification through GitHub OAuth/write-admin access, source ingestion, complete Git history sync, repeated build/run/introspection/audit/scoring, and public API output combining official metadata with derived analysis. These are useful inspection signals, but copy must not convert them into a guarantee that every listed server is safe.
Gateway and hosted deployment context
Glama hosting material says hosted deployments are private by default, access is scoped through account/workspace membership and access tokens, and public endpoints use Streamable HTTP. This belongs in a runtime-model section: hosted and gateway patterns can add access controls and logs, but also introduce provider trust and data-flow questions.
Best fit
Glama is a strong fit for teams that want more than a raw directory. It helps teams inspect server metadata, compare maintenance/security/quality signals, search tools, and evaluate gateway or hosted deployment paths. It should still feed a human review process before production rollout.
Safety caveats
Treat Glama scores and maintainer signals as evidence to inspect. Before using a server, check source ownership, tool permissions, auth model, local versus remote runtime, credential handling, and whether the server is maintained for production use. Do not treat any directory badge as a substitute for code, dependency, and permissions review.
Related topics
- Glama MCP
- MCP directory
- MCP gateway
- MCP inspector
- Glama