cowork (slashman413/cowork) is an MCP server listed on the M8ven Trust Index. It scores 73 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

C
Warning
73/100

cowork

Multi-Agent Cowork MCP Server — cross-platform AI agent coordination with Web UI Dashboard. Ships as Cowork Pro on Gumroad.

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

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

slashman413

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
🚨
Secret credentials may flow to a network call
1 flow detected: AGY_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 5 credentials: AGY_ACCESS_TOKEN, AGY_CLIENT_SECRET, AGY_REFRESH_TOKEN, COWORK_API_KEY, POSTGRES_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools · 4 behind config

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.

register_agent
deregister_agent
heartbeat
get_roster
create_task
claim_task
complete_task
list_inbox
get_dashboard
obsidian_info
obsidian_search
obsidian_read
obsidian_list
create_goalbehind config
list_goalsbehind config

List all Goals (newest first) with status, phases and audit history.

get_goalbehind config

Fetch one Goal by id (phases, decision history, meeting-minutes pointers).

update_goal_progressbehind config
// 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.
🔐 secretAGY_ACCESS_TOKEN
configAGY_CLIENT_ID
🔐 secretAGY_CLIENT_SECRET
🔐 secretAGY_REFRESH_TOKEN
configAGY_TOKEN_FILE
🔐 secretCOWORK_API_KEY
configCOWORK_CONFIG
configCOWORK_PORT
configCOWORK_ROSTER_TTL_MS
configPOSTGRES_DB
configPOSTGRES_HOST
🔐 secretPOSTGRES_PASSWORD
configPOSTGRES_PORT
configPOSTGRES_USER
// 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 — register_agent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); deregister_agent (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); heartbeat (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.

Tool test coverage

Only 3/17 tools referenced in tests (18%)

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

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (AGY_ACCESS_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

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

Dependency freshness

1/8 production deps stale: gray-matter@2023-07-12 (3.2y)

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 5 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/slashman413/cowork?variant=verified)](https://m8ven.ai/mcp/slashman413/cowork)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b6b8e48ca5863bb0e56bbf8e2de7256acfef1ca7
code hash: 31cdc9a8423d7b1224878c1bc1ec4a02585d0ae038d5c7a6a0b630cf63defbf8
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