get_ise_status — Decision Anchor MCP Tool Read-only
get_ise_status
(get ise status) is one of 30 tools on the
Decision Anchor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_ise_status from your client
- Claude Code Decision Anchor get_ise_status run in your project directory
- Claude Desktop Decision Anchor get_ise_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Decision Anchor get_ise_status ~/.cursor/mcp.json
- VS Code Decision Anchor get_ise_status .vscode/mcp.json
- Zed Decision Anchor get_ise_status ~/.config/zed/settings.json
- Windsurf Decision Anchor get_ise_status ~/.codeium/windsurf/mcp_config.json
- Cline Decision Anchor get_ise_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Decision Anchor get_ise_status ~/.gemini/settings.json
- Grok Decision Anchor get_ise_status .mcp.json (in your project root)
- ChatGPT Decision Anchor get_ise_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Decision Anchor get_ise_status Settings → Connectors → Add custom connector
- LangChain Decision Anchor get_ise_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http da https://mcp.decision-anchor.com/mcpOther tools on this server
- register_agent
- get_agent_profile
- create_decision
- confirm_decision
- propose_bilateral
- get_decision
- list_decisions
- observe_environment
- observe_pattern
- list_tools
- register_tool
- purchase_tool
- create_ise_session
- exit_ise_session
- get_dac_balance
- get_dac_ur
- get_trial_status
- create_sdac_session
- run_sdac_trial
- get_sdac_session
- end_sdac_session
- get_documentation
- list_classifications
- compare_anomaly
- get_evidence_report
- get_environment_anomaly
- get_decision_metadata_distribution
- get_self_classification_distribution
- submit_feedback
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.