Skip to content
Back to search

connectors

MCP servers that Zero Root writes for security tools whose vendor publishes none. Each one runs behind a Gibson connector.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 21 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/zeroroot-ai/connectors with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/zeroroot-ai/connectors'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/zeroroot-ai--connectors/badge.svg)](/listings/zeroroot-ai--connectors)

HTML

<a href="/listings/zeroroot-ai--connectors"><img src="/api/listings/zeroroot-ai--connectors/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 86 lines
  1. # connectors
  2. This repo holds the MCP servers that Zero Root writes for security tools whose vendor publishes none, and for response actions that no vendor server offers (ADR-0177, ADR-0180). Each server runs behind a Gibson connector. The Gibson catalog pins the image of each server by digest.
  3. ## Layout
  4. The repo is one Go module. We chose one module over one module for each tool for three reasons.
  5. 1. The shared code is one internal package, `internal/kit`. A separate module for each tool would need a published shared module or a `replace` directive, and the organization forbids `replace`.
  6. 2. Each tool still has its own directory, its own `package main` and its own `Dockerfile`. The image of a tool holds only the packages that its binary imports. It is one small static binary.
  7. 3. One `go.mod` means one dependency set to scan and to update.
  8. | Path | Content |
  9. |---|---|
  10. | `internal/kit` | Environment, secret type, logger, vendor HTTP client, validation, tool helpers and the streamable HTTP server. |
  11. | `internal/fixloop` | The types of the fix loop that the two Git host servers share. |
  12. | `internal/kit/kittest` | Test helpers: an in-memory MCP client. |
  13. | `<tool>/` | One server: `main.go`, `server.go`, tests, `Dockerfile`, `README.md`. |
  14. | `_template/` | The template of a new server. |
  15. | `scripts/` | `new-server.sh` and the guard `check-servers.sh` with its failing fixture. |
  16. ## Start a new server
  17. ```sh
  18. make new-server NAME=<tool>
  19. ```
  20. This copies `_template/` to `<tool>/`. Then edit `<tool>/server.go`, cite the page of the vendor API reference in a comment, write the tests against an `httptest` mock, and state the vendor permission in `<tool>/README.md`. The image workflow finds the new directory by its `Dockerfile`. It needs no edit.
  21. ## How a server runs
  22. - It serves streamable HTTP on `LISTEN_ADDR` (default `:8080`) at `/mcp`. It answers `/healthz` with HTTP 200. The session is stateless.
  23. - It reads each credential and each base URL from its environment. A missing variable stops the start and names the variable, never its value.
  24. - The server has no authentication of its own. The ToolHive proxy of the connector authenticates the daemon in front of it. Do not expose the port in any other way.
  25. ## Deployment requirement
  26. The MCP endpoint of each server binds `:8080` with no caller authentication. A caller that reaches the port can call each tool with the vendor credential of the server. The ToolHive proxy of the connector is the only access control.
  27. 1. Apply a NetworkPolicy to each server pod that admits ingress to port 8080 only from the ToolHive proxy pod of its connector.
  28. 2. Do not expose the port through a Service of type `LoadBalancer` or `NodePort`, an Ingress or a port-forward.
  29. The servers have no second authentication scheme, by design. The README of each server states the same requirement.
  30. - The vendor client sends a request to the fixed base URL only. It builds each path from escaped segments, never follows a redirect, limits the time and the size of a call, and retries only a request that is safe to repeat.
  31. - A log line holds the name of a tool, its outcome and its duration. It never holds an input, an output or a credential.
  32. ## Rules
  33. - A server holds no credential in its image. It reads each credential from its environment.
  34. - An input of a model is untrusted. Each tool checks the format and the length of each input. No server builds a shell command, and no server follows a URL from an input.
  35. - Each tool has a test against an `httptest` mock of the vendor API. The mock follows the public API reference of the vendor, and a comment cites the page.
  36. - A tool that changes its target carries the MCP annotations `destructiveHint`, `idempotentHint` and `readOnlyHint`. Its description names the tool that undoes the change, or says that no tool does (ADR-0180).
  37. - A server asks for the least API permission that its tools need. Its README states that permission.
  38. ## Commands
  39. | Command | Action |
  40. |---|---|
  41. | `make test` | Run the unit tests. |
  42. | `make check` | Run gofmt, `go vet` and the server guard. |
  43. | `make lint` | Run golangci-lint. |
  44. | `make build` | Compile each server into `bin/`. |
  45. ## Servers
  46. | Directory | Tool class | Tools | Issue |
  47. |---|---|---|---|
  48. | `prometheus` | observability | `query_instant`, `query_range`, `list_alerts`, `health_signal` | gibson#1540 |
  49. | `gitlab-fixloop` | git-host | `merge_request_state`, `merge_merge_request`, `revert_merge_request`, `deployment_state` | gibson#1539 |
  50. | `github-fixloop` | git-host | `merge_request_state`, `merge_merge_request`, `revert_merge_request`, `deployment_state` | gibson#1539 |
  51. | `okta` | identity, response | `revoke_user_sessions`, `suspend_user`, `unsuspend_user` | gibson#1548 |
  52. | `entra-id` | identity, response | `revoke_sign_in_sessions`, `disable_account`, `enable_account` | gibson#1549 |
  53. | `crowdstrike` | edr, response | `contain_host`, `lift_containment` | gibson#1545 |
  54. | `defender-endpoint` | edr, response | `isolate_device`, `release_device` | gibson#1546 |
  55. | `sentinelone` | edr, response | `disconnect_from_network`, `reconnect_to_network` | gibson#1547 |
  56. | `qualys` | scanner | `get_host_detections` | gibson#1541 |
  57. | `puppet` | patch | `start_patch_job`, `start_rollback_job`, `get_job` | gibson#1544 |
  58. ## Not built
  59. - Trellix (gibson#1542): the API reference of Trellix did not load from the workstation of the author, and no public source gave the request and response of an isolate call.
  60. - Microsoft Intune (gibson#1543): Microsoft Graph v1.0 has no call that starts a patch for one device, reads its result or rolls it back. The update profiles are in the beta API and they target groups.
  61. ## License
  62. Elastic License 2.0. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.