analyze_manifest — crx permission risk MCP Tool
analyze_manifest
(analyze manifest) is one of 3 tools on the
crx permission risk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_manifest from your client
- Claude Code crx permission risk analyze_manifest run in your project directory
- Claude Desktop crx permission risk analyze_manifest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor crx permission risk analyze_manifest ~/.cursor/mcp.json
- VS Code crx permission risk analyze_manifest .vscode/mcp.json
- Zed crx permission risk analyze_manifest ~/.config/zed/settings.json
- Windsurf crx permission risk analyze_manifest ~/.codeium/windsurf/mcp_config.json
- Cline crx permission risk analyze_manifest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI crx permission risk analyze_manifest ~/.gemini/settings.json
- Grok crx permission risk analyze_manifest .mcp.json (in your project root)
- ChatGPT crx permission risk analyze_manifest Settings → Connectors → Advanced → Developer mode
- Claude.ai crx permission risk analyze_manifest Settings → Connectors → Add custom connector
- LangChain crx permission risk analyze_manifest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crx-permission-risk https://crx-permission-risk-mcp.lipmichal.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.