productivity
Not malicious, needs a look Reviewed: expected behaviour
Bawwab's static rules found patterns that deserve a human look. This is not a finding that the package is malicious; the review notes below say what each pattern turned out to be.
Why it was flagged
The static rules marked this “Not malicious, needs a look” because of:
plugin.unresolved-server: Bundled MCP server could not be resolved (med, 2×)
- Kind
- Plugin
- Source
- github
- Repository
- anthropics/knowledge-work-plugins / productivity
- Commit
0e0fcacddcc892eb92a1b7873ff9d68159c47571- Listed in
- anthropics/knowledge-work-plugins
- Popularity
- 36,600 GitHub stars (2026-11-20)
- Link
- https://github.com/anthropics/knowledge-work-plugins/tree/0e0fcacddcc892eb92a1b7873ff9d68159c47571/productivity
- Scanned
- 2026-11-20T23:09:00+00:00
- Scan time
- 5.1 s
- Scanned as
- plugin
Review note: Anthropic's knowledge-work plugin of skills and hosted MCP connectors; the only flags are two connectors with an empty URL.
Findings (2)
plugin.unresolved-server: Bundled MCP server could not be resolved med
[server google calendar] cannot resolve how this bundled MCP server starts; it was not scanned
What this means: The plugin declares an MCP server whose start command could not be traced to code, so it was not scanned.
The rule's general advice: Review the server command in the plugin manifest manually. (see the review note for this case)
Expected for what this tool does
The .mcp.json entry for 'google calendar' has type http and an empty url, so there is no server to start or contact until the user supplies one; the other connectors point to vendor-hosted URLs.
Reviewed by Bawwab maintainers, 2026-11-20
plugin.unresolved-server: Bundled MCP server could not be resolved med
[server gmail] cannot resolve how this bundled MCP server starts; it was not scanned
What this means: The plugin declares an MCP server whose start command could not be traced to code, so it was not scanned.
The rule's general advice: Review the server command in the plugin manifest manually. (see the review note for this case)
Expected for what this tool does
The .mcp.json entry for 'gmail' has type http and an empty url, so there is no server to start or contact until the user supplies one.
Reviewed by Bawwab maintainers, 2026-11-20
8 low-severity notes (informational, do not affect the result)
plugin.bundled-mcp: Plugin bundles an MCP server low
.mcp.json
OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0010.005 Supply Chain Compromise: AI Agent Tool
plugin bundles MCP server(s): asana, atlassian, clickup, gmail, google calendar, linear, monday, notion, slack
What this means: The plugin installs additional MCP servers that run code on your machine and are not covered by this layer alone.
What you can do: Review each bundled server as if you were installing it separately.
fetch.auth-required: Remote server requires sign-in low
[server slack] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server notion] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server asana] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server linear] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server atlassian] remote server answered HTTP 403; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server monday] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
fetch.auth-required: Remote server requires sign-in low
[server clickup] remote server answered HTTP 401; sign-in required
What this means: The remote server requires sign-in; its tool descriptions could not be read. Bawwab re-checks at session start.
What you can do: Sign in through Claude; Bawwab re-checks the tool descriptions at session start.
Dispute this result
Maintainer and think this is wrong? Open a dispute on GitHub with the target id plugin-anthropics-knowledge-work-plugins-productivity-f91b3d.