hithereiamaliff/mcp-nextcloud (hithereiamaliff/mcp-nextcloud) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 28 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
52/100

hithereiamaliff/mcp-nextcloud

A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

→ hithereiamaliff/mcp-nextcloud· listed on official

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

⚡ 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

hithereiamaliff

Source: Official · also listed on Smithery

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 →

⚡ Connect GitHub for Live Monitored

Install from

Officialnot scored hereSmitherynot scored here

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.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: KEY_SERVICE_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 18 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: KEY_SERVICE_TOKEN, MCP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical18 high5 medium15 low

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

criticalfast-xml-parser@5.2.5GHSA-m7jm-9gc2-mpf2

fast-xml-parser has an entity encoding bypass via regex injection in DOCTYPE entity names

high@modelcontextprotocol/sdk@1.17.4GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.4GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.11.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

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_ORIGINSRestricted CORS: Only origins listed in are permitted (defaults to smithery.ai and claude.ai).
configANALYTICS_FILE
configENABLE_MCP_DIAGNOSTICSenable =true
configENABLE_SMITHERY_ENDPOINTSet =true only if you want to publish the dedicated Smithery direct-credentials endpoint.
configHOST
🔐 secretKEY_SERVICE_TOKENUse KEY_SERVICE_URL + only if you want hosted-style usr_... key resolution.
configKEY_SERVICE_URLUse + KEY_SERVICE_TOKEN only if you want hosted-style usr_... key resolution.
🔐 secretMCP_API_KEYImportant: The Smithery endpoint is designed for direct credentials via headers. It does not use the MCP Key Service and does not require the shared .
configMCP_TRACE_HTTP5. Enable temporary tracing with =true and inspect:
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool 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

28/28 tools missing one or more hints — nc_notes_create_note (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); nc_notes_update_note (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); nc_notes_append_content (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 call in production code run through a shell (open.js:6)

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

Secrets stay with their owner

1 secret sent to a request target we could not resolve (KEY_SERVICE_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

1 critical, 18 high severity in production deps — fast-xml-parser@5.2.5 (critical), @modelcontextprotocol/sdk@1.17.4 (high)

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

Dependency freshness

2/10 production deps stale: ts-node-dev@2022-06-27 (4.2y), localtunnel@2023-11-07 (2.9y)

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/hithereiamaliff/mcp-nextcloud?variant=verified)](https://m8ven.ai/mcp/hithereiamaliff/mcp-nextcloud)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 05be513a6579fe46be07da7f1a3630cdfc8dffb1
code hash: e4f294c234f76b22b46cfe11a9e08b8ab43a2f03d1caea1e812dccadcdac10ce
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