F
Warning
3/100
12 days ago

work-tools

Local MCP tools for work: Outlook, Harvest, and AI-powered daily planning

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

DIGI-UW

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
⚠️
Tool descriptions don’t match what handlers do
8 tools describe read intent but their handlers mutate — harvest_list_projects (line 53: unlinkSync(TOKEN_FILE)); harvest_list_tasks (line 53: unlinkSync(TOKEN_FILE)); harvest_list_time_entries (line 53: unlinkSync(TOKEN_FILE))
⚠️
Known vulnerabilities in dependencies: 4 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.
🔐
You'll be asked for 3 credentials: HARVEST_ACCESS_TOKEN, JIRA_API_TOKEN, JIRA_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 high

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

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

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highplaywright@1.52.0GHSA-7mvr-c777-76hp

Playwright downloads and installs browsers without verifying the authenticity of the SSL certificate

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.
🔐 secretHARVEST_ACCESS_TOKEN
configHARVEST_ACCOUNT_ID
🔐 secretJIRA_API_TOKEN
configJIRA_BASE_URL
configJIRA_EMAIL
🔐 secretJIRA_TOKEN
configOUTLOOK_TIMEZONE
configWORK_MCP_PROFILE
// quality suggestions

Dependencies

6 dependencies, 1 flagged: playwright

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

22/22 tools missing one or more hints — warmup (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); harvest_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); harvest_refresh (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +19 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.

Destructive tools are labelled

8 tools perform destructive updates without destructiveHint — harvest_list_projects deletes at line 53 (unlinkSync(TOKEN_FILE)); harvest_list_tasks deletes at line 53 (unlinkSync(TOKEN_FILE)); harvest_list_time_entries deletes at line 53 (unlinkSync(TOKEN_FILE))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

8 tools describe read intent but their handlers mutate — harvest_list_projects (line 53: unlinkSync(TOKEN_FILE)); harvest_list_tasks (line 53: unlinkSync(TOKEN_FILE)); harvest_list_time_entries (line 53: unlinkSync(TOKEN_FILE))

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

Tool inputs are validated

14/22 tool handlers declare input schemas (64%)

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

Tool handlers catch errors

12/22 tool handlers wrap calls in try/catch (55%)

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

README present

No README found

Add a README.md describing the server and its tools.

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.

Production dependencies are patched

0 critical, 4 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)

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

Domain consistency

npm scope @work-tools doesn't match GitHub owner digi-uw

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Tool description accuracy

8 tools have description/behavior mismatches: harvest_list_projects: description implies read-only but handler writes/deletes/executes; harvest_list_tasks: description implies read-only but handler writes/deletes/executes; harvest_list_time_entries: 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 12 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/digi-uw-work-tools-f9r6zs?variant=verified)](https://m8ven.ai/mcp/digi-uw-work-tools-f9r6zs)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 89fe54262c246c00f32cb0d32becc1682889f1fd
code hash: a4ac3d12c603f03c151f8ec52ff03ab04d41a1fd8c0c8b85002bb66f8fbdfd43
verified: 8/8/2026, 7:12:02 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