StyleMCP (distinctlydeveloped/stylemcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
D
Caution
54/100
10 days ago

StyleMCP

Brand rules for AI outputs. Validate and rewrite text to match your brand voice.

→ distinctlydeveloped/stylemcp· listed on pulsemcp

Caution. Specific findings reduced this grade. They are listed on the page. 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

distinctlydeveloped

Source: PulseMCP · also 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. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

PulseMCPGlama

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

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: STYLEMCP_API_KEY, TELEGRAM_BOT_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 3 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 7 credentials: ANTHROPIC_API_KEY, GITHUB_WEBHOOK_SECRET, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STYLEMCP_API_KEY, SUPABASE_SERVICE_KEY, TELEGRAM_BOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical3 high1 low

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

criticalvitest@1.6.1GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

highjs-yaml@4.1.1GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@4.1.1GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

highexpress-rate-limit@8.2.1GHSA-46wh-pxpv-q5gq

express-rate-limit: IPv4-mapped IPv6 addresses bypass per-client rate limiting on servers with dual-stack network

lowjs-yaml@4.1.1GHSA-h67p-54hq-rp68

JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases

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.
configALLOWED_ORIGINS
🔐 secretANTHROPIC_API_KEY
configAPI_RATE_LIMIT
configDD_ERRORS_PATH
🔐 secretGITHUB_WEBHOOK_SECRETGitHub webhook secret (none)
configLEGACY_RATE_LIMIT_PER_MINUTE
configMAX_BATCH_ITEMS
configMAX_CONTEXT_LENGTH
configMAX_PACK_NAME_LENGTH
configMAX_SAMPLES_PER_REQUEST
configMAX_TEXT_CHARS
configMAX_TEXT_LENGTH
configPACK_OVERWRITE_TIERS
configPACK_WRITE_TIERS
configRATE_LIMIT_BUSINESS_PER_MINUTE
configRATE_LIMIT_ENTERPRISE_PER_MINUTE
configRATE_LIMIT_FREE_PER_MINUTE
configRATE_LIMIT_PRO_PER_MINUTE
configRATE_LIMIT_TEAM_PER_MINUTE
configRATE_LIMIT_WINDOW_MS
🔐 secretSTRIPE_SECRET_KEY
🔐 secretSTRIPE_WEBHOOK_SECRET
🔐 secretSTYLEMCP_API_KEYecho "=$(openssl rand -hex 32)" > .env
configSTYLEMCP_TELEGRAM_CHAT
🔐 secretSUPABASE_SERVICE_KEY
configSUPABASE_URL
configTELEGRAM_ALERT_CHAT
🔐 secretTELEGRAM_BOT_TOKEN
configTRUST_PROXY
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Dependencies

23 dependencies, 1 flagged: puppeteer

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

9/9 tools missing one or more hints — validate_text (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rewrite_to_style (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_voice_rules (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

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

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

Secrets not logged

10 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — js-yaml@4.1.1 (high), js-yaml@4.1.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 7 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/distinctlydeveloped-stylemcp-0qa83u?variant=verified)](https://m8ven.ai/mcp/distinctlydeveloped-stylemcp-0qa83u)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: fb5ea98cf4ffea9c68e82b8a1ed4cc14d2849511
code hash: 7a0bb50b6d9d044ac5a2474ecf4ca9570e07178e09dfd04d2a93f2272c9fd060
verified: 8/17/2026, 3:47:33 PM
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