get_registrations_expiring — deawatch MCP Tool Read-only
get_registrations_expiring
(get registrations expiring) is one of 5 tools on the
deawatch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_registrations_expiring from your client
- Claude Code deawatch get_registrations_expiring run in your project directory
- Claude Desktop deawatch get_registrations_expiring ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor deawatch get_registrations_expiring ~/.cursor/mcp.json
- VS Code deawatch get_registrations_expiring .vscode/mcp.json
- Zed deawatch get_registrations_expiring ~/.config/zed/settings.json
- Windsurf deawatch get_registrations_expiring ~/.codeium/windsurf/mcp_config.json
- Cline deawatch get_registrations_expiring ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI deawatch get_registrations_expiring ~/.gemini/settings.json
- Grok deawatch get_registrations_expiring .mcp.json (in your project root)
- ChatGPT deawatch get_registrations_expiring Settings → Connectors → Advanced → Developer mode
- Claude.ai deawatch get_registrations_expiring Settings → Connectors → Add custom connector
- LangChain deawatch get_registrations_expiring pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http deawatch https://deawatch.artificl.us/mcpOther tools on this server
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.