Nextcloud (hithereiamaliff) MCP Server

mcp-nextcloud npm v1.0.0

Published by hithereiamaliff — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A Model Context Protocol (MCP) server for Nextcloud integration, providing 30+ tools for Notes, Calendar, Contacts, Tables, and WebDAV operations with advanced unified search capabilities

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Tool "nc_webdav_write_file" can modify the filesystemMTC-CAP-002

Tool "nc_webdav_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool nc_webdav_write_file

low Mutating tool "nc_webdav_write_file" declares no destructiveHintMTC-CAP-005

Tool "nc_webdav_write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool nc_webdav_write_file

Tools 28

Each tool and what it can reach — statically extracted from the published source.

  • nc_webdav_read_filereads sensitive data
  • nc_webdav_write_filewrites files
  • nc_calendar_create_eventno sensitive capability
  • nc_calendar_delete_eventno sensitive capability
  • nc_calendar_get_eventno sensitive capability
  • nc_calendar_list_calendarsno sensitive capability
  • nc_calendar_list_eventsno sensitive capability
  • nc_calendar_update_eventno sensitive capability
  • nc_contacts_create_addressbookno sensitive capability
  • nc_contacts_create_contactno sensitive capability
Show 18 more tools ↓
  • nc_contacts_delete_addressbookno sensitive capability
  • nc_contacts_delete_contactno sensitive capability
  • nc_contacts_list_addressbooksno sensitive capability
  • nc_contacts_list_contactsno sensitive capability
  • nc_notes_append_contentno sensitive capability
  • nc_notes_create_noteno sensitive capability
  • nc_notes_delete_noteno sensitive capability
  • nc_notes_search_notesno sensitive capability
  • nc_notes_update_noteno sensitive capability
  • nc_tables_delete_rowno sensitive capability
  • nc_tables_get_schemano sensitive capability
  • nc_tables_insert_rowno sensitive capability
  • nc_tables_list_tablesno sensitive capability
  • nc_tables_read_tableno sensitive capability
  • nc_tables_update_rowno sensitive capability
  • nc_webdav_create_directoryno sensitive capability
  • nc_webdav_delete_resourceno sensitive capability
  • nc_webdav_list_directoryno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 96/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-nextcloud/badge.svg)](https://mcptrustchecker.com/registry/mcp-nextcloud)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-nextcloud"><img src="https://mcptrustchecker.com/registry/mcp-nextcloud/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-nextcloud/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-nextcloud --online

Use the free API → How scoring works

Other implementations of Nextcloud 3

Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →

More in Web, Search & Scraping