Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Blackpoint Cyber CompassOne: tenants, detections, assets, vulnerabilities and a cross-tenant view.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
PRINTING_PRESS_CLIENT_PROFILE, BLACKPOINT_API_TOKEN, BLACKPOINT_BASE_URL, BLACKPOINT_MCP_READ_ONLY, BLACKPOINT_NO_LOCAL_DATA, BLACKPOINT_USER_AGENT, BLACKPOINT_MCP_HTTP_TOKENLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
BLACKPOINT_BASE_URL envBLACKPOINT_MCP_READ_ONLY envBLACKPOINT_NO_LOCAL_DATA envBLACKPOINT_USER_AGENT envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: PRINTING_PRESS_CLIENT_PROFILE, BLACKPOINT_API_TOKEN, BLACKPOINT_MCP_HTTP_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.1) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Whisper
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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,
Solo se muestra el principio; lee el resto en el repo