GSEP-MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSEP_PRESET | No | Preset: minimal, standard, conscious, full | full |
| OLLAMA_HOST | No | Ollama server URL | http://localhost:11434 |
| GSEP_HTTP_HOST | No | HTTP server host | 0.0.0.0 |
| GSEP_HTTP_PORT | No | HTTP server port | 3100 |
| GSEP_LOG_LEVEL | No | silent, info, debug | info |
| GSEP_TRANSPORT | No | stdio or http | stdio |
| OPENAI_API_KEY | No | OpenAI API key | |
| GSEP_MAX_GENOMES | No | Maximum cached genomes before LRU eviction | 100 |
| ANTHROPIC_API_KEY | No | Anthropic API key | |
| GSEP_MAX_SESSIONS | No | Maximum active HTTP MCP sessions | 500 |
| GSEP_STORAGE_PATH | No | Genome persistence path | ~/.gsep-mcp |
| GSEP_GENOME_TTL_MS | No | Expire idle cached genomes after this many milliseconds | 3600000 |
| GSEP_SESSION_TTL_MS | No | Expire idle HTTP MCP sessions after this many milliseconds | 1800000 |
| GSEP_GATEWAY_ENABLED | No | Enable OpenAI-compatible /v1 gateway in HTTP mode | true |
| GSEP_HTTP_AUTH_REQUIRED | No | Require API key validation for HTTP transport | true |
| GSEP_KEY_VALIDATION_URL | No | API key validation endpoint | |
| GSEP_HTTP_AUTH_FAIL_OPEN | No | Allow requests if validation service is unreachable | false |
| GSEP_GATEWAY_AUTH_REQUIRED | No | Require API key validation for gateway requests (follows HTTP_AUTH_REQUIRED by default) | |
| GSEP_SESSION_CLEANUP_INTERVAL_MS | No | Cleanup interval for expired sessions and genomes | 60000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsep_chatA | Send a message through the full GSEP pipeline. Runs C3 prompt injection scan, enhanced LLM call with evolved genes, C4 behavioral immune check, C5 action firewall, fitness tracking, and autonomous evolution. Returns the protected response. |
| gsep_scan_inputA | Scan user input with C3 Content Firewall (53 patterns). Detects prompt injection, role hijacking, data exfiltration attempts, encoding evasion, and more. Use this before sending any external content to your LLM. |
| gsep_scan_outputA | Scan LLM output with C4 Behavioral Immune System (6 checks). Detects if the response was infected by Indirect Prompt Injection — system prompt leakage, role confusion, data exfiltration patterns, and more. |
| gsep_scan_actionsA | Scan LLM response for dangerous or destructive actions with C5 Action Firewall (80+ patterns). Classifies actions as safe/caution/destructive/critical. Permanently blocks rm -rf, DROP DATABASE, disk wipes, etc. |
| gsep_before_llmA | Middleware hook to run before any agent calls an LLM. Returns enhanced_prompt, sanitized_message, and C3/security status. Use this when GSEP-MCP protects an existing external agent rather than owning the LLM call. |
| gsep_after_llmA | Middleware hook to run after an external LLM responds. Runs C4 behavioral immune checks, records fitness, and returns safe_response before content is shown to users or tools. |
| gsep_before_toolB | Middleware hook to run before an agent executes a tool, shell command, database query, filesystem action, or API call. Uses C5 Action Firewall to block destructive actions before execution. |
| gsep_after_toolA | Middleware hook to run after a tool returns external content and before that content is fed back into an agent/LLM. Scans for prompt injection and dangerous action instructions. |
| gsep_get_statusA | Get genome health, fitness scores, drift status, evolution generation, and security stats. Omit genome_id to list all active genomes. |
| gsep_record_feedbackA | Record user satisfaction feedback for a genome. Positive signals reinforce current gene configuration. Negative signals trigger evolution on the next cycle. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gsepcore/gsep-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server