86trust / 100

Pronto Stream

by pronto.stream in Developer tools

MCP serverPassing, checked 3 h ago

Real-time planetary signal engine and Model Context Protocol (MCP) server for autonomous AI agents.

https://pronto.stream/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
160 ms typical, 160 ms slowest 5%
Last check
3 h ago
Next check
in 3 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "pronto-stream": {
      "type": "http",
      "url": "https://pronto.stream/mcp"
    }
  }
}

15 tools

  • get_billing_profile

    Report who you are resolved as and what your plan grants: the agent identity behind this call, the funded account it acts for, the plan, the per-minute call ceiling, the per-response row budget, and which indicator set you may compute. Returns a CWF BILL line, a CREDIT line when

  • register_agent

    Create your own identity on pronto and receive an API key, with no human present. Send the key back as an Authorization header on later calls and you will be recognised across sessions. Registering grants no plan. A new identity has exactly the limits an unauthenticated caller h

  • open_payment

    Buy access for yourself, with no human involved. Step one of two: this quotes the exact amount and binds the purchase to the wallet you will pay from. Three things can be bought. Call credits: plan "credits" with amount_usd from 1 to 100, at $0.001 a call — one credit per succes

  • settle_payment

    Redeem a payment you have made and activate what it bought — a plan, a pass or call credits. Step two of two, after open_payment and the transfer. Prove the payment is yours: sign the SIGN message from open_payment with the paying wallet (personal_sign; smart wallets via ERC-127

  • get_plans

    List what can be bought — call credits, day and week passes, and plans — what each costs, and what each raises — the call ceiling, the row budget, and whether the commercial indicator set is included. Machine-readable, so you can decide what to do about a refusal without parsing

  • get_latest_signals

    Fetch the most recent live signals from the wire in token-efficient CWF format, optionally filtered to one collection. The all-collections view is diversified: no provider may exceed its share of the page, no collection may take more than half of it, and what overflows is named

  • get_signal

    Fetch one signal by its id, when you already know which one you want. Every other read tool returns a set and bounds it, so re-reading a single row through them means re-running a query and hoping the row survives the row budget a second time; this returns that row and nothing el

  • search_signals

    Find signals by the words in them. Use this when you are looking for a subject — a storm name, a company, a phrase a report would print — and cannot name it as a category. When you can name it as a category instead (a country, a domain, a severity), scope_signals selects that sli

  • list_fusion_products

    List every derived intelligence product pronto can compute, with the published index or model each one implements, the signal collections it consumes, and whether it needs a plan. Read this to find out whether pronto computes the thing you need, then call get_fused_signal to actu

  • get_fused_signal

    Compute derived intelligence products from the live wire. Each result states the method it implements and cites the signals it was computed from; a source row with no citation is labelled as such. Pick one from the `product` enum, or omit it for everything the current window sup

  • scope_signals

    Select a slice of the live wire by facet tags — the structured metadata each signal carries, not the words in its text. Use this when you can name the slice you want: every high-severity climate signal in Japan, everything from one provider, everything in one language. It returns

  • get_facet_manifest

    Read the shape of the wire in one small response: a two-level tree of domain and the topics under it, each with a signal count, ranked so the busiest lead. This is the map to read first — read it once, choose a scope offline, then make one precise call to scope_signals or search_

  • list_facets

    List the full filter vocabulary: every facet value currently on the wire, across every key — lang, country, region, domain, topic, severity, provider, coverage and place — as one flat list with a signal count each, and a human-readable label for place ids. Every value it returns

  • get_related_signals

    Follow the link graph from one signal to other signals about the same subject. Each link states the reason the link exists. An echo link marks the same story from several sources. A related link marks a similar signal in the same domain. A cross-domain link joins two domains. For

  • list_data_sources

    List the data-source endpoints feeding the wire, with provider, signal type, country, cadence, and license. Returns one SRC line per source.

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
3 h agoPassed200189 ms
12 h agoPassed200160 ms