Life Saver MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DDS_COOKIE | No | DDS API Cookie for Lanhu (alternative to LANHU_COOKIE) | |
| LANHU_COOKIE | No | Cookie for Lanhu app authentication | |
| ZENTAO_COOKIE | No | Cookie for Zentao authentication (requires zentaosid and zp) | |
| GOOGLE_API_KEY | No | Google Gemini API Key | |
| OPENAI_API_KEY | No | OpenAI API Key (or compatible endpoint) | |
| ANTHROPIC_API_KEY | No | Anthropic Claude API Key | |
| LIFE_SAVER_CONFIG | No | Path to JSON configuration file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_imageD | – |
| analyze_urlD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools target different input types (image vs URL), making them clearly distinct despite lacking descriptions.
Both tool names follow the consistent 'analyze_' verb_noun pattern.
With only 2 tools, the server feels minimal but may be appropriate for a narrow scope; the name 'Life Saver' suggests a focused utility.
The server only offers analysis operations with no CRUD or lifecycle coverage, leaving potential gaps in functionality.