Openwebui (PyPI) MCP Server

openwebui-mcp-server PyPI v0.2.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for managing Open WebUI - users, groups, models, knowledge bases, and more

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_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 delete_file

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

Tool "delete_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 delete_file

Tools 82

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

  • delete_filewrites files
  • list_filesreads sensitive data
  • add_memoryno sensitive capability
  • add_user_to_groupno sensitive capability
  • archive_chatno sensitive capability
  • clone_chatno sensitive capability
  • create_channelno sensitive capability
  • create_folderno sensitive capability
  • create_functionno sensitive capability
  • create_groupno sensitive capability
Show 72 more tools ↓
  • create_knowledge_baseno sensitive capability
  • create_modelno sensitive capability
  • create_noteno sensitive capability
  • create_promptno sensitive capability
  • create_toolno sensitive capability
  • delete_all_chatsno sensitive capability
  • delete_all_filesno sensitive capability
  • delete_all_memoriesno sensitive capability
  • delete_channelno sensitive capability
  • delete_channel_messageno sensitive capability
  • delete_chatno sensitive capability
  • delete_folderno sensitive capability
  • delete_functionno sensitive capability
  • delete_groupno sensitive capability
  • delete_knowledge_baseno sensitive capability
  • delete_memoryno sensitive capability
  • delete_modelno sensitive capability
  • delete_noteno sensitive capability
  • delete_promptno sensitive capability
  • delete_toolno sensitive capability
  • delete_userno sensitive capability
  • export_configno sensitive capability
  • get_bannersno sensitive capability
  • get_channelno sensitive capability
  • get_channel_messagesno sensitive capability
  • get_chatno sensitive capability
  • get_current_userno sensitive capability
  • get_fileno sensitive capability
  • get_file_contentno sensitive capability
  • get_folderno sensitive capability
  • get_functionno sensitive capability
  • get_groupno sensitive capability
  • get_knowledge_baseno sensitive capability
  • get_modelno sensitive capability
  • get_models_configno sensitive capability
  • get_noteno sensitive capability
  • get_promptno sensitive capability
  • get_system_configno sensitive capability
  • get_toolno sensitive capability
  • get_tool_serversno sensitive capability
  • get_userno sensitive capability
  • list_channelsno sensitive capability
  • list_chatsno sensitive capability
  • list_foldersno sensitive capability
  • list_functionsno sensitive capability
  • list_groupsno sensitive capability
  • list_knowledge_basesno sensitive capability
  • list_memoriesno sensitive capability
  • list_modelsno sensitive capability
  • list_notesno sensitive capability
  • list_promptsno sensitive capability
  • list_toolsno sensitive capability
  • list_usersno sensitive capability
  • post_channel_messageno sensitive capability
  • query_memoriesno sensitive capability
  • remove_user_from_groupno sensitive capability
  • reset_memoriesno sensitive capability
  • search_filesno sensitive capability
  • share_chatno sensitive capability
  • toggle_functionno sensitive capability
  • update_channelno sensitive capability
  • update_file_contentno sensitive capability
  • update_folderno sensitive capability
  • update_functionno sensitive capability
  • update_groupno sensitive capability
  • update_knowledge_baseno sensitive capability
  • update_memoryno sensitive capability
  • update_modelno sensitive capability
  • update_noteno sensitive capability
  • update_promptno sensitive capability
  • update_toolno sensitive capability
  • update_user_roleno 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
v0.2.0 latest A 95/100 2 1.13.0 2026-08-25

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/openwebui-mcp-server-2/badge.svg)](https://mcptrustchecker.com/registry/openwebui-mcp-server-2)
HTML
<a href="https://mcptrustchecker.com/registry/openwebui-mcp-server-2"><img src="https://mcptrustchecker.com/registry/openwebui-mcp-server-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/openwebui-mcp-server-2/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 openwebui-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Openwebui 1

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

More in Developer Tools