blog-writer_mcp (Divine-myositistrichinosa310/blog-writer_mcp) 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.

C
Emerging
74/100

blog-writer_mcp

Automate blog writing with an MCP server that helps AI turn your ideas into clear, personal posts

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

Divine-myositistrichinosa310

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 →

Install from

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
🚨
Secret credentials may flow to a network call
15 flows detected: TELEGRAM_BOT_TOKEN, OPENAI_API_KEY, IMGBB_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 20 credentials: TELEGRAM_BOT_TOKEN, OPENAI_API_KEY, COUPANG_ACCESS_KEY, COUPANG_SECRET_KEY, ANTHROPIC_API_KEY, WP_APP_PASSWORD, GOOGLE_TTS_API_KEY, KLING_API_KEY, IMGBB_API_KEY, INSTAGRAM_ACCESS_TOKEN, TIKTOK_ACCESS_TOKEN, X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_SECRET, SEEDANCE_API_KEY, ELEVENLABS_API_KEY, TYPECAST_API_KEY, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_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.
configGOOGLE_SEARCH_CONSOLE_SITE
configBLOG_SITE_URL
🔐 secretTELEGRAM_BOT_TOKEN
configTELEGRAM_CHAT_ID
configBLOG_MAIN_ID
configFFMPEG_PATH
🔐 secretOPENAI_API_KEY
configIMAGE_MODE
🔐 secretCOUPANG_ACCESS_KEY
🔐 secretCOUPANG_SECRET_KEY
configREMOTE_CLAUDE_POLLING_ENABLED
🔐 secretANTHROPIC_API_KEY
configWP_URL
configWP_USERNAME
🔐 secretWP_APP_PASSWORD
configFFPROBE_PATH
🔐 secretGOOGLE_TTS_API_KEY
🔐 secretKLING_API_KEY
🔐 secretIMGBB_API_KEY
configLOCAL_IMAGE_SERVER
configVIDEO_HOST_BASE_URL
🔐 secretINSTAGRAM_ACCESS_TOKEN
configINSTAGRAM_ACCOUNT_ID
🔐 secretTIKTOK_ACCESS_TOKEN
configTIKTOK_OPEN_ID
🔐 secretX_API_KEY
🔐 secretX_API_SECRET
🔐 secretX_ACCESS_TOKEN
🔐 secretX_ACCESS_SECRET
configYOUTUBE_CHANNEL_ID
🔐 secretSEEDANCE_API_KEY
🔐 secretELEVENLABS_API_KEY
🔐 secretTYPECAST_API_KEY
configTYPECAST_BASE_URL
configSORAWM_PATH
configSORAWM_MODEL
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
🔐 secretGOOGLE_REFRESH_TOKEN
// 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 — blog_get_trending (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); blog_write_article (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); blog_generate_image (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.

License file

No license file

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

Secrets not written to files

5 secret values written to files

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

Secrets not logged

8 secret values sent to logger.info/logger.error/logger.debug

Redact or omit secret values from log output.

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 5 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/divine-myositistrichinosa310/blog-writer_mcp)](https://m8ven.ai/mcp/divine-myositistrichinosa310/blog-writer_mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bd855e4a63c9353a572c6a7193f7cdb70abd11b3
code hash: 6101eec9acb12fd5576a8e6c0105ecb543ee23fd23ea630defcca9f1c4e4b797
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