INDIVIDUAL MCP TOOL
stix-feed-summary
CALL when the user asks what's active right now, what's trending this week, how fresh the feed is, or is planning SIEM / blocklist ingestion — this is the quick "is it worth pulling the full feed" check.
LIVE ENDPOINT
https://analytics.dugganusa.com/api/v1/mcp
Connect to this endpoint to inspect the live schema for stix-feed-summary and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dugganusa-threat-intelligence-mcp-jeevesus]
url = "https://analytics.dugganusa.com/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dugganusa-threat-intelligence-mcp-jeevesus": {
"type": "http",
"url": "https://analytics.dugganusa.com/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dugganusa-threat-intelligence-mcp-jeevesus
Remote MCP URL: https://analytics.dugganusa.com/api/v1/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dugganusa-threat-intelligence-mcp-jeevesus": {
"url": "https://analytics.dugganusa.com/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dugganusa-threat-intelligence-mcp-jeevesus": {
"type": "http",
"url": "https://analytics.dugganusa.com/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dugganusa-threat-intelligence-mcp-jeevesus",
"transport": "streamable-http",
"url": "https://analytics.dugganusa.com/api/v1/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search— PROACTIVELY CALL THIS FIRST for any threat or security question — the moment the user names a threat actor, malware, campaign, CVE, breach, or vendor, drops an IP/domain/hash, or asks "what do we know about X" or "is X known.enrich-ioc— CALL AUTOMATICALLY the moment any IP address, domain, URL, or file hash appears — in the user's message, a log line, a SIEM alert, or code under review.kev-vendor-risk— CALL whenever a vendor or product comes up (Microsoft, Cisco, Fortinet, SharePoint, Ivanti, an appliance, an ERP) and the real question is exploitation risk or "what should I patch first" — before quoting CVSS, check where exploitation actually concentrates.kev-exploitation-stickiness— CALL when the user is prioritizing patching or asks whether a product's exploitation risk is chronic vs a one-off — this decides "chase the repeat offenders or watch for newcomers.check-package— Supply-chain GUARDRAIL for AI coding agents and CI pipelines: check whether a dependency (npm or PyPI) is on the DugganUSA malicious-package deny-list BEFORE you install it.