What are the capabilities of the Keryx MCP server and what data sources does it use for research?
9/22/2026, 6:18:50 PM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "What are the capabilities of the Keryx MCP server and what data sources does it use for research?"
Identified 2 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified source(s)
Recalled 26 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 1/1 positive proposal(s): 1 cached + 0 fresh, predicting 2/2 claim(s) above the evidence floor with $0.000000/$0.010000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.
First-party Keryx engineering notes (full text, 3071 bytes) directly describe Keryx's paid research job mechanics — quoting, journaling purchases, resuming jobs — which is the closest available source to the MCP server's research capabilities and data-source handling. Reputation 47/100 with 8 citations on this subject; cached so free to reuse. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Full-text (9316 bytes) discussion of MCP-powered 'capabilities' in agent-usable apps; the only candidate whose preview explicitly touches MCP capability design, so it can inform claim 0 about what an MCP server can expose. Cached, so free; past runs never cited it, hence modest value. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Cached abstract on x402 as an agent payment rail — relevant background for how a Keryx MCP research server would pay for and pull external data sources (claim 1). Reputation 33/100 with one prior citation; free reuse, so worth including as supporting context. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).
Cached abstract only covers USDC onchain settlement speed; it says nothing about Keryx MCP server capabilities or its research data sources. Low reputation (11/100) and no target claim is supported by the preview.
Abstract is about batched nanopayment economics, not MCP server capabilities or Keryx's research data sources. No claimIndex is supported by the preview.
Generic idempotency-key advice for retries; unrelated to Keryx MCP capabilities or its data sources. Preview supports neither claim.
Gardening content, entirely off-topic for Keryx MCP server capabilities or research data sources.
Vintage console repair; no connection to MCP server capabilities or Keryx research sources.
High-reputation source (100/100) but the abstract is about fraud rates at AI startups, not MCP server capabilities or Keryx's research data sources. No target claim supported.
About running AI agents against Ethereum protocol code; tangential to agent tooling but does not describe Keryx MCP capabilities or its research data sources. Preview supports neither claim.
High-reputation outlet, but the abstract concerns a local crypto-mining/data-center moratorium, unrelated to Keryx MCP capabilities or research data sources.
Metadata-only (0 plaintext bytes) with no preview substance; cannot establish anything about Keryx MCP capabilities or data sources, and would require payment for a title alone.
Metadata-only title about local computer-use agents; no preview content on MCP server capabilities or Keryx research sources, so not worth the toll.
Metadata-only and about low-risk DeFi on Ethereum; no bearing on Keryx MCP server capabilities or its research data sources.
A 2022 corporate rebuttal about proprietary trading; unrelated to MCP server capabilities or Keryx research data sources.
Russian crypto regulation news; no relevance to Keryx MCP capabilities or its research data sources.
CoinDesk has 0 citations on this subject; the abstract is about Visa stablecoin settlement data and lending, not MCP server capabilities or Keryx research sources.
Esoteric mysticism; wholly unrelated to Keryx MCP server capabilities or research data sources.
SpaceX AI data-center speculation; no connection to Keryx MCP capabilities or its research data sources.
Cached abstract benchmarks x402 settlement latency on Arc; it does not describe Keryx MCP server capabilities or which data sources it uses. No target claim supported.
Abstract covers x402 settlement timing only; unrelated to MCP server capabilities or Keryx's research data sources.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Keryx Engineering (first-party) — Recovering a Keryx paid research job (free) — S1
Sub-claim "What are the capabilities of the Keryx MCP server?": 10% covered — The supplied first-party passage describes a Keryx buyer client for quoting, buying, and recovering a paid research job, but it does not identify or describe a Keryx MCP server or its capabilities. This is only topical context around Keryx research-job tooling, not an answer about an MCP server.
Sub-claim "What data sources does the Keryx MCP server use for research…": 0% covered — No supplied passage names any data sources used by a Keryx MCP server for research. The excerpt covers payment, journaling, and resume mechanics of a buyer client, not research data sources.
Both sub-claims are essentially uncovered, but none of the skipped sources plausibly fills the gap: they concern unrelated topics such as x402 payments, SaaS/MCP capabilities generally, stablecoins, idempotency, gardening, retro consoles, fraud, Ethereum agents, crypto regulation, and esoteric cosmology. None is a Keryx MCP server documentation or data-source reference, so buying them would not improve coverage. Remaining budget is $0.01, but no affordable skipped source is relevant.
Final check — "What are the capabilities of the Keryx MCP server?": 0% assessed
Final check — "What data sources does the Keryx MCP server use for research…": 0% assessed
Final coverage assessment — The supplied source (S1) is a first-party engineering note about the Keryx buyer client's paid research job recovery workflow. It describes quoting, buying, journaling, and resuming a research job, but it does not describe an 'MCP server' or its capabilities, nor does it list the data sources used for research. The only data-source-adjacent content is a link to a research-package.ts file, which is a code reference, not an enumerated list of research data sources. Therefore neither sub-claim is answered. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 1 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Below reward gate — S1 supports claim 1 at 10%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”
Below reward gate — S1 supports claim 1 at 10%: “The buy command obtains a fresh quote, checks the payment policy again, writes a durable job journal, signs once and submits once.”
Below reward gate — S1 supports claim 2 at 10%: “Implementation and usage references at the documented revision: - https://github.com/tang-vu/keryx/blob/9ea84fa/docs/buyer-agent.md - https:…”
Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.
No citation passed the evidence gate — the $0.010000 citation pool stays unspent; settled access tolls still stand.
Drafted answer citing 0 source(s)
Confidence: Low — no citation passed the evidence gate.
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Payouts to cited creators appear here.
The provided source does not describe an "MCP server" named Keryx; it describes an independent Keryx buyer client that separates quoting, buying and recovering a research job. Its documented capabilities are: sending an unsigned quote request and validating the returned payment challenge; obtaining a fresh quote, re-checking the payment policy, writing a durable job journal, and signing and submitting once via the buy command; and, after a connection failure or process restart, resuming with the same job directory by sending only GET requests for the original job without signing a new authorization or replaying a purchase. It also uses the caller's already-funded wallet and does not automatically fund or deposit for it. Regarding data sources used for research, the supplied passages do not identify any research data sources; the only references given are implementation and usage documentation links at the documented revision. Therefore the question about the Keryx MCP server's research data sources is unanswered by the provided source.
Evidence ledger — quotes verified before rewards
What are the capabilities of the Keryx MCP server?
0%No reward-qualifying evidence
What data sources does the Keryx MCP server use for research?
0%No reward-qualifying evidence
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.