Home / MCP registry index / ai.smry.r/smry-product
smry Product
ai.smry.r/smry-product in the official MCP registry.
Endpoint https://api.smry.ai/mcp. Source: github.com/mrmps/SMRY.
The registry describes it as: Read public sources and manage a smry library, feeds, notes, highlights, files, and page monitors.
We read its 28 tools on 2026-10-21. 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_article search_article search_web open_web_pages search_feeds list_library_objects get_library_object get_library_asset list_library get_library_changes get_saved_article search_saved_item save_content save_article update_library_item bulk_update_library_items remove_library_item manage_collections query_feeds manage_feed_filter discover_feed_inputs follow_feeds create_news_query set_feed_feedback get_feed_changes mutate_feeds create_monitor manage_feed_consumers
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-smry-r-smry-product)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.