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