Home / MCP registry index / io.github.nmxmxh/pronto-stream
io.github.nmxmxh/pronto-stream
io.github.nmxmxh/pronto-stream in the official MCP registry.
Endpoint https://pronto.stream/mcp. Source: github.com/nmxmxh/pronto_v1.
The registry describes it as: Real-time planetary signal engine and Model Context Protocol (MCP) server for autonomous AI agents.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_billing_profile register_agent open_payment settle_payment get_plans get_latest_signals get_signal search_signals list_fusion_products get_fused_signal scope_signals get_facet_manifest list_facets get_related_signals list_data_sources
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-nmxmxh-pronto-stream)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.