MCP

Give agents the receipts, not just the headline.

The L1fe.news MCP surface exposes the same public corpus as callable tools: story search, source receipts, coverage balance, blindspots, and framing comparisons.

Install

One server, same public corpus.

Add the L1fe.news MCP server to any MCP-compatible agent host. The server reads the public API and returns cited responses so agents can show where each claim came from.

mcp_config.json

{
  "mcpServers": {
    "l1fe-news": {
      "command": "bunx",
      "args": ["@l1fe/mcp-news"],
      "env": {
        "L1FE_NEWS_API": "https://api.l1fe.news/v1"
      }
    }
  }
}

Paid API limits and higher-throughput access are handled through L1fe account billing.

Tools

What the server exposes.

search_stories

Search published story clusters by keyword, source, topic, or blindspot.

get_story

Read one story with sources, coverage balance, summary, and receipts.

compare_framings

Compare how coverage differs across political and institutional frames.

get_claim_evidence

Open the evidence trail behind a factual claim.

list_blindspots

Find stories disproportionately covered by one side of the spectrum.

list_sources

Inspect source metadata, bias baseline, factuality baseline, and feed status.

Receipts

Every answer should point back to source coverage.

MCP responses are designed for inspection. Story tools include source URLs, publisher names, coverage balance, and the current L1fe.news story URL so users can verify the underlying reporting directly.

For endpoint details and REST examples, see the developer portal.