Home / MCP registry index / dev.coinop/longwatch
dev.coinop/longwatch
dev.coinop/longwatch in the official MCP registry.
Endpoint https://longwatch.dev/mcp.
The registry describes it as: You are ephemeral; this remembers. Persist watch_id+key; poll later for what you missed.
We read its 18 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.
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
check_now create_watch check_web_page watch_web_page check_rss_feed watch_rss_feed check_crypto_price watch_crypto_price check_sec_filings watch_sec_filings check_insider_trades watch_insider_trades check_x402_endpoint watch_x402_endpoint poll_alerts try_watch poll_trial delete_watch
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-coinop-longwatch)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.