meistertracker (meisterpilze/meistertracker) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 50 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

meistertracker

Self-hosted lab management for specialty mushroom cultivation — barcode scanning, batch / culture / harvest tracking, label printing, CalDAV sync, MCP integration. Built at meisterpilze.de.

→ meisterpilze/meistertracker· listed on github_repo_search

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

meisterpilze

Source: github_repo_search

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

GitHub

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
🚨
Code appears obfuscated
3 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 2 credentials: GITHUB_WEBHOOK_SECRET, PRINT_BRIDGE_TOKEN
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.
🔐 secretGITHUB_WEBHOOK_SECRET
configHOST
configHTTP_REDIRECT_PORT
configLABEL_HEIGHT_DOTS
configLABEL_WIDTH_DOTS
configLOG_ACCESS
configLOG_FORMAT
configMT_DB_FILE
configMT_RATE_MAX
configPHOTO_DIR_MAX_GB
configPM2_PROCESS_NAME
configPRINTER_NAME
🔐 secretPRINT_BRIDGE_TOKEN
configPRINT_BRIDGE_URL
configPUBLIC_BASE_URL
configPUBLIC_HOSTNAME
configTRUST_PROXY
configWORKTREE_MODE
configMEISTERTRACKER_DB
configCAM1_RTSP
configCAM2_RTSP
configYOLO_MODEL
configYOLO_CONF_THRESHOLD
configPX_PER_MM
configHARVEST_GROWTH_THRESHOLD_PCT
configHARVEST_STALL_READINGS
configPIN_MAX_AREA_RATIO
configQR_ASSIGN_RADIUS_PX
configFRAME_SAVE_DIR
configINCUBATION_BAG_RADIUS_PX
configCOLONISATION_SCORE_THRESHOLD
configCOLONISATION_MIN_FRACTION
configUNSEEN_BAG_ALERT_HOURS
configCONTAM_MODEL
configCONTAM_CONF_THRESHOLD
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

50/50 tools missing one or more hints — daily_briefing (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_batches (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_batch_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +47 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 inputs are validated

49/50 tool handlers declare input schemas (98%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool test coverage

Only 9/50 tools referenced in tests (18%)

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

3 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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/meisterpilze/meistertracker?variant=verified)](https://m8ven.ai/mcp/meisterpilze/meistertracker)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 257b981ebf7dd290d4b621b1bab15107d3608666
code hash: 2fe1aeea43eb26da6ac0e459aed3d1e11dedcb3119526452ffe72ad5d79d31af
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