C
Emerging
74/100
8 days ago

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

Sakenfor

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 1 credential: PIXSIM_API_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 low

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

lowesbuild@0.24.0GHSA-67mh-4wv8-2f99

esbuild enables any website to send any requests to the development server and read the response

lowyaml@2.8.0GHSA-48c2-rrv3-qjmp

yaml is vulnerable to Stack Overflow via deeply nested YAML collections

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configPIXSIM_DETECTION_MODEL_ID
configPIXSIM_DETECTION_MAX_CONCURRENCY
configPIXSIM_EMBEDDING_WEDGE_SEC
configPIXSIM_EMBEDDING_MODEL_ID
configPIXSIM_EMBEDDING_MODEL_IDS
configPIXSIM_EMBEDDING_MAX_RESIDENT
configPIXSIM_EMBEDDING_MAX_CONCURRENCY
configPIXSIM_API_URL
🔐 secretPIXSIM_API_TOKEN
configPIXSIM_TOKEN_FILE
configPIXSIM_SCOPE
configPIXSIM_MCP_APPROVAL_TOOLS
configPIXSIM_HOOK_PORT
configPIXSIM_MCP_GROUPED
configCODEX_CLI
configPIXSIM_BRIDGE_MANAGED
configGENERATION_API_PORT
configPIXSIM_WEBVIEW_ARGS
configLOG_LEVEL
configPIXSIM_DATABASE_URL
configPIXSIM_HOME
configPG_DUMP_PATH
configPGPASSWORD
configPIXSIM_TEXT_EMBEDDING_WEDGE_SEC
configPIXSIM_TEST_SUBMIT
configPIXSIM_LOG_LEVEL
configPIXSIM_ENV
configPIXSIM_LOG_FORMAT
configPIXSIM_LOG_DB_URL
configLOG_DATABASE_URL
configPIXSIM_LOG_INGESTION_URL
configPIXSIM_LOG_ENABLE_HTTP
configPIXSIM_LOG_EXCLUDE_PATHS
configPIXSIM_LOG_SAMPLE_PATHS
configPIXSIM_LOG_SAMPLING_PROVIDER_STATUS
configPIXSIM_LOG_DB_AUTO_CREATE
configPIXSIM_SERVICE_NAME
configPIXSIM_SERVICE
configSERVICE_NAME
configPIXSIM_LOG_ALLOW_PYTEST
configPYTEST_CURRENT_TEST
configPIXSIM_LOG_DB_TABLE
configPIXSIM_LOG_DB_BATCH_SIZE
configPIXSIM_LOG_DB_FLUSH_INTERVAL
configPIXSIM_DEMO_SERVICE
configPIXSIM_LOG_DOMAINS
configPIXSIM_LOG_INGESTION_BATCH_SIZE
configPIXSIM_LOG_INGESTION_FLUSH_INTERVAL
configGITHUB_EVENT_PATH
configGITHUB_BASE_REF
configGITHUB_EVENT_BEFORE
configLAUNCHER_PORT
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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 — handle_call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_539 (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); dynamic_tool_587 (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.

Tool test coverage

6/10 tools referenced in tests (60%)

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

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (data/launcher/db_browser_widget.py:252)

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

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Domain consistency

npm scope @pixsim7 doesn't match GitHub owner sakenfor

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 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 Score](https://m8ven.ai/badge/mcp/sakenfor-pixsim7-crt42e)](https://m8ven.ai/mcp/sakenfor-pixsim7-crt42e)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2a7df4d504791794468194ed97d21738ba59338d
code hash: 989a0f7ccfd4fedac5e1f5459bb92a67d76be62412b589b55aa3c4131cc6dcb1
verified: 8/13/2026, 7:57:18 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