Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Daystruct

REMOTE · API.DAYSTRUCT.AI

Discover reusable source, data and memory capabilities; inspect release evidence and compatibility.

Available components

0 this week 82 Trust /100

Last scanned (20 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4023 tokens (~143/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 1% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
    • New tool “acquire_daystruct_package” functional
    • New tool “read_daystruct_package” functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Nov 26 +2
    • HSTS header: fail → pass ▲ security
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “discover_daystruct_capabilities” rewrote its description, which is the text the model reads security
    • Schema quality: 3380 → 3742 ▼ functional
    • New tool “get_daystruct_card_image” functional
  • 23 Oct 26 80
    • “discover_daystruct_capabilities” added an optional parameter “type” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.daystruct.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=daystruct.ai CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 368f8e28473f5e3213dbd56bac438adc
SANs: daystruct.ai, *.daystruct.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.daystruct.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
daystruct.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'none'; base-uri 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.daystruct.ai/mcp Verified 200
http (plaintext) http://api.daystruct.ai/mcp HTTPS enforced 301 https://api.daystruct.ai/mcp
MCP tools · 28 exposed · ~3,161 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
acquire_daystruct_package ~136

Acquire access to an inspected reusable source package at its exact discovered version and digest. With an API key: honors the explicit credit ceiling and key spending limit; repeating acquisition returns the same receipt; then use read_daystruct_package. Without a key, where x402 is enabled: returns x402 PaymentRequired (MCP transport); retry with _meta["x402/payment"] to pay in USDC and receive the artifact. This is not provider task execution or proof of successful integration.

NameTypeReqDescription
digeststringyes–
maxPriceCreditsinteger––
referencestringyes–
versionstringyes–

No output schema declared.

No examples provided.

answer_software_questions ~75

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.

NameTypeReqDescription
claimsarrayyes–
compatibilityobject––

No output schema declared.

No examples provided.

check_release_support ~116

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.

NameTypeReqDescription
productstringyes–
versionstringyes–

No output schema declared.

No examples provided.

check_security_exposure ~122

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.

NameTypeReqDescription
ecosystemstring––
packagestringyes–
versionstringyes–

No output schema declared.

No examples provided.

close_task_session ~50

Close a task with its reported outcome and compact summary.

NameTypeReqDescription
outcomestringyes–
request_idstringyes–
session_idstringyes–
summarystring––

No output schema declared.

No examples provided.

compat_check ~282

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.

NameTypeReqDescription
bundlestring––
capabilitiesarray––
projectobject––
verifyReportIdstring––

No output schema declared.

No examples provided.

create_task_session ~65

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

NameTypeReqDescription
current_stagestring––
intentstringyes–
request_idstringyes–
stepsarray––

No output schema declared.

No examples provided.

daystruct_status ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

discover_daystruct_capabilities ~303

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

NameTypeReqDescription
bundleMembersstring––
categorystring––
deliverystring––
licenseEvidencearray––
licensePolicyStatearray––
licenseReciprocalstring––
licenseSpdxarray––
licenseStatusarray––
licenseUnresolvedstring––
limitinteger––
offsetinteger––
querystring––
referencestring––
typestring––
viewstring––

No output schema declared.

No examples provided.

get_compat_verify_kit ~113

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.

NameTypeReqDescription
membersarrayyes–

No output schema declared.

No examples provided.

get_context_contract ~71

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.

NameTypeReqDescription
databankstringyes–

No output schema declared.

No examples provided.

get_daystruct_account ~74

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_daystruct_card_image ~158

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

NameTypeReqDescription
cardstringyesCard ID (cap_…) or reference (@handle/name)

No output schema declared.

No examples provided.

get_daystruct_validated_guidance ~70

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.

NameTypeReqDescription
databankstringyes–
modelstringyes–
taskFamilystringyes–

No output schema declared.

No examples provided.

get_entity_evidence ~69

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.

NameTypeReqDescription
entityIdstringyes–

No output schema declared.

No examples provided.

get_task_session ~43

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

NameTypeReqDescription
nextboolean––
session_idstringyes–

No output schema declared.

No examples provided.

list_daystruct_guidance_scopes ~42

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

NameTypeReqDescription
databankstringyes–

No output schema declared.

No examples provided.

lookup_vulnerability ~244

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.

NameTypeReqDescription
cvestringyes–

No output schema declared.

No examples provided.

plan_project_development ~144

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

NameTypeReqDescription
checksarray––
contextSourceRevision–––
currentSourceRevision–––
featuresarray––
goalstringyes–
hasContextboolean––
impactobject––
needsarray––
pendingarray––
scopeNeedsDecisionboolean––
stackarray––
stagestringyes–

No output schema declared.

No examples provided.

prepare_daystruct_capabilities ~69

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.

NameTypeReqDescription
referencesarrayyes–

No output schema declared.

No examples provided.

read_daystruct_package ~145

Read a source implementation previously acquired by this account. Returns data.artifact as a JSON string: compute SHA-256 over its exact UTF-8 bytes before parsing, and compare with data.digest and your preselected digest; do not hash the outer envelope or reserialize the inner JSON. Embedded artifact.priceCredits is immutable submitted metadata, not the current acquisition price. Review the source and follow the supplied application handoff in your authorized project. Validate integrated behavior and local adaptations. Downloading never installs or executes code. Needs a key with read; wallet owners re-download over REST with SIGN-IN-WITH-X.

NameTypeReqDescription
referencestringyes–
versionstring––

No output schema declared.

No examples provided.

read_recent_evidence_changes ~62

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.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

record_task_event ~99

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

NameTypeReqDescription
capabilitystring––
current_stagestring––
reported_cost_usdnumber––
reported_tool_turnsinteger––
request_idstringyes–
session_idstringyes–
summarystring––
typestringyes–

No output schema declared.

No examples provided.

resolve_daystruct_bundle ~52

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

resolve_task_capabilities ~156

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

NameTypeReqDescription
bundle_id–––
capabilitiesarray––
deliverystring––
include_consideredboolean––
include_repeatboolean––
intentstring––
limitinteger––
maxPriceCreditsinteger––
request_idstring––
session_idstring––

No output schema declared.

No examples provided.

search_daystruct_library ~66

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.

NameTypeReqDescription
limitinteger––
querystringyes–
scopestring––

No output schema declared.

No examples provided.

search_entities ~119

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.

NameTypeReqDescription
capabilitystring––
databankstring––
lanestring––
limitinteger––
minContextWindowinteger––
modelTypestring––
providerstring––
typestring––

No output schema declared.

No examples provided.

select_model ~189

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.

NameTypeReqDescription
capabilitiesarray––
limitinteger––
maxInputPricePerMillionTokensnumber––
maxOutputPricePerMillionTokensnumber––
minContextWindowinteger––
providerstring––

No output schema declared.

No examples provided.

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.

remote · api.daystruct.ai

# add to Claude Code
claude mcp add --transport http ai-daystruct-api-daystruct 'https://api.daystruct.ai/mcp'
Common questions

What is the Daystruct MCP server?

Daystruct is an MCP server listed in the public MCP registry as ai.daystruct.api/daystruct. Discover reusable source, data and memory capabilities; inspect release evidence and compatibility. This page covers its hosted endpoint (https://api.daystruct.ai/mcp).

Is the Daystruct MCP server safe to use?

Daystruct scores 82 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 28 tools: daystruct_status, search_entities, get_entity_evidence, get_context_contract, answer_software_questions, and 23 more. Their descriptions and schemas cost roughly 3,161 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Daystruct MCP server?

VerifyMCP ran 13 checks on Daystruct, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.