New Runtime archive

Read-only remote MCP server for the New Runtime AI-engineering newsroom archive: search and fetch evidence-linked signals, analyses, patterns and systems; contextualize a URL; submit sources or corrections.

View on newruntime.comTry this MCPSponsored

Hosted MCP Server

npx add-mcp 'https://newruntime.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

New Runtime agent entrypoint

Stable public routes, recommended reading order, source policy, and non-mutation boundaries for agents.

Recommended reading order

  1. Start with llms.txt or the developer guide.
  2. Narrow with patterns.json or topics.json.
  3. Retrieve only relevant detail JSON or Markdown records.
  4. Verify factual claims against each record's publishable source_urls.
  5. Use changes.xml for updates or POST /mcp for bounded resource reads.
  6. Use payment capabilities to discover optional paid compute products; send an unsigned request before authorizing any x402 payment.
  7. For EURC, WETH, cbBTC, or wSOL, use the candidate payment_route marked settlement_enabled=true. Never sign the sibling /quote-preview route.
  8. For native BNB, ETH, AVAX, POL, or SOL, use the exact direct_native_payment.candidates[].payment_route: preflight, broadcast the exact transfer with its declared data/memo binding, then submit that transaction identifier. Do not send an unquoted transfer.

When to use New Runtime

  • Compare a new AI capability with earlier signals, patterns, and system changes.
  • Retrieve a compact evidence-linked explanation of an agent engineering topic.
  • Inspect public project briefs, constraints, proof artifacts, and reproducibility commands.
  • Read the public owner career profile through recruiter- and ATS-friendly JSON or Markdown.
  • Buy a bounded archive research bundle or dated prior-coverage check without creating an account or API key.

Paid compute

The live payment-capabilities document is the source of truth for product IDs, prices, networks, assets, preflight, finality, and replay. Fixed and ERC-20/SPL routes use x402 exact settlement. Native BNB/ETH/AVAX/POL/SOL routes use the advertised exact-direct flow and require an onchain quote binding. Published records remain free. A paid POST computes a derived response but cannot mutate editorial or operational state.

Boundary

Public routes expose published records, publishable evidence, and explicitly advertised paid compute products only. They do not expose private discovery feeds, inbox rules, credentials, drafts, private Telegram operations, approval actions, deployment, administration, or site mutations.