Verified Feed MCP Server

com.dropwatchhq/verified-feed

answering

Verified Feed is answering right now. Last checked 1 min ago. It exposes 4 tools.

Contradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt.

Uptime history 41 hours of history

41 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

68 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add verified-feed --transport http https://verified.dropwatchhq.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "verified-feed": {
      "url": "https://verified.dropwatchhq.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.verified-feed]
url = "https://verified.dropwatchhq.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "verified-feed": {
      "url": "https://verified.dropwatchhq.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "verified-feed": {
      "url": "https://verified.dropwatchhq.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_receipt

Recompute + verify a verification receipt's hash-chain (proves the verification is unaltered since its as-of date). Pass the receipt id.

verify_record

Run a contradiction-verified, signed verification on ONE record of a data owner's feed. Attaches a verification STATUS (VERIFIED / CONTRADICTED / EXCLUSION_HIT / UNVERIFIABLE), an AS-OF date, source links, and a tamper-evident hash-chain receipt — by re-checking the record's subject against the live contradiction-engine (SEC 10-K vs USAspending) and, for named entities, the live exclude-feed. A dated evidence statement, never a guarantee.

verify_subject

One-off contradiction-verified check of a single subject (ticker and/or named entity) against the live hubs, with an as-of date and signed receipt. Free preview shows status only; paid call returns full detail + receipt.

feed

feed_status

Return the latest verification snapshot of a minted feed: per-record status + as-of date + stale flags (records past the feed's freshness SLA) + signed receipts. Try slug 'govcon-demo'.

Endpoints

URL	Transport	State	Latency	Checked
https://verified.dropwatchhq.com/mcp	streamable-http	answering	58 ms	1 min ago

Verified Feed — questions

Answers built from our own checks of this server.

What can Verified Feed do?

It exposes 4 tools, read directly from the server on our last check. Among them: feed_status, verify_receipt, verify_record, verify_subject. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Verified Feed working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 68 ms. The bar chart above shows every period we have measured.

How do I connect Verified Feed?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Verified Feed need an API key?

No. Verified Feed completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Verified Feed?

It answers our handshake in 68 ms on average, which is faster than 94% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.