# AI Lifeline (read-only observed values) (remote · ai-lifeline.org)

Read-only daily observed values from ai-lifeline.org with unit, date and source (JP, US, EU, SG).

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `ai-lifeline.org`: 71/100 (this document), [markdown](https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php.md), [page](https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php)

## Channel facts

- Endpoint: `https://ai-lifeline.org/api/mcp.php`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 606 tokens (~151/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AI Lifeline (read-only observed values) MCP server?

AI Lifeline (read-only observed values) is a hosted endpoint at https://ai-lifeline.org/api/mcp.php, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-ai-lifeline-ai-lifeline 'https://ai-lifeline.org/api/mcp.php'
```

### Cursor

```json
{
  "mcpServers": {
    "org-ai-lifeline-ai-lifeline": {
      "url": "https://ai-lifeline.org/api/mcp.php"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-ai-lifeline-ai-lifeline": {
      "type": "http",
      "url": "https://ai-lifeline.org/api/mcp.php"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-ai-lifeline-ai-lifeline]
url = "https://ai-lifeline.org/api/mcp.php"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-ai-lifeline-ai-lifeline": {
      "type": "remote",
      "url": "https://ai-lifeline.org/api/mcp.php",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-ai-lifeline-ai-lifeline --url 'https://ai-lifeline.org/api/mcp.php' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-ai-lifeline-ai-lifeline:
    url: "https://ai-lifeline.org/api/mcp.php"
```

### Netclaw

```json
{
  "McpServers": {
    "org-ai-lifeline-ai-lifeline": {
      "Transport": "http",
      "Url": "https://ai-lifeline.org/api/mcp.php"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-ai-lifeline-ai-lifeline -t streamable-http -u 'https://ai-lifeline.org/api/mcp.php'
```

### Other

```json
{
  "mcpServers": {
    "org-ai-lifeline-ai-lifeline": {
      "type": "http",
      "url": "https://ai-lifeline.org/api/mcp.php"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 71, +53)

- [security improvement] HTTPS: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.67
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-22 (score 18, −52)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.60 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-20 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 30. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 65, +2)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 23. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `list_series` (~104 tokens)

List the chapters AI Lifeline publishes (one entry per chapter page, from /api/index.json) with their page URL, API URL,
    the one-sentence answer line, the headline value (value, unit, date) and the series ids that belong to the chapter.
    region: optional filter, one of 'jp', 'us', 'eu', 'sg'. Returns exactly what index.json and series.json contain; no re-aggregation.

Input parameters:

- `region`

### `get_series` (~131 tokens)

Return one series by its permanent id ('<region>/<chapter>/<series_key>', e.g. 'jp/fiscal/jgb_yield') with the latest published
    value, unit, observed_at (observation date), value_status (final/provisional), the primary source (name, source_url, license,
    attribution), update frequency, last confirmed date, staleness judgement from health.json, limitations, page and API URLs, and checked_at
    (generation time of the site files). Values are the ones published by the site; nothing is recomputed.

Input parameters:

- `series_id` (string, required)

### `get_health` (~143 tokens)

Return the liveness of AI Lifeline itself from /api/health.json: site_status (ok/degraded), totals (series, stale, fetch_failed,
    source_under_review, not_measured), the staleness rule as written, the generation time per edition, and per series: last confirmed
    observation date, update frequency, next expected update, stale flag, age_days and the status of the last fetch.
    region: optional filter 'jp'|'us'|'eu'|'sg'. only_stale: return only series with stale=true. Nothing here judges the observed world.

Input parameters:

- `only_stale` (boolean)
- `region`

### `search_series` (~102 tokens)

Search published series by words in the series id, name, chapter, unit or source name (case-insensitive substring match over
    /api/series.json). Returns up to `limit` matches with series_id, name, unit, region, chapter, update_frequency, last_confirmed
    and source name; use get_series for the value. No ranking beyond match order in the registry.

Input parameters:

- `limit` (integer)
- `query` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php#diagnostics

## Score history

- 2026-10-23: 71
- 2026-10-22: 18
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 66
- 2026-10-12: 66
- 2026-10-10: 65
- 2026-10-07: 63
- 2026-10-05: 63
- 2026-10-04: 62
- 2026-10-03: 62

## Common questions

### What is the AI Lifeline (read-only observed values) MCP server?

AI Lifeline (read-only observed values) is an MCP server listed in the public MCP registry as org.ai-lifeline/ai-lifeline. Read-only daily observed values from ai-lifeline.org with unit, date and source (JP, US, EU, SG). This page covers its hosted endpoint (https://ai-lifeline.org/api/mcp.php).

### Is the AI Lifeline (read-only observed values) MCP server safe to use?

AI Lifeline (read-only observed values) scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AI Lifeline (read-only observed values) MCP server expose?

AI Lifeline (read-only observed values) exposes 4 tools: list_series, get_series, get_health, search_series. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

### Does the AI Lifeline (read-only observed values) MCP server require authentication?

No. We connected to AI Lifeline (read-only observed values) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the AI Lifeline (read-only observed values) MCP server still maintained?

AI Lifeline (read-only observed values) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ai-lifeline.org/api/mcp.php
- Website: https://ai-lifeline.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php.json
- HTML version of this page: https://verifymcp.io/servers/org-ai-lifeline-ai-lifeline/api-mcp-php