verified-feed

endpoint

https://verified.dropwatchhq.com/mcp

protocol

streamable-http ·2024-11-05

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is verified-feed live?

Yes — it answered the hub's last check (checked 43m ago). It answered 99% of checks over the last 30 days.

Is verified-feed free to use?

Yes — the hub reached it with no key and no payment.

What tools does verified-feed have?

4 tools: verify_receipt, feed_status, verify_record, verify_subject.

Is verified-feed safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• verify_receipt reads unknown never probed

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

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• feed_status reads unknown 8h ago

  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'.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy
• verify_record reads unknown never probed

  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.

  mcp-tool

  12345678910111213141516

  {
    "type": "object",
    "required": [
      "record"
    ],
    "properties": {
      "feed": {
        "type": "string",
        "description": "Feed slug the record belongs to (used for SLA + receipt scoping)."
      },
      "record": {
        "type": "object",
        "description": "{ id, subject:{ticker?, name?}, claim? }"
      }
    }
  }

  arguments 16 lines copy
• verify_subject reads unknown never probed

  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.

  mcp-tool

  1234567891011

  {
    "type": "object",
    "properties": {
      "name": {
        "type": "string"
      },
      "ticker": {
        "type": "string"
      }
    }
  }

  arguments 11 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• qualify.dropwatchhq.com dreamqualify mcp · 12 tools
• freight.dropwatchhq.com freight-intel mcp · 9 tools
• parceledge.dropwatchhq.com parcel-edge mcp · 7 tools
• abc.dropwatchhq.com distress-abc mcp · 5 tools
• diligence.dropwatchhq.com distress-diligence mcp · 5 tools
• oracle.dropwatchhq.com hobby-market-oracle mcp · 5 tools
• research.dropwatchhq.com research-intel mcp · 5 tools
• filings.dropwatchhq.com sec-intel mcp · 5 tools

27 more sit on this domain. All of them.