Servidor MCP de Daystruct

• Nome no registroai.daystruct.api/daystructverificado no registro MCP

O nome no registro fica sob daystruct.ai. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-23
• Ferramentas26
• O servidor se chamadaystruct
• Versão do servidor1.2.0
• Versão do protocolo2025-06-18

Em 2026-10-23 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 87 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 4 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 4 até agora
• Respondeumedindo4 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta117 ms
• Espaço no contexto do agente≈ 6.079 tokensas definições de todas as ferramentas (26), que o agente carrega a cada turno
• Definições das ferramentasB · 85 de 100
• Resultados tipados0 de 26 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 23 de 26

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• daystruct_status

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

• search_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.

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

• get_context_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…

• 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…

• check_security_exposure

  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…

• lookup_vulnerability

  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…

• check_release_support

  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…

• select_model

  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…

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

• compat_check

  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)…

• get_compat_verify_kit

  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…

• get_daystruct_validated_guidance

  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.

• list_daystruct_guidance_scopes

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

• plan_project_development

  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…

• get_daystruct_account

  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…

• resolve_task_capabilities

  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…

• create_task_session

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

• record_task_event

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

• get_task_session

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

• close_task_session

  Close a task with its reported outcome and compact summary.

• search_daystruct_library

  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.

• resolve_daystruct_bundle

  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.

• discover_daystruct_capabilities

  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…

• prepare_daystruct_capabilities

  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…

• get_daystruct_card_image

  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…