openquok-monorepo (Ratimon/openquok-monorepo) is an MCP server listed on the M8ven Trust Index. It scores 48 out of 100, grade D. It declares 20 tools. No publisher has claimed this listing.

D
Caution
48/100

openquok-monorepo

An agentic social media scheduling workspace engine/tool (CLI + Dashboard)

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

Ratimon

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
⚠️
Known vulnerabilities in dependencies: 7 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
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: PUBLIC_SUPABASE_PUBLISHABLE_KEY, SUPABASE_SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes20 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

analyticsPlatform

Platform-level metrics for a connected channel. days must be 7, 30, or 90.

analyticsPost

Per-post metrics for a published post row. days must be 7, 30, or 90. Empty for drafts.

groupList

List channel groups (customers) for the authenticated workspace. Use a group id with integrationList to filter channels.

integrationList

List connected social media channels for the authenticated workspace. Optionally filter by channel group id from groupList.

integrationSchema

Return posting rules, character limits, compose settings schema, and allow-listed tools for a platform (provider identifier, e.g. threads, facebook).

plugsActivate

Enable or disable a saved global plug rule.

plugsCatalog

List global plug types and field names per provider (like-threshold auto-reply/repost rules).

plugsDelete

Delete a saved global plug rule.

plugsList

List saved global plug rules on a connected channel.

plugsUpsert

Create or update a global plug rule on a connected channel (func + fields).

postsConnect

Link a post row to a provider release_id for per-post analytics.

postsDelete

Delete a post row by id.

postsFindSlot

Suggest a free schedule slot for the workspace or a specific connected channel.

postsList

List posts in a date window for the workspace (optional integration ids or channel group). Default window matches the public list API.

postsMissing

List provider candidates when a published post is missing release_id (needed before per-post analytics).

postsReviewTodo

Set or update the review-todo note on a post row.

postsStatus

Flip a post row between draft and scheduled at the stored publish time.

schedulePostTool
triggerTool

Invoke an allow-listed provider method on a connected channel (same as POST /public/integration-trigger/:id).

uploadFromUrl

Fetch a public HTTPS image or video URL into workspace media and return id and path for schedulePostTool.

// known CVEs in dependencies7 high12 low

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

highmulter@2.1.1GHSA-535w-7cp7-47q4

multer vulnerable to Denial of Service via oversized array index in field names

highmulter@2.1.1GHSA-72gw-mp4g-v24j

Multer vulnerable to Denial of Service via deeply nested field names

highmulter@2.1.1GHSA-wc9g-mqfw-jrwm

multer vulnerable to Denial of Service via crafted multipart field names

highnodemailer@8.0.1GHSA-2x7j-588g-ccc2

Nodemailer: Quadratic (O(n²)) time complexity in addressparser allows remote denial of service via a crafted address list

highnodemailer@8.0.1GHSA-p6gq-j5cr-w38f

Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message

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.
configAPI_PREFIX
configAUTH_RATE_LIMIT_MAX
configAUTH_RATE_LIMIT_WINDOW_MS
configAWS_EXECUTION_ENV
configAWS_LAMBDA_FUNCTION_NAME
configBULL_BOARD_ENABLED
configBULL_BOARD_SESSION_MAX_AGE_SEC
configCACHE_ENABLED
configCACHE_PROVIDER
configDOTENV_OVERRIDE
configFEEDBACK_RATE_LIMIT_MAX
configFEEDBACK_RATE_LIMIT_WINDOW_MS
configINTEGRATION_CONNECT_RATE_LIMIT_MAX
configINTEGRATION_CONNECT_RATE_LIMIT_WINDOW_MS
configJEST_WORKER_ID
configMCP_ENABLED
configMCP_RATE_LIMIT_MAX
configMCP_RATE_LIMIT_WINDOW_MS
configOAUTH_TOKEN_RATE_LIMIT_MAX
configOAUTH_TOKEN_RATE_LIMIT_WINDOW_MS
configOPENQUOK_JEST_HARNESS
configPUBLIC_API_RATE_LIMIT_MAX
configPUBLIC_API_RATE_LIMIT_WINDOW_MS
🔐 secretPUBLIC_SUPABASE_PUBLISHABLE_KEY
configPUBLIC_WRITE_RATE_LIMIT_MAX
configPUBLIC_WRITE_RATE_LIMIT_WINDOW_MS
configRATE_LIMIT_ENABLED
configRATE_LIMIT_MAX
configRATE_LIMIT_WINDOW_MS
🔐 secretSUPABASE_SECRET_KEY
configUPLOAD_RATE_LIMIT_MAX
configUPLOAD_RATE_LIMIT_WINDOW_MS
configVERCEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deploySENTRY_DSN
deploySENTRY_ENABLED
// 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

20/20 tools missing one or more hints — analyticsPlatform (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyticsPost (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); groupList (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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 inputs are validated

18/20 tool handlers declare input schemas (90%)

Declare an inputSchema with zod/joi/yup on every tool definition.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Production dependencies are patched

0 critical, 6 high severity in production deps — multer@2.1.1 (high), multer@2.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.

Dependency freshness

2/41 production deps stale: twitter-text@2022-06-28 (4.2y), swagger-ui-express@2024-05-31 (2.3y)

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 Verified](https://m8ven.ai/badge/mcp/ratimon/openquok-monorepo?variant=verified)](https://m8ven.ai/mcp/ratimon/openquok-monorepo)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 3408e04a1170139188718885543f8507db4c0096
code hash: 9c62eff8911eba4495584d87e843094c624d21abea0aa097b93d46ee388c4cd7
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