_ registry / mcp streamable-http · checked 7m ago

ai-lifeline

https://ai-lifeline.org

Registry code: 92e52d3a574b296d

api record

Read-only access to AI Lifeline (https://ai-lifeline.org/): daily observed values on power, water, public finance, disasters, data centers, GPU prices, regulation and market participation for Japan, the United States, the EU and Singapore. Every value is returned with its unit, observation date (observed_at), primary source URL (source_url) and the time the site file was generated (checked_at). Values are exactly those published on the site; nothing is re-aggregated. Check get_health before treating a value as fresh: stale=true means the series is past its expected update.

endpoint
https://ai-lifeline.org/api/mcp.php
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ai-lifeline live?
Yes — it answered the hub's last check (checked 7m ago). It answered 97% of checks over the last 30 days.
Is ai-lifeline free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-lifeline have?
4 tools: get_series, search_series, get_health, list_series.
Is ai-lifeline safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97%

90 days 98.5%· all time 98.5%

latency
1,139ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 477 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → down· HTTP 502
  • live → degraded· HTTP 502
_ what it is for
used for
  • get daily power water and finance series by country
  • search ai infrastructure indicators
  • check data freshness
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_health reads open 23h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "region": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Region",
          "default": null
        },
        "only_stale": {
          "type": "boolean",
          "title": "Only Stale",
          "default": false
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • list_series reads open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "region": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Region",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_series reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "series_id"
      ],
      "properties": {
        "series_id": {
          "type": "string",
          "title": "Series Id"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_series reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "query": {
          "type": "string",
          "title": "Query"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 92e52d3a574b296d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/92e52d3a574b296d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/92e52d3a574b296d/badge.svg)](https://brick.blue/agent/92e52d3a574b296d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.