Back to MCP Trust Indexm8ven
37
/ 100
1 month ago
glama

Self-hosted MCP server for Claude

Give Claude direct access to your AWS account, SSH into your servers, run shell commands on your laptop, query your databases, and manage PM2 processes — all from a Claude chat. No Claude Code subscription needed. Your keys never leave your machine.

→ LeszczynskiKarol/mcp-server· listed on 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.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — pm2_status (line 385: client.exec(command, (err, s) => {)
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
🔐
You'll be asked for 2 credentials: GITHUB_TOKEN, MCP_PASS
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.0.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configAUTH_CODE_TTL_SECONDS— 600 # 10 minutes
configCLIENT_TTL_SECONDS— 7776000 # 90 days (unused-client cleanup)
configEXEC_BUFFER_MB
configEXEC_TIMEOUT_SECONDS— 120 # per-command timeout
configGITHUB_OWNER— YourGitHubUsername
🔐 secretGITHUB_TOKEN— github_pat_xxxxxxxxxxxxxxxx
configHOSTS_CONFIG— ./hosts.json
configMCP_ALLOWED_IPS— leave empty unless you have a fixed office/VPN IP
configMCP_AUTO_ENROLL— true # let Claude.ai's egress IP enroll itself on first login
configMCP_BASE_URL— cp .env.example .env # fill in MCP_PASS and
configMCP_ENROLL_TTL_SECONDS
configMCP_MAX_CLIENTS
🔐 secretMCP_PASS— cp .env.example .env # fill in and MCP_BASE_URL
configMCP_SERVER_NAME— my-mcp-server
configMCP_TEST_MODE
configMCP_TRUST_PROXY— loopback # frpc connects to node over 127.0.0.1
configMCP_USER— 4. Click Connect → a login form appears → enter and MCP_PASS from your .env
configOAUTH_STATE_FILE— ./oauth-state.json
configPORT
configSG_CHECK_TTL_MS
configSSH_IDLE_TIMEOUT_SECONDS
configSSH_KNOWN_HOSTS
configTOKEN_TTL_SECONDS— 2592000 # 30 days
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 10 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/leszczynskikarol-mcp-server-72rh1k)](https://m8ven.ai/mcp/leszczynskikarol-mcp-server-72rh1k)
commit: dd525c69a356b321e91588702c80cf0e30c3f11c
code hash: 1d57fac101509930088d28879142cf2ed6d9904df87e0144491326578fa5adc2
verified: 6/17/2026, 11:32:24 AM
view raw JSON →