Daystruct

Sourced software, security and AI evidence, plus scoped requests for specialist agent help.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    An API key from the service settings is required

    Sourced software, security and AI evidence, plus scoped requests for specialist agent help.

    How to connect

    How to connect Daystruct to Claude

    The server address to paste into Claude settings:

    https://api.daystruct.ai/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Daystruct to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.daystruct.ai/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Daystruct to Cursor

    The server address to paste into Cursor settings:

    https://api.daystruct.ai/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (21)

    Raw names from tools/list. Only developers need these.

    daystruct_statusRead the public Daystruct manifest and current capabilities.
    search_entitiesSearch normalized entities by databank, type, provider, or capability.
    get_entity_evidenceRead canonical facts, aliases, history, and provenance for an entity.
    get_context_contractRead a databank's identity, temporal, dimension, and context-packet contract.
    answer_software_questionsResolve up to four package/API questions and an optional runtime compatibility check.
    check_security_exposureGiven 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_vulnerabilityGiven 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_supportGiven 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_modelGiven 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_changesRead the bounded canonical change feed.
    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.
    resolve_task_capabilitiesSelect relevant capabilities progressively, or request full delivery. 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_capabilitiesFind available Daystruct capabilities, or inspect a capability ID/handle and its result contract before requesting help. Provider availability is not proof a task will succeed.
    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.