mcp-twake-chat@0.6.1
CAUTION· install onlyPublisher claims: "Enables AI assistants to securely access and interact with Twake Chat and other Matrix homeservers, including end-to-end encrypted rooms, through tools for rooms, messages, threads, unread messages, mentions, people, attachments, drafts, and optional sending." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MATRIX_ACCESS_TOKENMATRIX_CREDENTIALS_FILEMATRIX_TOKEN_COMMANDMCP_HTTP_TOKEN_FILEConfiguration, not credentials: LIVE_QUERY, LIVE_READ_ROOM, LIVE_ROOM, MATRIX_APPROVAL, MATRIX_APPROVAL_TIMEOUT_MS, MATRIX_DEVICE_ID, MATRIX_DOWNLOAD_DIR, MATRIX_DRAFTS_ROOM_NAME, MATRIX_E2EE_RECOVERY, MATRIX_HOMESERVER_URL, MATRIX_RECOVERY_KEY_FILE, MATRIX_SEARCH_BACKFILL_DAYS, MATRIX_SEARCH_INDEX, MATRIX_SEND_SCOPE, MATRIX_STORE_DIR, MATRIX_STORE_KEY_FILE, MATRIX_TIMEOUT_MS, MATRIX_UPLOAD_DIR, MATRIX_USER_ID, MCP_HTTP_HOST, MCP_HTTP_PORT, MCP_TRANSPORT, MCP_URL, SMOKE_ROOM_QUERY, SMOKE_USER_QUERY, TOM_URL, USER_LANGUAGE, USER_TIMEZONE- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard. It asks for MATRIX_ACCESS_TOKEN, MATRIX_CREDENTIALS_FILE, MATRIX_TOKEN_COMMAND, MCP_HTTP_TOKEN_FILE and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 79/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
expect(safeName('../../etc/passwd')).toBe('passwd');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if (mode & 0o077) throw new Error(`${file} is readable by group/others (mode ${mode.toString(8)}): chmod 0600 it`);Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.env = { ...parseCredentialsFile(readFileSync(env.MATRIX_CREDENTIALS_FILE, 'utf8')), ...env };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- run: npx vitest run token-command-shellFix: Pin versions and sources; vendor anything fetched at install time.const ins = this.db.prepare('INSERT INTO msg (body, event_id, room_id, sender, sender_name, ts, thread_root) VALUES (?, ?, ?, ?, ?, ?, ?)');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.export function createMcpHttpHandler(newServer: () => McpServer, opts: HttpOptions) {Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
1 point to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim linagora: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- Access to sensitive file paths≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.