DrBaher/supstack-cli (DrBaher/supstack-cli) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
22 days ago

DrBaher/supstack-cli

Evidence-based supplement intelligence in your terminal, exposed as an MCP server for AI agents to research, compare, stack, and manage supplements.

→ DrBaher/supstack-cli· listed on glama

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

⚡ 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

DrBaher

Source: Glama

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

Glama

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: SUPSTACK_API_KEY, SUPSTACK_NO_ANON_TOKEN, SUPSTACK_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.
configNO_UPDATE_NOTIFIERSUPSTACK_NO_UPDATE_CHECK — Disable the "update available" notice (also honours )
configSHELLsupstack completion install # detects bash zsh fish from $
🔐 secretSUPSTACK_API_KEYOptional API key (anonymous works at 60/min/IP)
configSUPSTACK_API_URL
configSUPSTACK_CACHE_TTL3600 Response cache TTL in seconds
configSUPSTACK_COMPLETE_TIMEOUT
configSUPSTACK_HOME~/.supstack Directory for config, stack, and cache
configSUPSTACK_INTEGRATION
🔐 secretSUPSTACK_NO_ANON_TOKENDisable auto-minting of the anonymous instant-token
configSUPSTACK_NO_CACHESet to disable the response cache
configSUPSTACK_NO_UPDATE_CHECKDisable the "update available" notice (also honours NO_UPDATE_NOTIFIER)
configSUPSTACK_TIMEOUT20 Per-request timeout in seconds (or use --timeout)
🔐 secretSUPSTACK_TOKENin (supstack login, or a ); without a token they return a clear
// 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

10/10 tools missing one or more hints — compare (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); define (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); export (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (src/auth.ts:64)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Domain consistency

npm scope @supstack doesn't match GitHub owner drbaher

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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/drbaher/supstack-cli)](https://m8ven.ai/mcp/drbaher/supstack-cli)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 03d5516f11f15a2ff76ef5b521cf945ec13c0c52
code hash: f3c16587db1dfea42ed62ba6411fbd9eb22a943398a39348c8efbeccb4c5fd88
verified: 8/19/2026, 5:21:05 AM
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