knowledge-mcp (yungsimeon/knowledge-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 4 tools. No publisher has claimed this listing.
An MCP server that enables semantic search over a private knowledge base via pgvector, with GitHub OAuth authentication and a RAG pipeline.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
yungsimeon
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
GOOGLE_API_KEYSUPABASE_SERVICE_ROLE_KEY, , AUTH_DOMAIN und SERVER_URL eintragenNEXT_PUBLIC_MCP_SERVER_URLNEXT_PUBLIC_SUPABASE_ANON_KEYNEXT_PUBLIC_SUPABASE_URLSUPABASE_SERVICE_ROLE_KEYSUPABASE_URLTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
4/4 tools missing one or more hints — search_knowledge (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_topics (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_entry (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Descriptions match behaviour
3 tools describe read intent but their handlers mutate — search_knowledge (line 80: supabase.from("mcp_usage_logs").insert({); get_entry (line 80: supabase.from("mcp_usage_logs").insert({); search_by_tag (line 80: supabase.from("mcp_usage_logs").insert({)
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tool inputs are validated
Only 0/4 tool handlers declare input schemas (0%)
Declare an inputSchema with zod/joi/yup on every tool definition.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tool test coverage
Only 0/4 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Tool description accuracy
search_knowledge: description implies read-only but handler writes/deletes/executes; search_by_tag: description implies read-only but handler writes/deletes/executes
Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/yungsimeon/knowledge-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check