Back to MCP Trust Indexm8ven
D
Caution
52/100
4 days ago

clockify-master-mcp

→ hongkongkiwi/clockify-master-mcp· listed on modelscope

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

hongkongkiwi

Source: modelscope

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 →

⚡ Connect GitHub for Live Monitored

Install from

modelscope

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 15 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 1 credential: CLOCKIFY_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical15 high5 medium10 low

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

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

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

high@modelcontextprotocol/sdk@1.17.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.17.3GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.17.3GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.11.0GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

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_PROJECTS"": "proj-123,proj-456",
configALLOWED_WORKSPACESworkspace-id
configALLOW_CLIENT_MANAGEMENTAllow client operations (default: true)
configALLOW_FUTURE_TIME_ENTRIESAllow future time entries (default: false)
configALLOW_PAST_TIME_ENTRIES_IN_DAYSDays back to allow time entries (default: 30)
configALLOW_PROJECT_MANAGEMENTAllow project operations (default: true)
configALLOW_TIME_ENTRY_CREATIONAllow creating time entries (default: true)
configALLOW_TIME_ENTRY_DELETIONAllow deleting time entries (default: true)
configALLOW_USER_MANAGEMENTAllow user operations (default: false)
configCACHE_ENABLEDEnable response caching (default: false)
configCACHE_TTLCache time-to-live in seconds
🔐 secretCLOCKIFY_API_KEY"": "your_api_key_here"
configCLOCKIFY_API_URLCustom API URL (overrides region setting)
configCLOCKIFY_REGIONAPI region (global, eu, us) - default: global
configDEFAULT_PROJECT_IDWhen you configure specific projects (using or ALLOWED_PROJECTS), the system automatically protects these projects from accidental damage:
configDEFAULT_WORKSPACE_IDyour-main-workspace-id
configDENIED_PROJECTS
configDISABLED_TOOLSbulk_edit_time_entries,delete_time_entry
configENABLED_TOOLS"": "get_current_user,create_time_entry,stop_timer,get_today_entries,get_summary_report",
configENABLED_TOOL_CATEGORIES"": "user,workspace,project,client,timeEntry,report",
configLOG_LEVELLogging level (debug, info, warn, error)
configMAX_TIME_ENTRY_DURATIONMaximum hours per time entry
configMAX_TOOLSMaximum number of tools to expose (default: unlimited)
configRATE_LIMITRequests per minute limit
configREAD_ONLY"": "false",
// 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

54/54 tools missing one or more hints — get_current_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +51 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.).

Tool test coverage

26/54 tools referenced in tests (48%)

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

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.17.3 (high), @modelcontextprotocol/sdk@1.17.3 (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.

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/hongkongkiwi-clockify-master-mcp-vp8wqd?variant=verified)](https://m8ven.ai/mcp/hongkongkiwi-clockify-master-mcp-vp8wqd)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: de0aea004f70581d00b057ea53db72d535c5e945
code hash: ae2f164a1dabe14d8bc64761c9c9ae6734dd652ca89c44bd9cafff2136c5cd6e
verified: 8/18/2026, 9:56:07 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