Getaegis Cli MCP Server
@getaegis/cli
npm
v1.0.5
Source verified
Published by getaegis — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Credential isolation for AI agents. Store, guard, and record — your agent never sees your API keys.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
2. Client adoption risk — 94 − 6 = 88. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 6
high Shell/command execution in server code (dist/cli/helpers.js)MTC-SRC-002
In the server's implementation (`dist/cli/helpers.js:4`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { execSync } from 'node:child_process'; import * as fs from 'node:fs'; import * as path from 'node:path'; /** * Generat
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/helpers.js
high Shell/command execution in server code (dist/key-storage/credential-manager-windows.js)MTC-SRC-002
In the server's implementation (`dist/key-storage/credential-manager-windows.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from 'node:child_process'; import { commandExists } from './key-storage.js'; const TARGET = 'aegis/master-k
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/key-storage/credential-manager-windows.js
high Shell/command execution in server code (dist/key-storage/key-storage.js)MTC-SRC-002
In the server's implementation (`dist/key-storage/key-storage.js:13`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from 'node:child_process'; import * as os from 'node:os'; import { WindowsCredentialStorage } from './crede
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/key-storage/key-storage.js
high Shell/command execution in server code (dist/key-storage/keychain-macos.js)MTC-SRC-002
In the server's implementation (`dist/key-storage/keychain-macos.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from 'node:child_process'; import { commandExists } from './key-storage.js'; const SERVICE = 'aegis'; const
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/key-storage/keychain-macos.js
high Shell/command execution in server code (dist/key-storage/secret-service-linux.js)MTC-SRC-002
In the server's implementation (`dist/key-storage/secret-service-linux.js:10`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ecFileSync } from 'node:child_process'; import { commandExists } from './key-storage.js'; const ATTRS = ['application',
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/key-storage/secret-service-linux.js
medium Untrusted input concatenated into a command sink (dist/cli/helpers.js)MTC-SRC-009
In the server's implementation (`dist/cli/helpers.js:37`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: key (2048 bits) execSync(`openssl genrsa -out "${keyPath}" 2048`, { stdio: 'pipe' }); fs.chmodSync(keyPa
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/cli/helpers.js
Tools 3
Each tool and what it can reach — statically extracted from the published source.
aegis_healthno sensitive capabilityaegis_list_servicesno sensitive capabilityaegis_proxy_requestno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (3 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.5 latest |
B 88/100 | 6 | 1.13.0 | 2026-09-07 |
v1.0.3 |
B 88/100 | 6 | 1.12.1 | 2026-08-06 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @getaegis/cli --onlineMore in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.