AgentArmorHQ
Sign in

@stack256org/openeve

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

Filesystem-first framework for durable backend AI agents that run anywhere.

No outside reports on file

@stack256org/openeve reads and writes local folders; restrict its folder reach, network access, and credentials before installing.

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

Was this verdict for @stack256org/openeve helpful?

What it can access

  • Local filesReads & writes local foldersREVIEW
  • Command executionNo shell command runner notedLOW
  • Network reachLocal or standard API callsLOW
  • CredentialsNo API token requiredLOW
  • Package sourcenpm (@stack256org/openeve)PUBLIC

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

Install

npx -y @stack256org/openeve

All setup options ↓

Check this skillWatch it in my stackCompareAdd to allowlistREADME badgeView project

About @stack256org/openeve

@stack256org/openeve is an MCP server focused on Files & documents: Filesystem-first framework for durable backend AI agents that run anywhere.

It is published on npm as @stack256org/openeve and hosted on GitHub at stack256org/openeve (last repository push on 2026-09-20). Based on its public metadata, its operational scope includes: reads & writes local folders.

Setup

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

npm command

npx -y @stack256org/openeve

MCP client config

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

json
{
  "mcpServers": {
    "openeve": {
      "command": "npx",
      "args": [
        "-y",
        "@stack256org/openeve"
      ]
    }
  }
}

Why this grade

DD — High risk signals

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

Popularity and upkeep

4/100
Listing last refreshed
2026-10-23

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).

Check a specific version →

Risks to watch for

  • Local folder write access: Can create, edit, or delete files on disk. Restrict its working directory to a dedicated project folder and never mount home or credential directories.
  • Dependency & version pinning: Distributed via npm (@stack256org/openeve). 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 @stack256org/openeve?

Run npx -y @stack256org/openeve 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. Full setup docs and environment variables are in github.com/stack256org/openeve.

Are there security reports about @stack256org/openeve?

No reports found for this package in our research (last checked 2026-10-29). @stack256org/openeve currently holds Grade D (High 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 @stack256org/openeve actively maintained?

We do not have star or download counts on file for @stack256org/openeve yet (listing refreshed 2026-10-23). Check the commit history and open issues at github.com/stack256org/openeve before relying on it.

What are alternatives to @stack256org/openeve?

You can compare @stack256org/openeve side by side with other Filesystem MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

README badge and team notes

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

AgentArmorHQ Risk Grade D for @stack256org/openeve

GitHub README Markdown:

markdown
[![AgentArmorHQ Risk Grade for @stack256org/openeve](https://agentarmorhq.com/api/badge/stack256org-openeve)](https://agentarmorhq.com/skills/stack256org-openeve)

HTML embed:

html
<a href="https://agentarmorhq.com/skills/stack256org-openeve"><img src="https://agentarmorhq.com/api/badge/stack256org-openeve" alt="AgentArmorHQ Risk Grade for @stack256org/openeve" height="20" /></a>

Terminal check:

terminal
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "stack256org-openeve"

Share with your security lead

Need sign-off to use @stack256org/openeve? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: @stack256org/openeve
- **Listing URL:** https://agentarmorhq.com/skills/stack256org-openeve
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0

#### Permission & Blast-Radius Signals
- **Local files:** Reads & writes local folders
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** No API token required
- **Package source:** npm (@stack256org/openeve)

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

Key facts

Type
App connector
Publisher
stack256org
Source code
github.com/stack256org/openeve
Install command
npm install @stack256org/openeve
Est. context load
~500 tokens / turn (~3 tool schemas, 0.25% of 200k context)
Last updated
2026-10-23
Last graded
2026-10-22

Community

Discussions for @stack256org/openeve

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 @stack256org/openeve 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