Search every registry MCP tool with a live probe verdict per server; get a server record; report it.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 3 tools
Each tool has a clearly distinct purpose: get_server retrieves details for a specific server, search_tools discovers tools by functionality, and report_experience publishes user feedback. There is no overlap or potential for misselection.
All tool names follow a consistent verb_noun pattern: get_server, report_experience, search_tools. The nouns and verbs are clear, and there are no mixed naming conventions.
With only 3 tools, the surface is compact but well-scoped for a hub focused on discovery, lookup, and feedback. It sits at the low end of the ideal range, but each tool serves a necessary function with no redundant additions.
The set covers the core workflows: discover tools (search_tools), inspect a server (get_server), and contribute experiences (report_experience). A minor gap is the lack of a 'list all servers' operation, but search covers discovery adequately.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_serverreport_experiencesearch_toolsFind MCP servers and check whether they actually respond, via live handshake probes.
Health and token cost of every remote MCP registry server, probed daily. Look up, search, or probe.
Search the public universe of MCP servers. This data comes from the Official MCP Registry.
Search and browse every MCP server in the Model Context Protocol registry.
Add one secure layer between your agents and this server.