Skip to content

Hanging Context: News For Agents MCP server

com.hangingcontext/mcphangingcontext.comstreamable-httpv2.0.2Scanned

Fresh context for agents. Ask, search or follow stories. Each fact cites a Synorb Manifest.

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hanging Context: News For Agents MCP server can do

The Hanging Context: News For Agents MCP server is published by hangingcontext.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: hc_ask), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 9, 2026, version 2.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • hc_askAnswer a question from recent stories.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Answer a question from recent stories. Ranks stories by keyword match and copies the best key facts word for word. Returns up to 5 facts, each with its story URL and Manifest ids, and up to `limit` matched stories. If nothing matches, returns no_match true and suggestions. It does not use an LLM. Use it when the user asks a question about recent news.

    Annotations the server declares

    • title: Ask a question
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • hc_aboutExplain Hanging Context.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explain Hanging Context. Returns what it is, the checks on each story, the reuse rules, and how to read or receive stories.

    Annotations the server declares

    • title: About Hanging Context
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hc_get_storyRead one story.No findings

    Why it is in this group

    • The name "hc_get_story" says "get": a word for reading.
    Description, as the server wrote it
    Read one story. Use format `brief` for the headline, dek and key facts. Use format `full` for the whole story as Markdown. Use format `claims` for key facts and paragraphs as JSON, each with its Manifest ids. Returns the story in that format and up to 3 related stories.

    Annotations the server declares

    • title: Read a story
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hc_latestGet the latest stories, newest first.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the latest stories, newest first. Filter by topic or beat. Returns up to 20 stories with headline, dek, topic, URL and Manifest ids.

    Annotations the server declares

    • title: Get the latest stories
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hc_sinceGet only the stories that are new since your last call.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get only the stories that are new since your last call. Send the cursor from the last response. If you send no cursor, the call returns the current cursor and no stories. Returns up to 50 stories with next_cursor and has_more.

    Annotations the server declares

    • title: Get new stories since last check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hc_sourcesShow where a story gets its facts.No findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.
    Description, as the server wrote it
    Show where a story gets its facts. Returns each source with its title, source name, original URL and date, and which facts and paragraphs use it. Also returns the trust label.

    Annotations the server declares

    • title: Show a story's sources
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • hc_topicsList the topics.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the topics. Returns each topic with its title, beats, sources and story count for the last 24 hours. Also returns not_covered, a list of things this server does not cover. Call this first to get valid topic and beat ids for hc_latest, hc_search and hc_since.

    Annotations the server declares

    • title: List topics
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:39 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://hangingcontext.com/mcp: tools/list returned 8 tools to an anonymous client, including hc_ask (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 2.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http hangingcontext https://hangingcontext.com/mcp
claude mcp add --transport http hangingcontext https://hangingcontext.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__hangingcontext__hc_latest",
      "mcp__hangingcontext__hc_since",
      "mcp__hangingcontext__hc_search",
      "mcp__hangingcontext__hc_get_story",
      "mcp__hangingcontext__hc_sources",
      "mcp__hangingcontext__hc_topics",
      "mcp__hangingcontext__hc_about"
    ],
    "ask": [
      "mcp__hangingcontext__hc_ask"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as hangingcontext. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.hangingcontext/mcp/verify?hash=47f5ee3ea3154eef9cdd09f9efd16fe8afe4d7d7468f6b046b51ffe4068daa55" | jq -e '.changed == false'

Pinned hash 47f5ee3ea315, from Nov 9, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.hangingcontext/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.hangingcontext/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.hangingcontext/mcp.svg)](https://radar.anlyon.com/servers/com.hangingcontext/mcp)

Source: MCP Registry · repository. Synced Oct 26, 2026, 06:17 UTC.

Hanging Context: News For Agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hanging Context: News For Agents MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hanging Context: News For Agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Hanging Context: News For Agents MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hanging Context: News For Agents MCP server have?

8 tools: 1 write, 7 read. hc_ask, hc_latest, hc_since, hc_search, hc_get_story, hc_sources, hc_topics and hc_about.

Does the Hanging Context: News For Agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hanging Context: News For Agents MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hanging Context: News For Agents MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.