Servidor MCP de pronto.stream

• Endereçohttps://pronto.stream/mcpfora do registro oficial: respondeu quando perguntado

Nenhuma entrada do registro oficial de MCP nomeia este servidor. Ele respondeu em pronto.stream quando o Atlas perguntou no endereço onde servidores costumam ficar, então é do próprio fornecedor. Clientes e catálogos que listam servidores a partir do registro não o mostram.

• Estadorespondeverificado em 2026-10-28
• Ferramentas15
• O servidor se chamapronto-mcp
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

Em 2026-10-28 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 485 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCP98 de 100responde 100 · definições 100 · contexto 87 · conexão 100
• Respondeuem 100% dos dias7 de 7 verificações diárias
• Mediana da primeira resposta484 ms
• Espaço no contexto do agente≈ 4.862 tokensas definições de todas as ferramentas (15), que o agente carrega a cada turno
• Definições das ferramentasA · 100 de 100
• Resultados tipados0 de 15 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Todas as ferramentas passam nas seis verificações.

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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.