D
Caution
48/100
19 days ago

Nyxdoc

MCP server for Nyxdoc, a document system where humans and external agents collaborate on documents with version history, agent to-dos, and workspace permissions.

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

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

getnyxdoc

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
⚠️
Known vulnerabilities in dependencies: 5 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
51 tools verified — handlers match their declared behaviour
27 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.
🔐
You'll be asked for 2 credentials: BETTER_AUTH_SECRET, NYXDOC_COLLABORATION_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies5 high5 medium

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highnext@16.2.10GHSA-6gpp-xcg3-4w24

Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

highnext@16.2.10GHSA-89xv-2m56-2m9x

Next.js: Server-Side Request Forgery in Server Actions on custom servers

highnext@16.2.10GHSA-m99w-x7hq-7vfj

Next.js: Denial of Service in App Router using Server Actions

highnext@16.2.10GHSA-p9j2-gv94-2wf4

Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

highsharp@0.34.5GHSA-f88m-g3jw-g9cj

sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configALLOWED_EMAIL_DOMAIN
configALLOWED_EMAIL_DOMAINS
configAUTH_TRUSTED_ORIGINS
🔐 secretBETTER_AUTH_SECRET
configBETTER_AUTH_URL
configEMAIL_DOMAIN_POLICY
configEMAIL_VERIFICATION_ENABLED
configNYXDOC_BACKUP_ROOT
configNYXDOC_COLLABORATION_INTERNAL_URL
configNYXDOC_COLLABORATION_PORT
configNYXDOC_COLLABORATION_PUBLIC_URL
🔐 secretNYXDOC_COLLABORATION_SECRET
configNYXDOC_DB_PATH
configNYXDOC_DIAGNOSTICS_ENABLED
configNYXDOC_DIAGNOSTIC_RETENTION_DAYS
configNYXDOC_GATEWAY_COLLABORATION_URL
configNYXDOC_GATEWAY_PORT
configNYXDOC_MEDIA_ROOT
configNYXDOC_SOURCE_REVISION
configNYXDOC_TEST_BASE_URL
configPLAYWRIGHT_BASE_URL
configPLAYWRIGHT_EXTERNAL_SERVER
configREGISTRATION_MODE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_NYXDOC_BUILD_SHA
deployNYXDOC_GATEWAY_APP_URL
deploySMTP_PASSWORD
// quality suggestions

Dependencies

46 dependencies, 1 flagged: @playwright/test

All four hints declared on every tool

37/51 tools missing one or more hints — list_agent_workspaces (missing: idempotentHint); get_capabilities (missing: idempotentHint); get_schema (missing: idempotentHint), +34 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

47/51 tool handlers declare input schemas (92%)

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

Tool handlers catch errors

Only 1/51 tool handlers wrap calls in try/catch (2%)

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

Tool test coverage

Only 3/51 tools referenced in tests (6%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

12 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 5 high severity in production deps — next@16.2.10 (high), next@16.2.10 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

2/32 production deps stale: @slate-yjs/core@2023-07-11 (3.1y), y-indexeddb@2023-11-02 (2.7y)

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 6 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 Verified](https://m8ven.ai/badge/mcp/getnyxdoc-nyxdoc-1u7bze?variant=verified)](https://m8ven.ai/mcp/getnyxdoc-nyxdoc-1u7bze)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 432863ea584fcaddab3ce69482c8246ebeef0cad
code hash: 83501c81b5af19975820793552c7c7f030692c5ad5a7880dee76c41c1db61497
verified: 8/2/2026, 8:58:15 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