Breaking down: "What tools and data sources does this Keryx MCP server provide access to?"

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 24 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.005000 fetch USDC reserved.

Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Reused cached Keryx Engineering (first-party) — Recovering a Keryx paid research job (free) — S1

Sub-claim "What tools does this Keryx MCP server provide access to?": 10% covered by S1 — S1 describes a buyer client with commands (buy, resume) and a research-job workflow, but never identifies an MCP server or enumerates MCP tools. Only topical context about the Keryx buyer client, not an answer to the MCP tools question.

Sub-claim "What data sources does this Keryx MCP server provide access …": 10% covered by S1 — S1 mentions a research result and links to buyer-agent docs and a research-package module, but does not list or describe any data sources exposed by an MCP server. Topical context only.

Both sub-claims are essentially uncovered (0.1 each). However, none of the skipped sources plausibly address a Keryx MCP server's tools or data sources: they concern USDC settlement, x402, nanopayments, idempotency, gardening, retro consoles, Stripe fraud, Ethereum agents, Kalshi feeds, ontologies, LLM releases, Reachy Mini MCP tools, memory complexity, Coinbase, Russian crypto law, EUR/USDC onchain gap, esoteric cosmology, SpaceX data centers, and x402 latency. The only marginally related item (Hugging Face 'Adding MCP Tools to Reachy Mini') is about a different project's MCP tools, not Keryx, so it would not fill the gap. With remaining budget 0.005, no affordable skipped source would materially raise coverage; buying would be wasteful.

Final check — "What tools does this Keryx MCP server provide access to?": 10% assessed by S1

Final check — "What data sources does this Keryx MCP server provide access …": 10% assessed by S1

Final coverage assessment — The supplied source (S1) is a first-party engineering note about recovering a paid research job in the Keryx buyer client. It describes buyer-side commands (buy, resume), journaling, payment policy, and references buyer-agent documentation and a research-package TypeScript file. It does not enumerate or describe any MCP server tools, nor does it identify data sources exposed by a Keryx MCP server. The question asks specifically about a Keryx MCP server's tools and data sources; the source is topically related to Keryx but does not answer either sub-claim. 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 0%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”

Below reward gate — S1 supports claim 2 at 0%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”

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