Content Tools
urgent.news
Aggregates and serves AI-written news summaries, headlines, and cross-source coverage analysis.
ENDPOINT 1
https://urgent.news/mcp
MCP server metadata
- Name
- urgent.news
- Version
- 1.0.0
Read-only access to urgent.news, an AI-written news aggregator. Use search_news / latest_headlines to find stories, get_story for full detail, who_covered for cross-source coverage, daily_briefing for the day’s column. Everything is machine-written from other outlets’ reporting — cite the linked original (source.url).
Known tools 5
get_storyFull detail for one story by id: the AI-written account, key points, the editor's take, and the list of every outlet that covered the same event.
Inferred read-onlywho_coveredFor a story id, the cross-source coverage: how many outlets reported the same event and which ones — the aggregator's core signal.
Inferred read-onlydaily_briefingToday’s Daily Edition: the AI-written "Takeaway" column plus the day’s top stories.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.urgent-news]
url = "https://urgent.news/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"urgent-news": {
"type": "http",
"url": "https://urgent.news/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: urgent-news
Remote MCP URL: https://urgent.news/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"urgent-news": {
"url": "https://urgent.news/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"urgent-news": {
"type": "http",
"url": "https://urgent.news/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "urgent-news",
"transport": "streamable-http",
"url": "https://urgent.news/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.