# Daystruct (remote · api.daystruct.ai)

Find source-package workflows, inspect live prices and evidence, and connect with a scoped key.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `api.daystruct.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-daystruct-api-daystruct/api.md), [page](https://verifymcp.io/servers/ai-daystruct-api-daystruct/api)

## Channel facts

- Endpoint: `https://api.daystruct.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2677 tokens (~116/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Daystruct MCP server?

Daystruct is a hosted endpoint at https://api.daystruct.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-daystruct-api-daystruct 'https://api.daystruct.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-daystruct-api-daystruct": {
      "url": "https://api.daystruct.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-daystruct-api-daystruct": {
      "type": "http",
      "url": "https://api.daystruct.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-daystruct-api-daystruct]
url = "https://api.daystruct.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-daystruct-api-daystruct": {
      "type": "remote",
      "url": "https://api.daystruct.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-daystruct-api-daystruct --url 'https://api.daystruct.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-daystruct-api-daystruct:
    url: "https://api.daystruct.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-daystruct-api-daystruct": {
      "Transport": "http",
      "Url": "https://api.daystruct.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-daystruct-api-daystruct -t streamable-http -u 'https://api.daystruct.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 75, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “answer_software_questions” rewrote its description, which is the text the model reads
- [security] Tool “check_release_support” rewrote its description, which is the text the model reads
- [security] Tool “check_security_exposure” rewrote its description, which is the text the model reads
- [security] Tool “daystruct_status” rewrote its description, which is the text the model reads
- [security] Tool “get_context_contract” rewrote its description, which is the text the model reads
- [security] Tool “get_entity_evidence” rewrote its description, which is the text the model reads
- [security] Tool “lookup_vulnerability” rewrote its description, which is the text the model reads
- [security] Tool “read_recent_evidence_changes” rewrote its description, which is the text the model reads
- [security] Tool “search_entities” rewrote its description, which is the text the model reads
- [security] Tool “select_model” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 74, +1)

- [functional regression] Schema quality: 1752 → 2097
- [functional] New tool “compat_check”
- [functional] New tool “get_compat_verify_kit”

### 2026-09-22 (score 73, +1)

- [security] Tool “discover_daystruct_capabilities” rewrote its description, which is the text the model reads

## MCP tools (23)

### `daystruct_status` (~27 tokens)

Daystruct status and capabilities

Read the public Daystruct manifest: how capabilities are discovered, checked for compatibility and delivered.

### `search_entities` (~119 tokens)

Search Daystruct entities

Deprecated: 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.

Input parameters:

- `capability` (string)
- `databank` (string)
- `lane` (string)
- `limit` (integer)
- `minContextWindow` (integer)
- `modelType` (string)
- `provider` (string)
- `type` (string)

### `get_entity_evidence` (~69 tokens)

Get entity evidence

Deprecated: 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.

Input parameters:

- `entityId` (string, required)

### `get_context_contract` (~71 tokens)

Get a Daystruct context-packet contract

Deprecated: 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.

Input parameters:

- `databank` (string, required)

### `answer_software_questions` (~75 tokens)

Answer software questions

Deprecated: 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.

Input parameters:

- `claims` (array, required)
- `compatibility` (object)

### `check_security_exposure` (~122 tokens)

Check security exposure for a version

Deprecated: 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.

Input parameters:

- `ecosystem` (string)
- `package` (string, required)
- `version` (string, required)

### `lookup_vulnerability` (~244 tokens)

Look up a vulnerability by its identifier

Deprecated: 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.

Input parameters:

- `cve` (string, required)

### `check_release_support` (~116 tokens)

Check whether a release is still supported

Deprecated: 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.

Input parameters:

- `product` (string, required)
- `version` (string, required)

### `select_model` (~189 tokens)

Select a model that meets stated constraints

Deprecated: 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.

Input parameters:

- `capabilities` (array)
- `limit` (integer)
- `maxInputPricePerMillionTokens` (number)
- `maxOutputPricePerMillionTokens` (number)
- `minContextWindow` (integer)
- `provider` (string)

### `read_recent_evidence_changes` (~62 tokens)

Read recent evidence changes

Deprecated: 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.

Input parameters:

- `limit` (integer)

### `compat_check` (~282 tokens)

Check that Daystruct capabilities fit together and fit your project

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

Input parameters:

- `bundle` (string)
- `capabilities` (array)
- `project` (object)
- `verifyReportId` (string)

### `get_compat_verify_kit` (~113 tokens)

Get the local verify script for a resolved set

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

Input parameters:

- `members` (array, required)

### `get_daystruct_validated_guidance` (~70 tokens)

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

Input parameters:

- `databank` (string, required)
- `model` (string, required)
- `taskFamily` (string, required)

### `list_daystruct_guidance_scopes` (~42 tokens)

Find task families and exact tested models with live Frontier guidance for a databank, before requesting that guidance.

Input parameters:

- `databank` (string, required)

### `resolve_task_capabilities` (~97 tokens)

Select relevant capabilities progressively, or request full delivery. Optional task session remembers prior delivery and reported results; selection never executes or acquires a capability.

Input parameters:

- `bundle_id`
- `capabilities` (array)
- `delivery` (string)
- `include_repeat` (boolean)
- `intent` (string)
- `limit` (integer)
- `request_id` (string)
- `session_id` (string)

### `create_task_session` (~65 tokens)

Start compact task context with optional capability steps and dependencies. Requires read and requests:write. No conversation or reasoning trace is stored.

Input parameters:

- `current_stage` (string)
- `intent` (string, required)
- `request_id` (string, required)
- `steps` (array)

### `record_task_event` (~99 tokens)

Report viewed, called, succeeded, failed or skipped capability status, or task stage. Usage and outcomes remain client-reported.

Input parameters:

- `capability` (string)
- `current_stage` (string)
- `reported_cost_usd` (number)
- `reported_tool_turns` (integer)
- `request_id` (string, required)
- `session_id` (string, required)
- `summary` (string)
- `type` (string, required)

### `get_task_session` (~43 tokens)

Read compact task context or preview the next ready capabilities without consuming them or extending the session TTL.

Input parameters:

- `next` (boolean)
- `session_id` (string, required)

### `close_task_session` (~50 tokens)

Close a task with its reported outcome and compact summary.

Input parameters:

- `outcome` (string, required)
- `request_id` (string, required)
- `session_id` (string, required)
- `summary` (string)

### `search_daystruct_library` (~66 tokens)

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

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `scope` (string)

### `resolve_daystruct_bundle` (~52 tokens)

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

Input parameters:

- `id` (string, required)

### `discover_daystruct_capabilities` (~213 tokens)

Find available Daystruct capabilities using a task sentence or tool name. Query searches return up to eight ranked compact descriptors, matched terms, requirements, limitations, prices and profile links; meta.matched and fullResults expose truncation. Inspect a selected capability by reference for its full contract before requesting help. Provider availability is not proof a task will succeed. Licensing filters narrow the list to source packages whose licensing evidence matches; entries with no licensing evidence are excluded rather than assumed to pass, and a filtered list returns summary licensing only. Read a capability's profile for its full receipt. Licensing findings are evidence against a configured policy, not legal advice.

Input parameters:

- `bundleMembers` (string)
- `licenseEvidence` (array)
- `licensePolicyState` (array)
- `licenseReciprocal` (string)
- `licenseSpdx` (array)
- `licenseStatus` (array)
- `licenseUnresolved` (string)
- `query` (string)
- `reference` (string)

### `prepare_daystruct_capabilities` (~69 tokens)

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

Input parameters:

- `references` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-daystruct-api-daystruct/api#diagnostics

## Score history

- 2026-10-04: 78
- 2026-10-03: 78
- 2026-10-02: 77
- 2026-10-01: 77
- 2026-09-30: 76
- 2026-09-29: 76
- 2026-09-28: 75
- 2026-09-27: 75
- 2026-09-26: 75
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 69
- 2026-09-10: 68
- 2026-09-09: 68

## Common questions

### What is the Daystruct MCP server?

Daystruct is an MCP server listed in the public MCP registry as ai.daystruct.api/daystruct. Find source-package workflows, inspect live prices and evidence, and connect with a scoped key. This page covers its hosted endpoint (https://api.daystruct.ai/mcp).

### Is the Daystruct MCP server safe to use?

Daystruct scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Daystruct MCP server expose?

Daystruct exposes 23 tools: daystruct_status, search_entities, get_entity_evidence, get_context_contract, answer_software_questions, and 18 more. Their descriptions and schemas cost roughly 2,355 tokens of context every time the server is loaded.

### Does the Daystruct MCP server require authentication?

No. We connected to Daystruct without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Daystruct MCP server still maintained?

Daystruct is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.daystruct.ai/mcp
- Website: https://api.daystruct.ai/integrations/source-packages
- Changelog RSS feed: https://verifymcp.io/servers/ai-daystruct-api-daystruct/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-daystruct-api-daystruct/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-daystruct-api-daystruct/api