Server
Courier
Published by trycourier. Transport: HTTPS (remote). Written in typescript.
Description
Description below is sourced from the LF AAIF MCP registry. MCPowered surfaces the publisher's own words; the publisher is the warrantor of any claims they make.
Send notifications, manage templates, and configure integrations with Courier.
Provenance
- Server id
github/trycourier/courier-mcp- Repository
- trycourier/courier-mcp
- Surfaced by
- awesome-mcp-servers , LF AAIF registry
- Category
- Communication
Scan status
Tool description scan , Tool output literal scan , Dependency CVE check , Permission audit
Findings
No patterns matched. Per the posture, that is the absence of evidence of malice. It is not evidence of integrity.
What we couldn't check
-
dynamic_tool_descriptionsStatic analysis only sees descriptions hardcoded in source. Servers that compute descriptions at runtime (server-generated tools/list responses) are not covered by Check 1 at v0.
-
ast_indirectionv0 regex sees only literal description strings. Descriptions assembled by concatenation or pulled through variable indirection evade detection until AST-level extraction lands in v1.
Install configuration
Universal install-config generation across agent clients (Claude Code, Cursor, Windsurf, ChatGPT Apps, Continue, Cline, Zed) is a v0 deliverable. For now, install per the publisher's repository instructions linked above. The auto-generated client-specific configuration block lands here when the install-config generator ships.
Disclaimer
Scan results describe what our static checks found and didn't find at the time of scan. They are not a recommendation, certification, or guarantee. A scanned-clean result is the absence of evidence of malice, not the presence of evidence of integrity. Servers can be compromised after scan. You are responsible for evaluating whether to install any MCP server. See our methodology for what we check, what we can't check, and the limits of static analysis.
MCPowered