Developer · Local MCP server
Enigmagent MCP
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Agnuxo1/enigmagent-mcp- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-25
- Updated
- 2026-04-25
- Publisher
- Agnuxo1 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Agnuxo1) · how
- Repository
- github.com/Agnuxo1/enigmagent-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | enigmagent-mcp | 1.0.2 | stdio |
How to connect Enigmagent MCP
Enigmagent MCP runs locally from a Node.js package published to the npm registry: enigmagent-mcp version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y enigmagent-mcp@1.0.2. It reads these environment variables: VAULT_PASSWORD (secret) and VAULT_PATH; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"enigmagent-mcp": {
"command": "npx",
"args": [
"-y",
"enigmagent-mcp@1.0.2"
],
"env": {
"VAULT_PASSWORD": "<secret>",
"VAULT_PATH": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Engram ServerDurable memory for AI agents: fact extraction, hybrid retrieval, temporal graph. SQLite/Postgres. | Local · stdio |
| Engram: AI memory you can edit in ObsidianShared memory for Claude, ChatGPT and any MCP client. Read and edit it in Obsidian or the web app. | Remote · HTTPLive check: sign-in required |
| EngraphySelf-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector. | Local · HTTP |
| EngrmShared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex. | Local · stdio |
| Ensembl MCP ServerLook up genes, sequences, variants, homologs, and cross-database xrefs from Ensembl REST. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Enterprise MCP GatewayUnified gateway exposing 150+ tools across all NexGenData MCP servers via one endpoint. | Remote · HTTPLive check: sign-in required |
| entraadm MCPMCP server for Microsoft Entra ID sign-in and audit-log triage (read-only) | Local · stdio |
| Env Secret Exposure Analyzer MCPScans projects for secret exposure: leaked API keys, unprotected.env files, and secrets in logs. | Local · stdio |