Content Tools

feedatom.com

Aggregates news stories from multiple sources and provides searchable claims, topics, and source attribution with temporal context.

1 endpoint9 known toolsFirst detected October 16, 2026Last detected October 16, 2026

ENDPOINT 1

https://mcp.feedatom.com//mcp

No auth detected

MCP server metadata

Name: feedatom
Version: 0.1.0

Capabilities

tools

Server instructions

FeedAtom answers with stories and the claims behind them, not with links. Every answer carries its sources, both time axes (when it was true, when we learned it) and a confidence. Call list_stories or search_stories to find coverage; call search_claims for a factual question, then get_evidence for the proof behind any claim. Quote our summaries with attribution; publisher text is linked, never reproduced.

Known tools 9

list_stories

Stories ranked by what the ledger learned, each one gathering the articles that report it.

Inferred read-only

get_story

A single story: what happened, which sources reported it, and what the ledger recorded from them.

Inferred read-only

search_stories

Full-text search over stories.

Inferred read-only

list_topics

Every topic with coverage, for narrowing list_stories or search_stories.

Inferred read-only

search_claims

Answers with CLAIMS - what is asserted about a subject, by how many sources, and when it was true - rather than with links.

Inferred read-only

find_entity

Resolves a name to the entities the ledger knows, with their type and namespace.

Inferred read-only

get_dossier

The whole file on one entity: what is asserted about it by kind, how much of that is contradicted, who it appears beside, and its most recent claims with both time axes.

Inferred read-only

get_evidence

Every piece of evidence recorded for a claim: which document, which source, and the excerpt where we may redistribute it.

Inferred read-only

what_changed

The history of one subject's claims on both time axes: what was true when, and when we learned it.

Inferred read-only

CONNECT 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.feedatom]
url = "https://mcp.feedatom.com//mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "feedatom": {
      "type": "http",
      "url": "https://mcp.feedatom.com//mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: feedatom
Remote MCP URL: https://mcp.feedatom.com//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": {
    "feedatom": {
      "url": "https://mcp.feedatom.com//mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "feedatom": {
      "type": "http",
      "url": "https://mcp.feedatom.com//mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "feedatom",
  "transport": "streamable-http",
  "url": "https://mcp.feedatom.com//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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.