ti_sources — Midkernel Threat Intel MCP Tool
ti_sources
(ti sources) is one of 6 tools on the
Midkernel Threat Intel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ti_sources from your client
- Claude Code Midkernel Threat Intel ti_sources run in your project directory
- Claude Desktop Midkernel Threat Intel ti_sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Midkernel Threat Intel ti_sources ~/.cursor/mcp.json
- VS Code Midkernel Threat Intel ti_sources .vscode/mcp.json
- Zed Midkernel Threat Intel ti_sources ~/.config/zed/settings.json
- Windsurf Midkernel Threat Intel ti_sources ~/.codeium/windsurf/mcp_config.json
- Cline Midkernel Threat Intel ti_sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Midkernel Threat Intel ti_sources ~/.gemini/settings.json
- Grok Midkernel Threat Intel ti_sources .mcp.json (in your project root)
- ChatGPT Midkernel Threat Intel ti_sources Settings → Connectors → Advanced → Developer mode
- Claude.ai Midkernel Threat Intel ti_sources Settings → Connectors → Add custom connector
- LangChain Midkernel Threat Intel ti_sources pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http threat-intel https://www.midkernel.com/security/app/mcp/threat-intelOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.