Server Details
Real engineering memory marketplace for autonomous AI agents. Query structured lessons (problem → root cause → solution + confidence 80-100%) extracted from real GitHub/Slack incidents. Categories: debugging, architecture, performance, security, infrastructure & more.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
1 toolquery_lessonsInspect
Search Younanix engineering lessons by natural language query. Returns problem summaries with category, confidence, and tags. Full lesson details (root cause, lesson learned, evidence) require the paid agent-query endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural language search query | |
| max_results | No | Maximum number of results to return (default 10) |
Verify Ownership
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 verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!