homelab-mcp (bjeans/homelab-mcp) is an MCP server listed on the M8ven Trust Index. It scores 36 out of 100, grade F. It declares 45 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
36/100

homelab-mcp

Model Context Protocol (MCP) servers for managing homelab infrastructure through Claude Desktop. Monitor Docker/Podman containers, Ollama AI models, Pi-hole DNS, Unifi networks, and Ansible inventory. Includes security checks, templates, and automated pre-push validation. Production-ready for homelabs.

→ bjeans/homelab-mcp· listed on pulsemcp

Warning. Serious findings were identified. Review the full report before connecting. 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

bjeans

Source: PulseMCP · also listed on github_code, ModelScope

Maintenance & responsiveness
as of 2026-08-15
Issues closed (90d): 0 · 19 open
Releases (90d): none — last 2026-01-15
Contributor retention: 2/3 stayed · 3 active
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

PulseMCPnot scored hereGitHubModelScopenot 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
✅
45 tools verified — handlers match their declared behaviour
39 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: NUT_PASSWORD, UNIFI_API_KEY
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.
configMCP_DIRECTORY
configMCP_UNIFIED_MODE
configANSIBLE_INVENTORY_PATH1. Set in your .env file
configNUT_PORT
configNUT_USERNAME
🔐 secretNUT_PASSWORD
configDOCKER_ANSIBLE_GROUP
configPODMAN_ANSIBLE_GROUP
configOLLAMA_PORT
configOLLAMA_INVENTORY_GROUP
configLITELLM_HOST
configLITELLM_PORT
configPIHOLE_ANSIBLE_GROUP
configUNIFI_HOST
🔐 secretUNIFI_API_KEY4. Update in .env file
// quality suggestions

Tool annotations

39/45 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

6/45 tools missing one or more hints — get_claude_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_mcp_servers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_mcp_directory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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 test coverage

Only 0/45 tools referenced in tests (0%)

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

Secrets never reach shell commands

1 secret value passed to shell commands — possible command injection

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Secrets not logged

2 secret values sent to logger.info/logger.warning

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 5 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/bjeans/homelab-mcp?variant=verified)](https://m8ven.ai/mcp/bjeans/homelab-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: ad9eddbab3caec85f0c808521dd392d5f1f6a3d5
code hash: 106146c7d0361bb68acd502c810b9e50126ee870c312777a5f343b09da67098b
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