LoreDocs (labyrinth-analytics/loredocs) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Limited view
69/100
2 months ago

LoreDocs

Versioned document vault system for MCP-compatible AI agents. Organizes reference knowledge (specs, contracts, rules) into per-project vaults with 36 MCP tools for inject, search, link, and version operations. Local SQLite backend. Works with Claude, Cursor, Codex, Hermes Agent. Free (3 vaults) / Pro ($9/mo).

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

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

labyrinth-analytics

Source: Glama

Is this your MCP?

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
43 tools verified — handlers match their declared behaviour
15 read-only tools verified — handlers contain no write/delete/exec
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configLOREDOCS_MCP_COMPAT_DISABLE
configLOREDOCS_MCP_ACCEPTED_VERSIONS
configLOREDOCS_MCP_STRICT
configLOREDOCS_PRO
configLAB_DEV_MODE
configLOREDOCS_ROOTStorage: SQLite database at ~/.loredocs/loredocs.db; document files in ~/.loredocs/vaults/. No cloud storage. Override the root directory with the environment variable.
configLOREDOCS_CIRCUIT_RESET_MINUTES
configLOREDOCS_EMBEDDING_LINKS
// quality suggestions

Tool annotations

38/43 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

5/43 tools missing one or more hints — get_license_tier (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_link_session (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vault_get_session_links (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 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.

Tool inputs are validated

41/43 tool handlers declare input schemas (95%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 8/43 tool handlers wrap calls in try/catch (19%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/labyrinth-analytics-loredocs-1ax33r)](https://m8ven.ai/mcp/labyrinth-analytics-loredocs-1ax33r)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 1b9649a1eacf15fe7b6468b65e0a23ae622b9794
code hash: c107880c312dc5f1162dddfb434ffe628305b3670358034ade93c9613e715e40
verified: 6/20/2026, 9:05:24 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client