Keryx

Keryx MCP

Inspect a private saved library locally (source candidate)

inspect_saved_literature({backup, baselineBackup?}) validates a caller-supplied personal-bibliography v1 backup and returns aggregate counts for saved records, personal screening, repositories, recorded publication kinds and missing metadata. Output omits private focus, notes and individual paper identities. Missing fields and current paper status remain unknown; counts are not reading, quality or settlement proof. This local tool has no file, network, model, wallet or payment I/O. MCP clients may retain the entire supplied backup, including private notes. See offline inspection usage and limits.

Optional baselineBackup adds aggregate changes from that before snapshot to the backup after snapshot. Exact URLs define retained records; versions are not inferred matches. Metadata, timestamps and personal-state changes stay separate, and no changed values or paper identities enter the result. Both snapshots must validate within their individual 1 MiB limits. Clients may retain both full inputs. Omitting baselineBackup keeps the existing single-backup response.

Export private saved literature locally (source candidate)

export_saved_literature({backup, format, screening?, paperUrls?}) converts a caller-selected personal-bibliography v1 backup to BibTeX, RIS or CSL-JSON. It validates the full 1 MiB bounded JSON before selecting saved screening states, keeps exact versions and provenance, and omits private review title, question, notes and decisions. Optional paperUrls selects at most 50 unique exact saved URLs in caller order; an empty array exports no references. Missing/changed-version URLs refuse the entire export, and screening filters within the selection. No URL is fetched. This local tool has no file, network, model or payment I/O. Your MCP client may retain the entire supplied backup, including private notes. See offline export usage and boundaries.

The CLI bundles the pinned Circle 3.5.0 buyer implementation; its exact inputs are recorded in dist/build-inputs.json. Its application validators use the bundled, security-patched Zod 3 compatibility runtime, retaining existing UTF-16 limits and schema behavior. MCP SDK, its published Zod 4 dependency and viem remain external. The buyer does not auto-install x402's old Zod peer graph. Source builds require the repository's pinned dependencies. Bundled code, modifications and licenses are listed in THIRD-PARTY-NOTICES.txt.

Compare saved receipts locally (source candidate)

compare_saved_research({before, after, matches?, matchingPlan?}) accepts two version-1 research receipt JSON strings, at most 512 KiB each. It verifies both recorded payload checksums and compares exact retained excerpt rows, source versions and reading context. Unique identical targets are paired automatically; explicit one-to-one matches use recorded claim indices. [] leaves all targets unmatched. Alternatively, matchingPlan takes saved keryx-report-matching-v1 JSON (up to 64 KiB), bound to those exact receipt payload checksums in that order. Do not combine it with matches. The result includes a reusable matchingPlan object containing only checksums and target indices, alongside comparison. Missing historical ledgers stay unknown. A checksum is not authenticity, factual support, settlement or proof of improvement; row counts are not independent sources.

This stdio tool uses no network, model, database or payment capabilities. Your MCP client can retain the supplied text and results. For browser-memory-only file inspection and JSON/Markdown/CSV downloads, use /research/compare. API/remote MCP, extension and bot receipt downloads hand off to that local workspace. See the comparison contract for local CLI, matching, limits and export semantics. Production/package availability follows the coordinated release; this source section does not claim an installed version.

Sponsored public research (source candidate)

ask_keryx_sponsored runs hosted sponsored research with no API key, buyer wallet or funding setup. First build the source checkout:

npm install

npm --prefix mcp run build

Configure your MCP client to start the resulting bundle using its absolute path:

{

"mcpServers": { "keryx": { "command": "node", "args": ["/absolute/path/to/keryx/mcp/dist/keryx-mcp.mjs"] } } }

This configuration also works when the MCP client starts from another directory. Explicitly consent to a public question and trial report when calling the tool:

ask_keryx_sponsored({

question: "What evidence supports sodium-ion batteries for grid storage?", publicReport: true, mode: "quick", budget: 0 })

Questions are bounded to 2,000 characters; mode is quick or deep. The optional source budget accepts 0–0.08 USDC, including zero, independently of model/search operating costs. Server quotas, caps and pauses apply. No private task fields are accepted. A timeout or disconnect may leave server work running: there are no automatic retries or automatic paid fallbacks. Quota refusals require waiting before a deliberate new submission. Returned payment evidence keeps planned, pending and settled states distinct.

The separate ask_keryx tool remains the paid buyer path and retains its own wallet, merchant policy and recovery requirements. This addition is a source candidate; package publication and installed availability belong to the parent release and are not claimed here.

The ORIGINAL268 NEXT source candidate adds history_private_jobs_list, history_private_jobs_detail and history_private_jobs_export to both MCP registrations. Current published 0.4.20 does not contain these tools. No new package/version, artifact URL, installed availability or production delivery is claimed. Parent review, focused checks, required CI and exact-source packed MCP acceptance/publication remain required.

In this source checkout, the stdio registration uses an explicit KERYX_API_KEY whose live server key has history:read. It calls only the existing HTTPS POST /api/me/private-jobs, /detail and /export JSON contracts. No wallet private key, buyer wallet, cookie, chat/client label or expected-wallet precondition grants history ownership. The expected wallet can only refuse a mismatch. The remote registration uses the verified request actor and original request-local history revalidator before Db acquisition, after it and after private reading.

These are owner-private responses; an MCP desktop/agent client may retain tool messages. List is a finite exact-payer completed-job scan; detail is an explicit private answer read without public report/share links or automatic research/model submission; export returns bounded JSON metadata with complete, truncated and continuation. Own settled spend, creator rewards and paid creators remain NULL, and missing recorded provenance stays unknown. No research, source fetch, signer, purchase, database mutation, retry or alternate credential is used by these tools. Existing paid tools retain their separate roles.

The source-only CLI adapter is available at scripts/private-job-history.mts:

node --import tsx scripts/private-job-history.mts --help

node --import tsx scripts/private-job-history.mts list --limit 25 node --import tsx scripts/private-job-history.mts detail --id 'prv_<64-lowercase-hex>' node --import tsx scripts/private-job-history.mts export --format csv

The last three commands print private data for the authenticated caller. Supply the history key through the caller's existing private environment; never paste it into flags, URLs or a model prompt. The CLI loads no envfile and uses fixed https://keryx.cc; metadata CSV protects formula-leading text. See source roles, UNRUN fixtures and original268 remaining gates.

evidence_procurement prepares private missing-evidence requests, compares signed provider quotations within an integer quote budget, checks separately signed delivered bytes and retains explicit supporting/refuting reviews. Exported packets can be restored and reassessed on web, API and CLI using the same contract. This proposal tool does not contact providers, fetch sources, execute benchmarks, purchase or reward anyone. Signed quotations confer no payout or source ownership authority; coverage/reviews remain declarations and payment is unobserved. See the workflow and remaining hosted/funded gates.

The source supports optional language: en|vi|pt|pt-BR|es|fr|zh-Hans|de|ja|ko|hi|id|ru|ar on ask_keryx for human-readable presentation only. It is consumed locally after the buyer returns: it is not added to the paid request/body/hash or forwarded as a model-language directive. Omission uses the original question's finite selector; explicit overrides disclose that actual answer language is unrecorded. Serving/output-limit notices share the API/remote MCP catalogue. The original answer/excerpts, structured result, custody/recovery path, payment/settlement authority text, canonical USDC amount and receipts stay unchanged. Package build/publication and actual delivery remain root-owned gates; no live call is required or executed by these source checks. See the exact shared contract and coordinator inputs.

For a new ordinary Arabic answer, put أجب بالعربية. or Answer in Arabic. in question; language: "ar" selects labels only. Stored answers retain their original text and require their existing recorded-language evidence.

App 0.27.60 is the next coordinated candidate for bounded ordinary optimizer replay, presentation-only research/bot labels and default-OFF deadline observation. The read-only idle signing correction joins this cohort after its own CI gates. Candidate identities are stdio/package/Registry 0.4.19, hosted MCP 0.3.17 and Desktop 0.4.17. The unchanged extension payload retains 0.1.4.2. Exact final-source CI, compiled package vectors, artifacts, publication and deployed readback remain required; these numbers are not publication or install proof.

Production app 0.27.59 /513c6fa6 was actually delivered on October12, with hosted MCP 0.3.16 and published npm/Registry 0.4.18. Its compiled idle signing fixture refused unrelated traffic and supplied no four-case acceptance; #274 stays open until the corrected source is delivered and observed. Zotero, privacy and deadline-observer activation retain their explicit holds. No new schema/backfill, schedule, payment or custody authority is granted. Dated notes below retain their original source and delivery evidence.

App0.27.58's iPhone header repair is scoped to the hosted web UI. It retains hosted MCP0.3.15 and stdio/package/Registry0.4.17 tool contracts and identities; existing artifacts keep their original source provenance. No new MCP package is required by this increment. See the surface audit and acceptance record.

The app0.27.57 coordinated candidate selects stdio/package and official Registry 0.4.17, with hosted MCP 0.3.15. Current main adds local draft_check and updates evidence_draft retained excerpts and author-written statements. Their actual runtime inputs changed, so published0.4.16 retains its earlier delivered source rather than representing this candidate. Both tools process caller text; they fetch no source, call no research/provider/storage/payment path, and confer no signing or private-history authority. Imported origin remains unverified.

Exact combined source/CI/build, the actual release bundle bound to the existing private-tool package fixture, initiali