Home / MCP registry index / com.hangingcontext/mcp
Hanging Context: News For Agents
com.hangingcontext/mcp in the official MCP registry.
Endpoint https://hangingcontext.com/mcp. Source: github.com/Synorb/hanging-context.
The registry describes it as: Fresh context for agents. Ask, search or follow stories. Each fact cites a Synorb Manifest.
We read its 8 tools on 2026-10-27. 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
hc_ask hc_latest hc_since hc_search hc_get_story hc_sources hc_topics hc_about
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-hangingcontext-mcp)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.
Related
| mu.micro/mu mu.micro/mu | 167 tools, nothing matched 2026-10-27 |
| Rumoro dev.rumoro/mcp | 57 tools, nothing matched 2026-10-26 |
| com.datronis/mcp com.datronis/mcp | 49 tools, nothing matched 2026-10-27 |
| FirmLedger ke.co.firmledger/firmledger | 49 tools, nothing matched 2026-10-27 |
| Espn io.github.pipeworx-io/espn | 48 tools, nothing matched 2026-10-27 |
| NanoTools io.github.nanotools-x402/nanotools | 45 tools, nothing matched 2026-10-22 |