Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Blackpoint Cyber CompassOne: tenants, detections, assets, vulnerabilities and a cross-tenant view.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
PRINTING_PRESS_CLIENT_PROFILE, BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, BLACKPOINT_MCP_READ_ONLY, BLACKPOINT_NO_LOCAL_DATA, BLACKPOINT_USER_AGENT, BLACKPOINT_MCP_HTTP_TOKENAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
Trag die leeren Werte ein, bevor du ihn startest.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
BLACKPOINT_BASE_URL envBLACKPOINT_MCP_READ_ONLY envBLACKPOINT_NO_LOCAL_DATA envBLACKPOINT_USER_AGENT envDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto servosity bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: PRINTING_PRESS_CLIENT_PROFILE, BLACKPOINT_API_TOKEN, BLACKPOINT_MCP_HTTP_TOKEN
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.1) kam gestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du MCPB auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, HotCodePush
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Unofficial. Community-built Claude Code Skill and MCP server for the Blackpoint Cyber
API. Not affiliated with, endorsed by, or sponsored by Blackpoint Cyber.
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
CompassOne from the terminal: tenants, detections, assets, vulnerabilities, posture, reports and Cloud Response admin, plus a cross-tenant fleet view of open detections, stale agents and coverage gaps. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Blackpoint Cyber skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register blackpoint-mcp (no JSON editing). |
| ChatGPT (paid plans) | Run installer, host blackpoint-mcp over HTTPS with BLACKPOINT_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token. |
| 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 blackpoint-mcp to mcp.json under the servers key, then pick Agent mode. |
For ChatGPT, run blackpoint-mcp --transport http with BLACKPOINT_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.
Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not self-serve. Host blackpoint-mcp over HTTPS with BLACKPOINT_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md. |
| Google Gemini | Gemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md. |
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 Blackpoint Cyber MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Blackpoint Cyber 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 blackpoint@msp-skills
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Blackpoint Cyber 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/blackpoint/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/blackpoint/install.ps1 | iex. Then authenticate per the README and runblackpoint-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/blackpoint/install.ps1 | iex
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/blackpoint/install.sh)
The installer drops both blackpoint-cli (the CLI) and blackpoint-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
blackpoint-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/blackpoint/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/blackpoint/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 blackpoint@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 remote Microsoft 365 Copilot / Copilot Studio path. 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/blackpoint --force
Inside a Hermes chat session:
/skills install servosity/msp-skills/skills/blackpoint --force
Hermes speaks MCP natively, so it can also use the blackpoint-mcp server directly - same install path, same env vars.
Tell your OpenClaw agent (copy this):
Install the blackpoint skill from https://github.com/servosity/msp-skills/tree/main/skills/blackpoint. The skill defines how its required CLI (
blackpoint-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 Blackpoint Cyber portal):
BLACKPOINT_API_TOKEN=<value> blackpoint-cli doctor
doctor checks config, paths, and API reachability, then sends one authenticated read and reports the credential as valid, rejected (401), scope-limited (403), or pointed at the wrong base URL (404).
| Question your MSP keeps asking | Command |
|---|---|
| Which open detections are oldest across every client? | blackpoint-cli triage --older-than 24h |
| Which devices' agents stopped reporting? | blackpoint-cli stale-agents --days 14 |
| Which customers have no recent scan, no escalation contacts or no posture rating? | blackpoint-cli gaps --scan-days 30 |
| Which exploited CVE affects the most customers? | blackpoint-cli cve-spread --exploited |
| Which tenants have the weakest posture score, and in which NIST function? | blackpoint-cli leaderboard |
| Which travel exceptions have expired or end this week? | blackpoint-cli geo-audit --expiring 7d |
| What does one client look like right now? | blackpoint-cli overview "Acme Dental" |
| What are this client's numbers for the monthly report? | blackpoint-cli client-report "Acme Dental" --since 30d |
The cross-tenant commands (triage, stale-agents, gaps, cve-spread, leaderboard, geo-audit, overview) read the local mirror: run blackpoint-cli fleet-sync first, and again whenever you want fresh numbers. Before the first sync they return an empty list with a hint on stderr. client-report and the endpoint commands call the API live.
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
Most Blackpoint Cyber integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which open detection, across all 40 of my CompassOne tenants, has waited longest?" Every CompassOne detection, asset, vulnerability and scan call is scoped to one tenant, so the live answer is one call per customer.
This skill syncs Blackpoint Cyber into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like triage, gaps and cve-spread join across every tenant's detections, devices, vulnerabilities, scans, contact groups and posture ratings - work a stateless API wrapper can't do.
CompassOne is built tenant by tenant: every detection, asset, vulnerability, scan and report call names one customer tenant (the API's x-tenant-id header), and the portal views follow the same shape. Reviews of Blackpoint for MSPs say the same thing from the operator's side: Flamingo's Blackpoint Cyber review notes reviewers find the partner portal "less polished than the detection engine behind it, with a learning curve on reporting and day-to-day navigation." At 30 or 80 customers, "which fire do I put out first?" and "who has no coverage?" become a tab-by-tab exercise.
This skill closes that gap:
blackpoint-cli triage --older-than 24h lists open detections across all tenants, oldest first, with tenant, age, alert count and ticket status.blackpoint-cli stale-agents --days 14 lists devices across every tenant whose agent has not reported, with Defender status.blackpoint-cli gaps --scan-days 30 flags tenants with no recent completed scan, no or empty escalation contact group, or no posture rating.blackpoint-cli cve-spread --exploited ranks exploited CVEs by tenants and assets affected.blackpoint-cli client-report "Acme Dental" --since 30d gathers detection count and weekly trend, top entities and threats, posture and report runs for one customer.See pain-point.md for the longer narrative.
Yes, on **Plus, Pro, Team, Business,
Nur der Anfang wird gezeigt; den Rest findest du im Repo