yoru-studio-mcp (yoruuuchan/yoru-studio-oss) 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.

C
Emerging
74/100
16 days ago

yoru-studio-mcp

MCP server for Yoru Studio that lets AI agents read projects, schedules, and inbox, and safely append inspiration, storyboard shots, and execution records to a creator's self-hosted workspace.

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

yoruuuchan

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 →

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 2 credentials: CLOUDFLARE_API_TOKEN, STUDIO_SESSION_SECRET
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.
configSTUDIO_PRODUCTION_COMMIT
🔐 secretCLOUDFLARE_API_TOKEN
configSTUDIO_MCP_OAUTH_ISSUER_URLPublic URL that hosts the OAuth AS metadata; setting it wakes the OAuth path (unset)
configSTUDIO_MCP_OAUTH_CODE_TTL_SECONDSOAuth authorization-code lifetime 300
configSTUDIO_CONFIGMost values live in environment variables (production is Docker-friendly that way). A subset can also live in a TOML file loaded by --config or — see config/config.example.toml for the shape.
configSTUDIO_DATA_DIRWhere the SQLite database lives ./data
configSTUDIO_UPLOADS_DIRWhere uploaded attachments live <data-dir>/uploads
🔐 secretSTUDIO_SESSION_SECRETa random string, at least 32 characters.
configSTUDIO_AUTH_PASSWORD_HASHuv run studio hash-password # interactively hash a password for
configSTUDIO_RADAR_TOKEN_HASHsha256 hex of the intake channel's bearer token; unset disables the intake endpoint (unset)
configSTUDIO_MCP_TOKEN_HASHsha256 hex of the MCP static-bearer token; unset disables the static-Bearer path (unset)
// 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

8/8 tools missing one or more hints — list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_sub_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +5 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.

Secrets not written to files

1 secret value written to files

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

Secrets not logged

1 secret value sent to console.log

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 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/yoruuuchan-yoru-studio-oss-1oz4ov)](https://m8ven.ai/mcp/yoruuuchan-yoru-studio-oss-1oz4ov)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 77f6312b67795574d0e1f9122db8232291f82d0c
code hash: 59e1ffacb06d2fab73b6bf7f33eb7393d30dd3ae5433f958e0acdbeccd8df747
verified: 8/14/2026, 9:51:30 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