Local MCP capabilities provider for Expo
Nothing to run from here
Jeevesus — DugganUSA Threat Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
check-package: block malicious npm/PyPI deps before your AI agent installs them. Free, no key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http jeevesus-dugganusa-threat-intelligence-mcp https://analytics.dugganusa.com/api/v1/mcp
# 2 — ask your agent for something these tools do
# search, enrich-ioc, stix-feed-summary and 4 more
Jeevesus — DugganUSA Threat Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PDAll 3 servers
pduggusa3 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http jeevesus-dugganusa-threat-intelligence-mcp https://analytics.dugganusa.com/api/v1/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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. Security topics ONLY — do not use this for general programming, documentation or web questions (e.g. "rea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query. |
| indexes | string | no | Optional comma-separated allow-listed indexes. Defaults to all public indexes. |
| limit | integer | no | Max results (default 10, hard max 25). |
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. Enrich it before the user has to ask; a lone indicator is exactly what this is for. Look up a single indicator of compromise (IP, domain, URL, or hash) in the DugganUSA corpus and return everything we know about it: threat type, malware family, s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| indicator | string | no | The indicator to enrich (IP, domain, URL, or hash). |
| value | string | no | Alias of indicator. Either field works. |
| type | string | no | Optional type hint. Default auto-detect. |
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 shape report on the DugganUSA STIX 2.1 threat feed for a chosen lookback window (1-7 days). Returns total indicator count, top malware families, top source feeds, type breakdown (ip/domain/u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Lookback window in days (1–7). Default 1. |
CALL before quoting what an AI model or an agent session costs, or when a usage report needs dollars — prices are dated and copied from each provider's own pricing page, never from memory. Returns the per-1M-token USD rates for a model (input, output, and for Anthropic models the 5-minute and 1-hour cache write, cache read and fast-mode rates), the date the provider page was checked, and the page
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | no | Model id, e.g. "claude-opus-5-5", "gpt-4o-mini", "gemini-2.5-flash". Omit to list all priced models. |
| input_tokens | integer | no | — |
| output_tokens | integer | no | — |
| cache_read_tokens | integer | no | — |
| cache_write_5m_tokens | integer | no | — |
| cache_write_1h_tokens | integer | no | — |
| fast | boolean | no | Anthropic fast mode (premium rates). |
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. Vendor / product risk matrix built from CISA's Known Exploited Vulnerabilities (KEV) catalog — where real, confirmed in-the-wild exploitatio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor | string | no | Optional vendor or product name (e.g. "Adobe", "Citrix", "SharePoint", "ColdFusion"). Omit for the top-vendor risk ranking. |
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." Does in-the-wild exploitation risk STICK to proven products, or SPREAD to new ones? Analyzes CISA KEV: correlates each product's historical known-exploited count against its RECENT KEV additions (Spearman rho), and sp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Recent-window size in days (30-720). Default 180. |
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. This is the runtime defense against slopsquatting / HalluSquatting / hijacked-package attacks — an AI agent about to run npm install or pip install, or a CI pre-install hook, calls this FIRST and blocks on a hit. Returns
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm or pypi. |
| name | string | yes | The package name to check. |
| version | string | no | Optional exact version for version-aware checking. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Jeevesus — DugganUSA Threat Intelligence or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Jeevesus — DugganUSA Threat Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.