suite_status — mitracore — trust layer for agent work MCP Tool
suite_status
(suite status) is one of 5 tools on the
mitracore — trust layer for agent work
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call suite_status from your client
- Claude Code mitracore — trust layer for agent work suite_status run in your project directory
- Claude Desktop mitracore — trust layer for agent work suite_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mitracore — trust layer for agent work suite_status ~/.cursor/mcp.json
- VS Code mitracore — trust layer for agent work suite_status .vscode/mcp.json
- Zed mitracore — trust layer for agent work suite_status ~/.config/zed/settings.json
- Windsurf mitracore — trust layer for agent work suite_status ~/.codeium/windsurf/mcp_config.json
- Cline mitracore — trust layer for agent work suite_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mitracore — trust layer for agent work suite_status ~/.gemini/settings.json
- Grok mitracore — trust layer for agent work suite_status .mcp.json (in your project root)
- ChatGPT mitracore — trust layer for agent work suite_status Settings → Connectors → Advanced → Developer mode
- Claude.ai mitracore — trust layer for agent work suite_status Settings → Connectors → Add custom connector
- LangChain mitracore — trust layer for agent work suite_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mitracore https://rta.lat/mitracore/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 21 October 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.