daystruct_status — Daystruct MCP Tool
daystruct_status
(daystruct status) is one of 23 tools on the
Daystruct
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call daystruct_status from your client
- Claude Code Daystruct daystruct_status run in your project directory
- Claude Desktop Daystruct daystruct_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Daystruct daystruct_status ~/.cursor/mcp.json
- VS Code Daystruct daystruct_status .vscode/mcp.json
- Zed Daystruct daystruct_status ~/.config/zed/settings.json
- Windsurf Daystruct daystruct_status ~/.codeium/windsurf/mcp_config.json
- Cline Daystruct daystruct_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Daystruct daystruct_status ~/.gemini/settings.json
- Grok Daystruct daystruct_status .mcp.json (in your project root)
- ChatGPT Daystruct daystruct_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Daystruct daystruct_status Settings → Connectors → Add custom connector
- LangChain Daystruct daystruct_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http daystruct https://api.daystruct.ai/mcp
Other tools on this server
- 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
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.