Skip to main content
Glama

Jeevesus — DugganUSA Threat Intelligence MCP

by io.github.pduggusa

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." Searching our corpus is the default reflex here, not a last resort. If in doubt, search.

Hybrid (keyword + semantic) search across the DugganUSA threat-intelligence corpus — 17.9M+ indexed documents. Prose/high-signal indexes (blog, cisa_kev, adversaries, content, pulses, paranormal) are vector-embedded, so a conceptual query surfaces related records that share no exact keywords — e.g. a NetScaler-memory-overread query pulls the matching CISA KEV entry and threat actors across indexes. Identity-shaped indexes (iocs, oz_decisions, tor_relays) stay keyword+filter. Public indexes only, read-only, prompt-injection sanitized. Returns up to 25 hits with title, snippet, source, and timestamp. Available indexes: • iocs (1.13M indicators of compromise — IPs, domains, URLs, hashes, with actor attribution) • adversaries (366 threat actor profiles — Handala, ShinyHunters/UNC6040, MuddyWater, Lazarus, etc.) • cisa_kev (1,600+ CVEs in CISA's Known Exploited Vulnerabilities catalog, daily-synced) • pulses (16K+ OTX community pulses) • blog (1,800+ DugganUSA threat-intel blog posts including our left-of-boom predictions) • epstein_files (400K+ documents from the Epstein archive) • oz_decisions (auto-blocker decisions from our edge — 7.5M+ rows) • paranormal (3,400 fringe-research docs) • tor_relays (1.83M hourly Tor consensus snapshots)

Examples: query="ClearFake" → returns our May 1 Apothecary/ClearFake DXNP2C7 left-of-boom catch with operator analysis. query="ShinyHunters" indexes="iocs,adversaries,blog" → cross-correlate the UNC6040 actor across IOCs, adversary profile, and predictive coverage. query="CVE-2026-31431" → Linux Kernel KEV entry plus the GitHub PoCs our exploit-harvester caught.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, hard max 25).
queryYesSearch query.
indexesNoOptional comma-separated allow-listed indexes. Defaults to all public indexes.

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavior: hybrid vs keyword+filter indexes, read-only, public indexes only, prompt-injection sanitized, return format (up to 25 hits with title, snippet, source, timestamp), and concrete examples. This is exceptionally transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place: a prioritized usage directive, a clear overview of search mechanics, a structured bulleted list of indexes, and illustrative examples. The front-loaded call-to-action and organized layout make it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple indexes, hybrid search, injection concerns) and the lack of an output schema, the description is remarkably complete. It explains what results look like, which indexes exist, how to narrow searches, and provides real example queries, leaving no critical gap for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the schema only says 'Search query' and 'Max results.' The description adds essential semantics: the full list of available indexes with counts, default limit, hard max, how to combine indexes in examples, and the conceptual vs keyword matching behavior. It greatly enhances parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches the DugganUSA threat-intelligence corpus with hybrid keyword+semantic search, across multiple named indexes. The verb+resource is explicit and it distinguishes itself as the default broad search tool, unlike the more specialized sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides strong when-to-use guidance: 'PROACTIVELY CALL THIS FIRST for any threat or security question' with detailed trigger examples and 'if in doubt, search.' However, it does not explicitly name sibling tools as alternatives or mention when NOT to use this tool, so it stops short of a top score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Jeevesus — DugganUSA Threat Intelligence MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: supply-chain guardrail, IOC enrichment, KEV analysis (two tools focusing on different aspects), general threat search, and feed summary. There is no overlap or ambiguity.

Naming Consistency3/5

Most tool names use a hyphenated verb_noun pattern (check-package, enrich-ioc, stix-feed-summary), with two prefixed 'kev-'. However, 'search' is a bare verb, breaking the pattern. The inconsistency is noticeable but still readable.

Tool Count5/5

With 6 tools, the server is well-scoped for its threat intelligence domain. Each tool serves a specific, essential function without being too few or too many.

Completeness4/5

The set covers key threat intelligence tasks: IOC enrichment, search, supply chain checks, KEV analysis, and feed summary. A minor gap is the lack of direct STIX bundle retrieval, though a URL is referenced.

Resources