Daystruct

Tools

• daystruct_statusRead the public Daystruct manifest: how capabilities are discovered, checked for compatibility and delivered.
• search_entitiesDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Search normalized entities by databank, type, provider, or capability.
• get_entity_evidenceDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Read canonical facts, aliases, history, and provenance for an entity.
• get_context_contractDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Read a databank's identity, temporal, dimension, and context-packet contract.
• answer_software_questionsDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Resolve up to four package/API questions and an optional runtime compatibility check.
• check_security_exposureDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Given a package and the version you are running, return the known vulnerabilities that affect it, worst first, each with the version that fixes it. Advisories whose affected range could not be parsed are returned under undetermined; treat undetermined as unanswered, never as safe.
• lookup_vulnerabilityDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Given a vulnerability identifier such as a CVE, return what is held about it: the affected package and version range, the version that fixes it, severity, and whether it is recorded as known-exploited. Use this when you have an identifier rather than a package you are running. Fields come back as claims carrying their own authority. status 'known' with authority 'exclusive' means Daystruct has evidence for the value; if you hold a different value, treat it as a conflict to resolve. status 'unknown' with authority 'non_exclusive' means Daystruct has no evidence either way -- an absence of evidence, which does not contradict or supersede anything you already know: keep what you independently know, and stay uncertain if you do not. A field returned as null means Daystruct looked and holds nothing for it; no other Daystruct tool will have it either. Exploitation status is never reported false from a partial catalog.
• check_release_supportDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Given a product and version, return whether that release line is supported, in security-fix-only maintenance, or past end of life, with the dates behind the answer and the cycles you could upgrade into. A line with no published end-of-life returns undetermined rather than supported.
• select_modelDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Given a need -- minimum context window, required capabilities, a price ceiling -- return the models that satisfy it, cheapest input price first, with the corroboration behind each record so you can judge how well-sourced it is. Prices are per million tokens. A model with no published price is returned under undetermined rather than excluded, so an unpriced model never reads as a disqualified one. This returns candidates and their evidence, not a recommendation.
• read_recent_evidence_changesDeprecated: this evidence tool is no longer refreshed and will be removed on or after 2026-12-31. For building, use discover_daystruct_capabilities and compat_check. Read the bounded canonical change feed.
• compat_checkResolve Daystruct capabilities to exact versions that fit each other, or get the exact constraint that broke with suggested alternatives. Send the project manifest by default: project.runtime (the node or python version the project runs), project.platform, and the project's package-lock.json (or an installed name->version map) plus the dependency sections of package.json. That makes the answer project-checked rather than bundle-only. Never send source code or other files; only those fields are read and nothing is stored. The result's scope says what it covers (bundle-only, project-checked, project-verified). Its state is compatible, except when you pass bundle (for example security-scanners@latest-verified) instead of capabilities: then it is verified, because that exact set passed its integration suite, and the result names the run and the environment it ran in. Affected versions are refused and listed under advisoriesAvoided; a deprecated version is chosen only when nothing else fits and is named in notes. To reach project-verified, fetch the verify kit for the resolved members, show the user the report the script prints, send it only with the user's agreement (--send), and pass the returned report id as verifyReportId.
• get_compat_verify_kitReturn the files of the local verify step for exact source members from compat_check: a script, its plan, and the interface conformance suites. Write them to a scratch directory and run `node daystruct-verify.mjs` from the user's project; it runs the members' own tests and conformance suites and prints a report of counts and versions only. It sends nothing unless run with --send, which needs the user's agreement. Native members cannot be verified locally.
• get_daystruct_validated_guidanceRetrieve reviewed Frontier guidance scoped to an exact databank, task family and tested model. Returns only live, unexpired promotions and their evidence limits; never private test fixtures.
• list_daystruct_guidance_scopesFind task families and exact tested models with live Frontier guidance for a databank, before requesting that guidance.
• plan_project_developmentGet a small stage-specific capability selection and concrete next actions from a caller-approved project projection. Keep source and full snapshots local. Caller-reported outcomes are not verified execution. Does not acquire, execute, store project context or send reminders.
• get_daystruct_accountRead the connected key's account: available and reserved credits, the key's scopes, its per-call spending limit (null means none) and where the owner adds credits. Check this before a paid call, show the user the price first, and tell them what was spent afterwards. Read-only; never returns the key.
• resolve_task_capabilitiesSelect relevant capabilities progressively, or request full delivery. Charges the published resolve price (/api/v1/pricing) to a key with read + requests:write; data.economics reports chargedCredits and creditsRemaining. Optional maxPriceCredits caps this call. Optional task session remembers prior delivery and reported results; selection never executes or acquires a capability.
• create_task_sessionStart compact task context with optional capability steps and dependencies. Requires read and requests:write. No conversation or reasoning trace is stored.
• record_task_eventReport viewed, called, succeeded, failed or skipped capability status, or task stage. Usage and outcomes remain client-reported.
• get_task_sessionRead compact task context or preview the next ready capabilities without consuming them or extending the session TTL.
• close_task_sessionClose a task with its reported outcome and compact summary.
• search_daystruct_librarySearch this account's saved or owned capabilities and bundles. Returns a small shortlist; saving does not acquire, execute or grant access to source. Inspect a selected profile before use.
• resolve_daystruct_bundleRead a saved, owned or public bundle with pinned source versions and current member availability. Returns a composition plan, not an execution or purchase. Each capability retains its usage terms.
• discover_daystruct_capabilitiesBrowse every public Daystruct capability without an account, or search using a task sentence or tool name. Lists default to eight compact descriptors. Set limit (1-100) and offset to follow meta.nextOffset until null; view: full returns up to 100 full metadata records per page. Category and delivery filters narrow the list. Responses carry live freshness, requirements, limitations, prices and profile links; inspect a reference for its full contract before using it. Provider availability is not proof a task will succeed. Licensing filters exclude entries with no licensing evidence; read a profile for its full receipt. Licensing findings are evidence against a configured policy, not legal advice. Private Data and Memory cards never appear here; list your account's cards with list_daystruct_cards. Each result's card field holds its image reference; show it with get_daystruct_card_image when you introduce that capability.
• prepare_daystruct_capabilitiesGroup up to six discovered capability IDs into a plan with each profile and delivery instructions. Missing entries remain explicit. Does not acquire, execute, check combined compatibility or charge credits. Your agent can combine these pieces with Daystruct knowledge and verify the resulting task.
• get_daystruct_card_imageGet the image of a Daystruct card (Source, Data or Memory) to show the user beside your text when you introduce, use, update or report on that card. Pass the card's ID (cap_…) or exact reference, never a guessed name. Returns PNG image content plus the card's name, type and page link; if your client cannot display images, show the name and link instead and do not say an image was shown. Public cards need no key; private cards need a key on the owning account. Show a card once per response, not on every repeated step. Never required to use a capability and never charged.

Updated：2026-10-29 (tools/list verified)

Configure in Claude / Cursor

{
  "mcpServers": {
    "remote-ai-daystruct-api-daystruct": {
      "type": "http",
      "url": "https://api.daystruct.ai/mcp"
    }
  }
}