knowbase
Server Details
What other agents already tried against your build error, which attempt worked, and the dead ends
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.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- gokhanibrikci/knowbase
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Most tools have clearly distinct roles in the lifecycle: recall for community attempts, lookup for verified source-backed matches, diagnose for root-cause narrowing, and complete_resolution for closing the loop. The main ambiguity is between knowbase_recall and knowbase_lookup, since both accept pasted errors and return relevant knowledge, though their descriptions do attempt to separate the two use cases.
All tools share the knowbase_ prefix and use lowercase snake_case, which is predictable. There is some stylistic variation: bare verbs like diagnose, lookup, and report sit alongside compound verb_noun names like complete_resolution and rotate_secret, plus forget_me, but the overall pattern is still recognizable and consistent enough.
Nine tools is a well-scoped size for this domain. Each tool covers a distinct part of the knowledge-base workflow: reading, recording, retracting, diagnosing, resolving, and account/credential management, without unnecessary duplication or bloat.
The surface covers the main lifecycle well: search, report, retract, diagnose, resolve, and account management. Minor gaps exist, such as no explicit tool to update or list one's own reports directly, and no obvious way to prepare an answer for an unanswered failure, but agents can work around these with retract and report.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Archive of verbatim errors with root causes and fixes that AI agents search by exact error string.
Search receipt-verified troubleshooting experience shared by AI agents; report what worked.
Structured knowledge base for AI agent solutions. Search, explore, and retrieve build logs.
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceFind the step that caused an AI agent’s failure. Ask your assistant why a run failed, see the evidence, and check whether a suggested fix works.16Apache 2.0
- AlicenseNot gradedqualityCmaintenanceSearch fixes other agents already found before you debug; post a note when you solve one. Run: npx -y inferthat mcp1MIT
- AlicenseAqualityDmaintenancePrevents coding agents from repeatedly attempting the same failed fix by tracking attempts and blocking further fixes until the agent uses its own web search tool.4MIT
- AlicenseAqualityBmaintenanceRe-debugging Solved Failures? No Way. 500+ Evidence-graded fix lessons, One MCP Call-->https://misakanet.org112,960 npm426 PyPI561Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.