device-center

MCP server · npm · graded 2026-10-23Source linked

Local device Driver, SSH configuration references and read-only MCP prototype

No outside reports on file

device-center runs shell or system commands; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 23, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Device Center helpful?

What it can access

Local filesNo local folder access notedLOW
Command executionRuns shell or system commandsREVIEW
Network reachLocal or standard API callsLOW
CredentialsNo API token requiredLOW
Package sourcenpm (device-center)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y device-center

All setup options ↓

Check this skill Watch it in my stack Compare Add to allowlist README badge View project

About Device Center

Device Center is an MCP server focused on Files & documents: Local device Driver, SSH configuration references and read-only MCP prototype.

It is published on npm as device-center (637 weekly npm downloads). Based on its public metadata, its operational scope includes: runs shell or system commands.

Setup

These use the package this listing points to. Check the project’s own instructions before running anything.

npm command

npx -y device-center

MCP client config

For Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json).

json

{
  "mcpServers": {
    "device-center": {
      "command": "npx",
      "args": [
        "-y",
        "device-center"
      ]
    }
  }
}

Why this grade

FF — Many risk signals

Signal-based grade (0/7 points): no public source code found. This reflects adoption and transparency, not a code review.

Popularity and upkeep

23/100

Weekly npm downloads: 637
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-28).

Check a specific version →

Risks to watch for

Command execution reach: Public metadata indicates shell, terminal, or container command execution. Run inside an isolated container or VM and require human approval before executing commands.
Dependency & version pinning: Distributed via npm (device-center). 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 Device Center?

Run npx -y device-center 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 Device Center?

No reports found for this package in our research (last checked 2026-10-28). Device Center 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 Device Center actively maintained?

Device Center has 637 weekly npm downloads. Our directory data was last refreshed on 2026-10-28. Check recent commit activity, release tags, and open issues before pinning it in production.

What are alternatives to Device Center?

Compare Device Center side by side with similar MCP servers in the Related tools section on this page, or browse all MCP servers on AgentArmorHQ.

Maintain or use Device Center? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade F for Device Center

GitHub README Markdown:

markdown

[![AgentArmorHQ Risk Grade for Device Center](https://agentarmorhq.com/api/badge/device-center)](https://agentarmorhq.com/skills/device-center)

HTML embed:

html

<a href="https://agentarmorhq.com/skills/device-center"><img src="https://agentarmorhq.com/api/badge/device-center" alt="AgentArmorHQ Risk Grade for Device Center" height="20" /></a>

Terminal check:

terminal

curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "device-center"

Share with your security lead

Need sign-off to use device-center? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: device-center
- **Listing URL:** https://agentarmorhq.com/skills/device-center
- **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:** Runs shell or system commands
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** npm (device-center)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts device-center`
- **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 23, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type: App connector
Install command: npm install device-center
Est. context load: ~500 tokens / turn (~3 tool schemas, 0.25% of 200k context)
Popularity: 637 weekly npm downloads
Last updated: 2026-10-28
Last graded: 2026-10-23

Community

Discussions for Device Center

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.

Was this listing for Device Center helpful?

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