D
Caution
44/100
14 days ago

TeamMCP

TeamMCP is an MCP-native collaboration server that enables AI agents and humans to communicate through shared channels, direct messages, and integrated task management. It provides a persistent layer for real-time collaboration with full-text search and a centralized web dashboard.

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

cookjohn

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
7 flows detected: TEAMMCP_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: MEMORY_LLM_KEY, TEAMMCP_INTERNAL_SECRET, TEAMMCP_KEY, TEAMMCP_REGISTER_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 high1 low

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

highws@8.20.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

ws: Uninitialized memory disclosure

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.
configAGENTS_BASE_DIRYes — Root path for Agent working directories; start_agent/stop_agent depend on this
configAGENT_NAME"": "{agent_name}",
configAUTH_MONITOR_CANARY
configAUTH_MONITOR_FILE_CAP
configAUTH_MONITOR_SCAN_DEPTH
configCODEX_EXE
configCONTEXT_TOKEN_PATH
configCRED_PROBE_INTERVAL_MIN
configFALLBACK_FAILED_RECOVERY_MS
configGATE2_ENABLED
configMCP_HTTP_PORT
configMEMORY_ENGINE
configMEMORY_INTERNALIZE
🔐 secretMEMORY_LLM_KEY
configPREFLIGHT_DB_MAX_BYTES
configPROGRAMDATA
configPROGRAMFILES
configRETENTION_SWEEP
configRETRY_SIGNOFF
configSESSION_IDLE_MS
configSESSION_REVIEW_MAX
configSYSTEMROOT
configTEAMMCP_AGENTS_DIR
configTEAMMCP_AUTO_RESTARTAgents offline for more than 30 seconds can be auto-restarted (enable via =1, disabled by default). Intentionally stopped Agents do not trigger false alarms.
configTEAMMCP_BATCH_ENABLED
configTEAMMCP_BATCH_WINDOW_MS
configTEAMMCP_BIND_HOST
configTEAMMCP_CLAUDE_CMD
configTEAMMCP_CMD_ALLOWLIST_EXTRA
configTEAMMCP_DAEMON_DEV
configTEAMMCP_DEV
configTEAMMCP_ENV
configTEAMMCP_HOMEData → /home/teammcp/teammcp-data for the service
🔐 secretTEAMMCP_INTERNAL_SECRET
🔐 secretTEAMMCP_KEY"": "{agent_token}",
configTEAMMCP_NOW_TTL_MS
configTEAMMCP_PORTNo 3100 Server listening port
configTEAMMCP_PTY_DAEMON
🔐 secretTEAMMCP_REGISTER_SECRETRegistration Control: Optional registration secret ()
configTEAMMCP_URL"": "http://localhost:3100"
configTEAM_IDLE_WARN_HOURS
configWATCHDOG_DISABLED
configWECHAT_TOKEN_PATH
configWINDIR
// 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

146/146 tools missing one or more hints — send_message (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); send_dm (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_history (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +143 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 0/146 tools referenced in tests (0%)

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

Shell command execution

65 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

7 secret/sensitive values flow into network calls (TEAMMCP_KEY → dynamic, TEAMMCP_KEY → dynamic)

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

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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.

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/cookjohn-teammcp-1wdqyy?variant=verified)](https://m8ven.ai/mcp/cookjohn-teammcp-1wdqyy)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: c82572da10c290429fa53b7d2706ee4687b3fe6f
code hash: 441f7f82a280521a883ae569d8c90182b3aa108a06a671888abf55266845acfb
verified: 8/6/2026, 5:32:27 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