Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Description from the maker (original English)
Every ThreatDown OneView API, plus fleet-wide stale-endpoint, health and seat reports across all
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
THREATDOWN_CLIENT_ID, THREATDOWN_CLIENT_SECRET, THREATDOWN_OAUTH_SCOPE, THREATDOWN_BASE_URL, THREATDOWN_TOKEN_URL, THREATDOWN_USER_AGENT, THREATDOWN_MCP_READ_ONLY, THREATDOWN_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILEValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
THREATDOWN_OAUTH_SCOPE envTHREATDOWN_BASE_URL envTHREATDOWN_TOKEN_URL envTHREATDOWN_USER_AGENT envTHREATDOWN_MCP_READ_ONLY envPRINTING_PRESS_CLIENT_PROFILE envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account servosity, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: THREATDOWN_CLIENT_ID, THREATDOWN_CLIENT_SECRET, THREATDOWN_MCP_HTTP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 14 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: Mirobody, FHIR MCP Server, Google Health MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Unofficial. Community-built Claude Code Skill and MCP server for the ThreatDown
API. Not affiliated with, endorsed by, or sponsored by Malwarebytes Inc.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Every ThreatDown OneView API, plus fleet-wide stale-endpoint, health and seat reports across all your sites, and guarded isolate/scan/restore jobs. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build checks a token, but it
predates the fix release's request size and time limits. The MCP tools can
also make changes with your credentials. Use the default stdio transport. If
you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the ThreatDown skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register threatdown-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add threatdown-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add threatdown-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs threatdown-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
.mcpbDownload ThreatDown MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ThreatDown release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
/plugin marketplace add Servosity/msp-skills
/plugin install threatdown@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the ThreatDown Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.ps1 | iex. Then authenticate per the README and runthreatdown-cli --helpto explore.
The same prompt works in any agent that can run shell.
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.sh)
The installer drops both threatdown-cli (the CLI) and threatdown-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
threatdown-cli --version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatdown/install.ps1 | iex
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update threatdown@msp-skills.
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/threatdown --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/threatdown --force
Hermes speaks MCP natively, so it can also use the threatdown-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the threatdown skill from https://github.com/servosity/msp-skills/tree/main/skills/threatdown. The skill defines how its required CLI (
threatdown-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Set the credentials the CLI needs (from your ThreatDown portal):
export THREATDOWN_CLIENT_ID=<value>
export THREATDOWN_CLIENT_SECRET= threatdown-cli doctor
Keep both variables set for every process that runs the CLI or the MCP server (the MCP install puts them in your client's env block). doctor exchanges them for a token and probes it with an authenticated call to OneView's account endpoint (its Credentials row), so a wrong secret shows there as a credentials error with HTTP 401. Only the minted token is cached, in the CLI's credentials.toml, and a process without the variables does not reuse it. To store the pair instead, export both variables once and run threatdown-cli auth login --client-id : it saves that client ID and the secret from the environment in that file until threatdown-cli auth logout, and the secret never appears on a command line.
| Question your MSP keeps asking | Command |
|---|---|
| Which endpoints haven't checked in for 24 hours, across every site? | threatdown-cli fleet stale --hours 24 --agent |
| Which customer site needs attention first? | threatdown-cli fleet health --agent |
| Which sites are over- or under-allocated on seats, and which subscriptions are expiring? | threatdown-cli seats reconcile --agent |
| Which scans or isolations never ran? | threatdown-cli respond pending --since 7d --agent |
| Which threats hit more than one customer this month? | threatdown-cli threats spread --since 30d --min-sites 2 --agent |
| Which infected or suspicious machine should I contain next? | threatdown-cli threats queue --since 7d --agent |
| Everything about one customer while they're on the phone | threatdown-cli customer report "Acme Corp" --agent |
| Isolate a machine, with a preview first | threatdown-cli respond isolate --host LAPTOP-042 --agent |
threats spread, threats queue and customer report read the local copy, so run threatdown-cli fleet sync first (and again when you want fresh numbers). The respond commands send nothing until you add --confirm.
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
We found no other MCP server for ThreatDown OneView on GitHub as of October 2026. The integrations that do exist, such as the Sumo Logic and Datadog (Crest Data) apps, move OneView data into a SIEM or monitoring tool. A question like "which threats hit more than one of my 40 customers this month" is still a per-site export and a spreadsheet.
This skill resolves every site's account ID for you and syncs sites, endpoints, detections and jobs into a local SQLite mirror with full-text search (search --data-source local). Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like threats spread, threats queue and customer report join detections, endpoints, jobs and sites - work a stateless API wrapper can't do. ThreatDown's own AI features, such as the AI-assisted Security Advisor and AI Detection & Response, work inside the ThreatDown console; this skill complements them by bringing every OneView site into the agent you already use.
ThreatDown OneView answers one site at a time. The Monday question - "which machines went dark since Friday, across all my customers?" - has no single page. ThreatDown's own
Only the beginning is shown; read the rest in the repo