datacore-mcp (datacore-one/datacore-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.
MCP server exposing Datacore's knowledge base, GTD, and engram memory to any AI assistant.
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
datacore-one
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
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
js-yaml: Exponential parsing time in flow collections leads to denial of service
js-yaml: Quadratic-complexity (O(n^2)) DoS via !!omap tag in YAML11_SCHEMA
js-yaml: YAML merge-key chains can force quadratic CPU consumption in js-yaml
tsup DOM Clobbering vulnerability
DATACORE_CACHE_TTL60 File cache TTL in secondsDATACORE_CORE_PATHOverride with environment variables: DATACORE_PATH (full) or (core).DATACORE_HTTP_HOST127.0.0.1 HTTP bind addressDATACORE_HTTP_PORT3100 HTTP transport portDATACORE_LOG_LEVELwarning debug, info, warning, errorDATACORE_PATHOverride with environment variables: (full) or DATACORE_CORE_PATH (core).DATACORE_PYTHONDATACORE_TIMEZONESystem IANA timezone (e.g., Europe/Ljubljana)DATACORE_TRANSPORTstdio stdio or httpTool 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
12/12 tools missing one or more hints — datacore_capture (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); datacore_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); datacore_ingest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 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 test coverage
7/12 tools referenced in tests (58%)
Write tests that reference each tool by name so every tool has at least one test.
Production dependencies are patched
0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.0.0 (high), js-yaml@5.0.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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/datacore-one-datacore-mcp-1k08yu)?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