mocop
Browse · Docs · Guide · Analyze

daystruct

MCP server by Daystruct · mcp

First confirm the user's intended outcome and target project/environment from existing context before pricing or acquisition; ask if unclear. Without a project, continue public contract/readiness evaluation, or a disposable synthetic demo only if explicitly requested. Do not invent a manifest or force acquisition. Discover the current authenticated tools/list and schemas; Card images: every Source, Data and Memory card has a static image of its Daystruct card (custom artwork if set, otherwise its network artwork). Results carry card.imageUrl and card.pageUrl. When you introduce, use, update or report on a specific card, show its image once with get_daystruct_card_image (pass the card ID, never a guessed name) if your client displays images; otherwise give its name and link, and never say an image was shown when it was not. Images are optional, free and never needed to use a capability. Anonymous clients may omit acquisition tools and the account tools for Data and Memory cards (list_d…

Endpoint: https://api.daystruct.ai/mcp

Verification: observed. Source: crawl.

Capabilities (28)

  • daystruct_status
  • search_entities
  • get_entity_evidence
  • get_context_contract
  • answer_software_questions
  • check_security_exposure
  • lookup_vulnerability
  • check_release_support
  • select_model
  • read_recent_evidence_changes
  • compat_check
  • get_compat_verify_kit
  • get_daystruct_validated_guidance
  • list_daystruct_guidance_scopes
  • plan_project_development
  • get_daystruct_account
  • resolve_task_capabilities
  • create_task_session
  • record_task_event
  • get_task_session
  • close_task_session
  • search_daystruct_library
  • resolve_daystruct_bundle
  • discover_daystruct_capabilities
  • prepare_daystruct_capabilities
About · Contact · Privacy