@lumenkey/cli
Unified CLI & MCP Server for LumenKey Multi-Modal AI (Video, Image & LLMs)
No outside reports on file
@lumenkey/cli is distributed via npm (@lumenkey/cli); review its source code, dependencies, and requested permissions before use.
Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesNo local folder access notedLOW
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsNo API token requiredLOW
- Package sourcenpm (@lumenkey/cli)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
npx -y @lumenkey/cliAbout @lumenkey/cli
@lumenkey/cli is an MCP server focused on Developer tools and Cloud & infrastructure: Unified CLI & MCP Server for LumenKey Multi-Modal AI (Video, Image & LLMs).
It is published on npm as @lumenkey/cli. Based on its public metadata, it operates with standard local or API scope without broad shell execution flags noted.
Setup
These use the package this listing points to. Check the project’s own instructions before running anything.
npm command
npx -y @lumenkey/cliMCP client config
For Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json).
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"@lumenkey/cli"
]
}
}
}Why this grade
Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- Listing last refreshed
- 2026-10-28
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Security reports
No reports found for this package in our research (last checked 2026-10-29).
Risks to watch for
- Dependency & version pinning: Distributed via npm (@lumenkey/cli). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.
How to lower the risk
Least-privilege permissions
- Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
- Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.
Network isolation
- Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
- If your IT team can, limit which websites and services it is allowed to contact.
Monitoring
- Check its activity history or logs weekly at first, and look at what it changed or sent.
- Turn on alerts for new logins or unusual usage on any account it connects to.
Red flags to watch for
- It asks for more access than its job requires, or prompts you to paste passwords.
- It suddenly updates with new owners, or starts contacting unfamiliar websites.
Questions
How do I install @lumenkey/cli?
Run npx -y @lumenkey/cli in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page.
Are there security reports about @lumenkey/cli?
No reports found for this package in our research (last checked 2026-10-29). @lumenkey/cli currently holds Grade F (Many risk signals) based on public adoption and transparency signals. Review the permissions and source repository before granting access to local files, shell commands, or API keys.
Is @lumenkey/cli actively maintained?
We do not have star or download counts on file for @lumenkey/cli yet (listing refreshed 2026-10-28). Check the commit history and open issues before relying on it.
What are alternatives to @lumenkey/cli?
Compare @lumenkey/cli side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.
README badge and team notes
Maintain or use @lumenkey/cli? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/lumenkey-cli)HTML embed:
<a href="https://agentarmorhq.com/skills/lumenkey-cli"><img src="https://agentarmorhq.com/api/badge/lumenkey-cli" alt="AgentArmorHQ Risk Grade for @lumenkey/cli" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "lumenkey-cli"Share with your security lead
Need sign-off to use @lumenkey/cli? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: @lumenkey/cli
- **Listing URL:** https://agentarmorhq.com/skills/lumenkey-cli
- **Type:** App connector
- **Risk Grade:** Grade F (Many risk signals)
- **Outside Security Advisories on File:** 0
#### Permission & Blast-Radius Signals
- **Local files:** No local folder access noted
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** npm (@lumenkey/cli)
#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts @lumenkey/cli`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- App connector
- Install command
- npm install @lumenkey/cli
- Est. context load
- ~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
- Last updated
- 2026-10-28
- Last graded
- 2026-10-20
Community
Discussions for @lumenkey/cli
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude