C
Caution
74/100
12 days ago

seenpaid

Enables AI agents to schedule and manage social media posts across 25 platforms via a simple 3-tool MCP interface, including listing connected accounts and recent posts.

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

justinasrolando-cpu

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
🚨
Secret credentials may flow to a network call
16 flows detected: MASTODON_CLIENT_SECRET, META_APP_SECRET, PINTEREST_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 17 credentials: API_KEY, LINKEDIN_CLIENT_SECRET, MASTODON_CLIENT_SECRET, META_APP_SECRET, PINTEREST_CLIENT_SECRET, R2_SECRET_ACCESS_KEY, REDDIT_CLIENT_SECRET, REDIS_PASSWORD, RESEND_API_KEY, S3_SECRET_ACCESS_KEY, THREADS_CLIENT_SECRET, TIKTOK_CLIENT_KEY, TIKTOK_CLIENT_SECRET, TOKEN_ENCRYPTION_KEY, TUMBLR_CLIENT_SECRET, VK_CLIENT_SECRET, X_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 high

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

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

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

criticalvitest@2.1.8GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highdrizzle-orm@0.38.0GHSA-gpj5-g38j-94v9

Drizzle ORM has SQL injection via improperly escaped SQL identifiers

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
🔐 secretAPI_KEYfill in and TOKEN_ENCRYPTION_KEY (openssl rand -hex 32 for each)
configAPP_URL
configLINKEDIN_CLIENT_ID
🔐 secretLINKEDIN_CLIENT_SECRET
configLOG_LEVEL
configMASTODON_CLIENT_ID
🔐 secretMASTODON_CLIENT_SECRET
configMASTODON_INSTANCE_URL
configMETA_APP_ID
🔐 secretMETA_APP_SECRET
configNOSTR_RELAYS
configOWNER_EMAIL
configPINTEREST_CLIENT_ID
🔐 secretPINTEREST_CLIENT_SECRET
configR2_ACCESS_KEY_ID
configR2_ACCOUNT_ID
configR2_BUCKET
configR2_PUBLIC_BASE_URL
🔐 secretR2_SECRET_ACCESS_KEY
configREDDIT_CLIENT_ID
🔐 secretREDDIT_CLIENT_SECRET
configREDIS_HOST
🔐 secretREDIS_PASSWORD
configREDIS_PORT
🔐 secretRESEND_API_KEY
configRESEND_FROM_EMAIL
configRUN_INLINE_WORKER
configS3_ACCESS_KEY_ID
configS3_BUCKET
configS3_ENDPOINT
configS3_PUBLIC_BASE_URL
configS3_REGION
🔐 secretS3_SECRET_ACCESS_KEY
configTHREADS_CLIENT_ID
🔐 secretTHREADS_CLIENT_SECRET
🔐 secretTIKTOK_CLIENT_KEY
🔐 secretTIKTOK_CLIENT_SECRET
🔐 secretTOKEN_ENCRYPTION_KEYfill in API_KEY and (openssl rand -hex 32 for each)
configTRUST_PROXY
configTUMBLR_CLIENT_ID
🔐 secretTUMBLR_CLIENT_SECRET
configVK_CLIENT_ID
🔐 secretVK_CLIENT_SECRET
configX_CLIENT_ID
🔐 secretX_CLIENT_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// 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

3/3 tools missing one or more hints — list_accounts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_posts (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); schedule_post (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

2/3 tool handlers declare input schemas (67%)

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

Tool handlers catch errors

Only 0/3 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

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

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

Shell command execution

1 child_process call — runs shell commands

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

Production dependencies are patched

0 critical, 1 high severity in production deps — drizzle-orm@0.38.0 (high)

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

Dev dependencies

2 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 8 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/justinasrolando-cpu-seenpaid-1fiisd?variant=verified)](https://m8ven.ai/mcp/justinasrolando-cpu-seenpaid-1fiisd)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: a2840eb16842e4a4936f77ea3b90ed16d09ea64e
code hash: 83ae622a1baec5e424f33ee563db2cbbb79c067220c78be7cfab493124562947
verified: 8/7/2026, 7:46:06 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