F
Warning
34/100
11 days ago

ossaihub-cron

Daily GitHub stars refresh for OSS AI Hub

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

chadcorp

Source: github_code

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
6 flows detected: API_KEY, GH_READONLY_TOKEN, BASE44_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — calculator (line 70: return str(eval(expression, {"__builtins__": {}})) # noqa: S307 -- sandboxed)
🔐
You'll be asked for 27 credentials: MCP_TOKEN, ANTHROPIC_API_KEY, OPENAI_API_KEY, TAVILY_API_KEY, E2B_API_KEY, GITHUB_TOKEN, HF_TOKEN, COHERE_API_KEY, VOYAGE_API_KEY, GROQ_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, MISTRAL_API_KEY, OPENROUTER_API_KEY, MEM0_API_KEY, NEO4J_PASSWORD, TRACELOOP_API_KEY, DD_API_KEY, HONEYCOMB_KEY, HELICONE_API_KEY, YOUR_LLM_KEY, PINECONE_API_KEY, QDRANT_API_KEY, TURBOPUFFER_API_KEY, API_KEY, TOOLS_UPSERT_API_KEY, CLAUDE_CODE_OAUTH_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.
🔐 secretMCP_TOKEN
configMCP_STDIO_CMD
configMODEL
🔐 secretANTHROPIC_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretTAVILY_API_KEY
🔐 secretE2B_API_KEY
🔐 secretGITHUB_TOKENGH_READONLY_TOKEN github.com/settings/tokens → fine-grained token, public-repo read, 90-day expiry. (Or use the auto-provided secrets..) refresh-stars
configGITHUB_REPOSITORY
configPR_NUMBER
configDUCKDB_PATH
configANTHROPIC_MODEL
configBATCH_SIZE
configKAFKA_BOOTSTRAP
configKAFKA_GROUP_ID
configKAFKA_IN_TOPIC
configKAFKA_OUT_TOPIC
configKAFKA_DLQ_TOPIC
configVALID_TOKENS
🔐 secretHF_TOKEN
configCLOUD_RUN_URL
🔐 secretCOHERE_API_KEY
🔐 secretVOYAGE_API_KEY
configLLM_STUB
🔐 secretGROQ_API_KEY
🔐 secretGEMINI_API_KEY
🔐 secretGOOGLE_API_KEY
configAWS_REGION
🔐 secretMISTRAL_API_KEY
🔐 secretOPENROUTER_API_KEY
🔐 secretMEM0_API_KEY
configLETTA_BASE_URL
configLETTA_MODEL
configLETTA_EMBED
configMEMORY_DB
configMEMORY_HALFLIFE_HOURS
configNEO4J_URI
configNEO4J_USER
🔐 secretNEO4J_PASSWORD
configSCENE_THRESHOLD
🔐 secretTRACELOOP_API_KEY
🔐 secretDD_API_KEY
🔐 secretHONEYCOMB_KEY
🔐 secretHELICONE_API_KEY
🔐 secretYOUR_LLM_KEY
configTRACELOOP_BASE_URL
configQDRANT_URL
configFAIL_OPEN
configENV
configCANARY_ALERT_WEBHOOK
configCANARY_LOG
🔐 secretPINECONE_API_KEY
🔐 secretQDRANT_API_KEY
🔐 secretTURBOPUFFER_API_KEY
configMARQO_URL
configCHUNK
configINTER_BATCH_MS
configDRY_RUN
configUPSERT_URL
🔐 secretAPI_KEY
🔐 secretTOOLS_UPSERT_API_KEYThe random string you pasted into the Base44 secret field refresh-stars, enrich-descriptions, glossary-v2-push
configMAX_RETRIES
🔐 secretCLAUDE_CODE_OAUTH_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployREDIS_URL
deployPOSTGRES_URL
// 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

17/17 tools missing one or more hints — now_utc (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_text_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); append_to_log (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — calculator (line 70: return str(eval(expression, {"__builtins__": {}})) # noqa: S307 -- sandboxed)

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

15/17 tool handlers declare input schemas (88%)

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

Tool handlers catch errors

Only 4/17 tool handlers wrap calls in try/catch (24%)

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

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

16 child_process calls — runs shell commands

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

Secrets stay with their owner

3 secret/sensitive values flow into network calls (API_KEY → dynamic, API_KEY → dynamic) (3 other flows matched canonical API hosts)

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

9 secret values sent to console.log

Redact or omit secret values from log output.

Tool description accuracy

calculator: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 11 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/chadcorp-ossaihub-cron-11buhd?variant=verified)](https://m8ven.ai/mcp/chadcorp-ossaihub-cron-11buhd)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 4c9a94a28ceeed410bf1ed50889b592105f6480f
code hash: 59ade4189b48cf67b9a6851005e2a418e8210f1eb294ac4444177e3f899547a3
verified: 8/8/2026, 8:33:57 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