Contradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt.
Scored across 4 tools
Each tool serves a distinct purpose: feed_status retrieves feed-level snapshots, verify_receipt checks receipt integrity, verify_record verifies a single feed record, and verify_subject performs independent subject checks. No functional overlap.
Three tools follow the verb_noun pattern (verify_*), but feed_status is a noun_noun phrase, breaking consistency. All use lowercase with underscores, which is acceptable.
Four tools are well-scoped for a verification server covering feed status, receipt verification, record verification, and subject verification. No unnecessary tools.
The set covers the core verification lifecycle: checking feed status, verifying records and subjects, and validating receipts. Missing a tool for listing feeds or retrieving specific receipts, but not critical.
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'.
Inputs: slug (required).
Recompute + verify a verification receipt's hash-chain (proves the verification is unaltered since its as-of date). Pass the receipt id.
Inputs: id (required).
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.
Inputs: record (required), feed.
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.
Inputs: name, ticker.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
Business-published entity records with confirmation dates: look up, page feeds, check claims.
Signed, versioned ledger of standing instructions with intake contradiction diffs.
Market evidence with receipts: every claim resolves to a real stored record you can fetch back.
Add one secure layer between your agents and this server.