@getaegis/cli

MCPattested
v1.0.5Samuel WarrenApache-2.0Updated 2mo agonpmGitHub

Credential isolation for AI agents. Store, guard, and record — your agent never sees your API keys.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
241Downloads/wk
14GitHub stars
2Forks
2mo agoLast update
Needs 2 credentials before it runs
  • AEGIS_MASTER_KEYAPI keyrequired

    Master encryption key for the credential vault

  • AEGIS_SALTAPI keyrequired

    Hex-encoded 32-byte salt for key derivation (generated by aegis init)

  • AEGIS_REQUIRE_AGENT_AUTHAPI keyoptional

    Require agent authentication on every request (true/false, default: false)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorSamuel Warren
LicenseApache-2.0
Version1.0.5
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · f1321b3
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv1.0.5 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

3 tools · none privileged
Statically extracted from the published packagev1.0.5 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

aegis_proxy_requestNo description published

This tool published no description. Forge does not invent one.

aegis_list_servicesNo description published

This tool published no description. Forge does not invent one.

aegis_healthNo description published

This tool published no description. Forge does not invent one.

0 of 3 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Credential isolation for AI agents. Store, guard, and record — your agent never sees your API keys.

Keywords
ai-agentcredential-isolationsecuritysecrets-managementai-securityagent-governance
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in security