Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Voyager Net

by dir-aiversion 0.14.0i★ –iRuns on your computer
Registry nameio.github.dir-ai/voyager-net

Install

Overview

Description from the maker (original English)

A safe, read-only, authorized audit of one host you own: DNS, ports, TLS, HTTP hygiene.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "voyager-net": {
      "command": "npx",
      "args": [
        "-y",
        "@dir-ai/voyager-net",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add voyager-net -- npx -y @dir-ai/voyager-net mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "voyager-net": {
      "command": "npx",
      "args": [
        "-y",
        "@dir-ai/voyager-net",
        "mcp"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "voyager-net": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dir-ai/voyager-net",
        "mcp"
      ]
    }
  }
}

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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account dir-ai, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 4908 servers in this category
  • Published to the registry more recently than 27% of the other 4908 servers in this category
  • Basic checks equal to or better than 100% of the other 4908 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Voyager Net safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.14.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

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

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago
Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago
Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install

README from the maker

Open the README

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.

voyager-net

**Voyager's network organ — a safe, read-only, *authorized* audit of one host or domain you own, so an AI agent can find the falle in your infra and describe the fix.**

Voyager penetrates the web (@dir-ai/voyager), the repo (@dir-ai/voyager-repo), and — here — networks. This is the *sense*: it finds problems. Applying fixes ("the hands") is a separate, consent-gated organ, by design — an AI must never mutate live infrastructure on its own.

voyager-net scan yourhost.example.com --authorized

voyager-net scan 10.0.5.20 --authorized --ports 22,80,443,5432

What it checks (read-only)

  • Resolve-once + IP pinning (every probe, HTTP included) — a domain is resolved a single time and **the DNS, port, TLS *and* HTTP probes are all pinned to that one IP** via a custom socket lookup, so nothing re-resolves the name mid-scan (closes the HTTP DNS-rebinding path). The resolved IP is classified canonically (via ipaddr.js) and any non-public address — loopback, private, link-local, CGNAT, NAT64, IPv4-mapped IPv6, metadata — is refused.
  • DNS — A/AAAA/MX/TXT/CAA + email/CA hygiene, and it grades the content: SPF +all (anyone may send) and DMARC p=none (no enforcement) are findings, not just presence checks. All target-controlled records are injection-framed.
  • Ports — a bounded common-service probe by plain TCP connect() with real states (open / closed / filtered / unreachable — an OS timeout reads as *filtered*, not closed), no SYN tricks, no payloads, no range/CIDR sweeps.
  • Service fingerprinting — reads the banner a service *volunteers* on connect (SSH, SMTP, FTP, POP3, IMAP) to identify product + version (framed).
  • Unauthenticated-service detection — for auth-expecting services (Redis, Memcached, Elasticsearch, CouchDB, Docker API, ZooKeeper) it sends ONE benign, read-only protocol hello (e.g. Redis PING) and reports the service as exposed only if it answers *without* asking for credentials. Honest scope: this and the TLS/HTTP inspectors DO send bytes (a ClientHello, a GET /, a protocol hello) — the audit is active-but-safe (no writes, no mutation, no exploit), not purely passive, and it runs only against the host you authorized.
  • TLS — the full set of accepted protocol versions (not just the negotiated one), chain trust against the system store (any validation failure is reported, not only self-signed), RSA key size (EC/EdDSA exempted), certificate expiry/issuer.
  • HTTP hygiene (graded) — status, Server banner, HSTS/CSP quality (weak max-age, unsafe-inline/wildcard — not just presence), clickjacking protection, per-cookie Secure/HttpOnly (each cookie evaluated on its own), CORS wildcard *and* the dangerous credentials-with-origin case, version-leak, and HTTP→HTTPS redirect. All pinned to the vetted IP.
  • Honest partial — an open TLS/HTTP port that couldn't be inspected is reported as *UNKNOWN*, never folded into a "no issues" verdict.

Findings that name a detected service+version suggest checking it against a CVE feed — voyager-net detects the version; **CVE *matching* stays a lookup, and CVE *probing* (Nuclei &c.) is out of scope** — that is active testing, a separate, more-gated capability, not a read-only sense.

Each finding carries a severity, confidence, and a described fix — e.g. "certificate expires in 6d → renew and automate ACME", "mysql reachable publicly → restrict to a private network", "no DMARC → publish v=DMARC1; p=quarantine".

Safety — non-negotiable

  • Authorized-only, fail-closed. Without --authorized (CLI) / authorized:true (MCP) it refuses. You assert you own / may test the target.
  • One host or domain only. CIDR ranges, IP ranges, lists, wildcards, and URLs are rejected — it can never become a mass scanner.
  • Cloud metadata endpoints are hard-blocked (169.254.169.254 etc.).
  • Read-only. It never applies a fix, exploits, floods, or mutates anything. Bounded concurrency and timeouts; a plain TCP connect, not a scanner's SYN sweep.
  • Untrusted output framed. Every target-controlled string — banners, certificate subject/issuer/SANs, Server/CSP headers, CORS value, and DNS TXT/CAA/MX records — is injection-stripped before your model sees it.
  • Exit codes: 0 clean · 1 high/critical finding(s) · 2 tool error / not authorized.

Scanning infrastructure you do not own or have explicit permission to test may

be illegal in your jurisdiction. This tool is for auditing your own systems.

MCP

voyager-net mcp

Tool: scan_host — same audit, fail-closed (authorized defaults off).

Library

import { scan } from '@dir-ai/voyager-net'

const brief = await scan('yourhost.example.com', { authorized: true }) const urgent = brief.findings.filter((f) => f.severity === 'high' || f.severity === 'critical')

Roadmap

Wrap Prowler/Steampipe (cloud config), Trivy (CVE), Hubble (flow) under the same trust contract; attack-path correlation; drift (IaC declared ↔ actual). Then — separately and consent-gated — the remediation "hands".

License

MIT

Ask PopNx