Local MCP capabilities provider for Expo
Nothing to run from here
ThreatDown 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.
—
trust score
—
calls last 7d
local
runs on your machine
—
p95 latency
What it does
Every ThreatDown OneView API, plus fleet-wide stale-endpoint, health and seat reports across all
Quickstart
Install it the way its author documents:
1. Download threatdown-mcp.mcpb and open it in Claude Desktop or another client that installs MCP bundles (.mcpb)
2. Its sha256 is 02e0eac78f571cdc2d44493602ba3d40a7a5602b967e140bea7c6dec46dceabb
The full guide: https://github.com/Servosity/msp-skills/releases/download/threatdown-v0.1.3/threatdown-mcp.mcpb
Publishernot claimed
SEAll 84 servers
Servosity84 servers
13 categories
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. This one runs on your machine: your client starts ThreatDown as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Install it the way its author documents:
1. Download threatdown-mcp.mcpb and open it in Claude Desktop or another client that installs MCP bundles (.mcpb)
2. Its sha256 is 02e0eac78f571cdc2d44493602ba3d40a7a5602b967e140bea7c6dec46dceabb
The full guide: https://github.com/Servosity/msp-skills/releases/download/threatdown-v0.1.3/threatdown-mcp.mcpb
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No tool surface on file
This listing has not published its tool list here yet. Nothing is shown here rather than another listing’s tools, which is what this page used to do.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- 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 ThreatDown 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.
The scanner was given this release and could not read it — three attempts, and none of them came back with a source to grade. So there is no letter and no report here: not a withheld one, an unmeasured one. It is sent again when this listing ships a new version or names a source that can be read.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.3.
0.1.3
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 ThreatDown 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.