AI Lifeline (read-only observed values)
by ai-lifeline.orgorg.ai-lifeline/ai-lifelinev1.0.0
Read-only daily observed values from ai-lifeline.org with unit, date and source (JP, US, EU, SG).
- Remote endpoint
Uptime
Checked · every day
99.94%from 14 days of checks
Up without downtime on 12 of 13 days with data; down 10 minutes in all, on 3 November.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 2752 ms, slowest 5% 7680 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 93.3%
- Completed the handshake 93.3%
- Listed its tools 86.6%
4 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 12 Nov (today) | No verdict yet | 0 | – |
| 11 Nov | No downtime | 1of 1 | 1959 ms |
| 10 Nov | No downtime | 1of 1 | 2808 ms |
| 9 Nov | No downtime | 1of 1 | 3516 ms |
| 8 Nov | No downtime | 1of 1 | 2728 ms |
| 7 Nov | No downtime | 1of 1 | 4285 ms |
| 6 Nov | No downtime | 1of 1 | 3496 ms |
| 5 Nov | No downtime | 1of 1 | 2745 ms |
| 4 Nov | No downtime | 1of 1 | 3506 ms |
| 3 Nov | Down 10 minutes | 3of 1 | 7231 ms |
| 2 Nov | No downtime | 1of 1 | 2737 ms |
| 1 Nov | No downtime | 1of 1 | 2749 ms |
| 31 Oct | No downtime | 1of 1 | 3496 ms |
| 30 Oct | No downtime | 1 | 3476 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://ai-lifeline.org/api/mcp.php Run in a terminal:
claude mcp add --transport http ai-lifeline https://ai-lifeline.org/api/mcp.php Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"ai-lifeline": {
"type": "http",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"ai-lifeline": {
"type": "streamableHttp",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "ai-lifeline"
type: streamable-http
url: "https://ai-lifeline.org/api/mcp.php" Add to ~/.config/goose/config.yaml:
extensions:
"ai-lifeline":
type: streamable_http
name: "ai-lifeline"
enabled: true
uri: "https://ai-lifeline.org/api/mcp.php"
headers: {}
env_keys: []
envs: {}
timeout: 300 Add to ~/.gemini/settings.json:
{
"mcpServers": {
"ai-lifeline": {
"httpUrl": "https://ai-lifeline.org/api/mcp.php"
}
}
} Run in a terminal:
codex mcp add ai-lifeline --url https://ai-lifeline.org/api/mcp.php Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
{
"mcpServers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"ai-lifeline": {
"type": "streamable",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"ai-lifeline": {
"type": "http",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server AI Lifeline (read-only observed values) (`org.ai-lifeline/ai-lifeline`)
Its page: https://plug.directory/servers/org.ai-lifeline/ai-lifeline
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://ai-lifeline.org/api/mcp.php
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport http ai-lifeline https://ai-lifeline.org/api/mcp.php
```
## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
```json
{
"mcpServers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"ai-lifeline": {
"type": "http",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Zed
Merge into ~/.config/zed/settings.json:
```json
{
"context_servers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Cline
Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
```json
{
"mcpServers": {
"ai-lifeline": {
"type": "streamableHttp",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "ai-lifeline"
type: streamable-http
url: "https://ai-lifeline.org/api/mcp.php"
```
## Goose
Merge into ~/.config/goose/config.yaml:
```yaml
extensions:
"ai-lifeline":
type: streamable_http
name: "ai-lifeline"
enabled: true
uri: "https://ai-lifeline.org/api/mcp.php"
headers: {}
env_keys: []
envs: {}
timeout: 300
```
## Gemini CLI
Merge into ~/.gemini/settings.json:
```json
{
"mcpServers": {
"ai-lifeline": {
"httpUrl": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Codex
Run in a terminal:
```sh
codex mcp add ai-lifeline --url https://ai-lifeline.org/api/mcp.php
```
## mcp-client-cli, TUUI, BoltAI
This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
Merge into ~/.config/agenvoy/mcp.json:
```json
{
"servers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"ai-lifeline": {
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## AnythingLLM
Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
```json
{
"mcpServers": {
"ai-lifeline": {
"type": "streamable",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
## Augment Code
Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
```json
{
"mcpServers": {
"ai-lifeline": {
"type": "http",
"url": "https://ai-lifeline.org/api/mcp.php"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem