owui-mcp-spawner (torfeu/owui-mcp-spawner) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

C
Emerging
74/100
7 days ago

owui-mcp-spawner

Spawn OpenWebUI-compatible tool JSONs as isolated Model Context Protocol (MCP) servers — each in its own virtualenv. Upload or write a tool, dependencies install automatically, and it's served over Streamable HTTP for OpenWebUI, Claude Code, or any MCP client.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

torfeu

Source: github_code

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
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 3 credentials: MCP_BEARER_TOKEN, MCP_MANAGER_PASSWORD, MCP_USER_JWT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
🔐 secretMCP_BEARER_TOKENBearer token for MCP endpoints when starting runner/server components directly. With app/manager.py, use --mcp-token or the Settings page.
configMCP_RUNNER_HOST
configMCP_MANAGER_PASSWORD_HASHPre-hashed SHA-256 hex digest (takes precedence)
🔐 secretMCP_MANAGER_PASSWORDSecurity note: Never bind to 0.0.0.0 without setting .
configMCP_EDIT_MODE
configMCP_NO_TOKEN_EDIT
🔐 secretMCP_USER_JWT_SECRETShared secret. Unset = no identity is ever verified.
configMCP_USER_TRUST_HEADERSAccept OpenWebUI's plain user headers when no token is sent (see below).
configMCP_EDIT_MODE_LOCKED
configMCP_USER_JWT_HEADERHeader carrying the token.
configMCP_USER_JWT_ISSUERRequired iss claim.
configMCP_MANAGER_PORT
configMCP_IDENTITY_POLICYAccess-rule file.
// 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

2/2 tools missing one or more hints — handle_call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_166 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

1/2 tools referenced in tests (50%)

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

Secrets not logged

1 secret value sent to print

Redact or omit secret values from log output.

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 4 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 Score](https://m8ven.ai/badge/mcp/torfeu/owui-mcp-spawner)](https://m8ven.ai/mcp/torfeu/owui-mcp-spawner)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: ed24eeb709e5fad3f2e544efb7e0a8384cdd0522
code hash: 1d1d018d2ff24c3bd3e2729d043dc23476cbdae1bd87f3438ff1e914b22d9bf8
verified: 9/3/2026, 7:35:53 PM
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