Developer · Local MCP server
Koma Gate MCP
Classifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.swnotmetal/koma-gate-mcp- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-15
- Updated
- 2026-08-15
- Publisher
- swnotmetal (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/swnotmetal) · how
- Website
- github.com/swnotmetal/Project-Koma/blob/main/packages/koma-gate-mcp/README.md
- Repository
- github.com/swnotmetal/Project-Koma (folder packages/koma-gate-mcp)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | koma-gate-mcp | 0.1.1 | stdio |
How to connect Koma Gate MCP
Koma Gate MCP runs locally from a Node.js package published to the npm registry: koma-gate-mcp version 0.1.1. 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 koma-gate-mcp@0.1.1. It reads these environment variables: KOMA_PROVIDER, KOMA_MODEL, GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), ANTHROPIC_API_KEY (secret) and DEEPSEEK_API_KEY (secret); 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": {
"koma-gate-mcp": {
"command": "npx",
"args": [
"-y",
"koma-gate-mcp@0.1.1"
],
"env": {
"KOMA_PROVIDER": "<value>",
"KOMA_MODEL": "<value>",
"GEMINI_API_KEY": "<secret>",
"OPENAI_API_KEY": "<secret>",
"ANTHROPIC_API_KEY": "<secret>",
"DEEPSEEK_API_KEY": "<secret>"
}
}
}
}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 from swnotmetal (GitHub)
| Server | Runs |
|---|---|
| Koma Core MCPProtected RAG storage - agents discover public metadata, content only by access token. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| kObsidianFilesystem-first MCP for Obsidian - an LLM-maintained wiki inspired by Karpathy's LLM Wiki. | Local · stdio |
| KodaVerification and memory layer for coding-agent workflows. | Local · stdio |
| KogniteHosted agent memory: store, search, and recall facts across sessions from any MCP client. | Remote · HTTPLive check: sign-in required |
| Kolada SeKolada (RKA) MCP - Sweden's municipal & regional key-performance-indicator (KPI) database. | Remote · HTTPLive check: ✓ handshake |
| komentRead and write checked code rationale stored outside source comments. | Local · stdio |
| komentRead and write checked code rationale stored outside source comments. | Local · stdio |
| komnetLets AI coding agents coordinate asynchronously through a private git repository. No server. | Local · stdio |
| Komodo MCP ServerMCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI. | Local · stdio |