# N2yo (npm · @pipeworx/mcp-n2yo)

N2YO MCP — wraps the N2YO Satellite Tracking REST API (n2yo.com)

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-n2yo/n2yo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-n2yo/n2yo-mcp)
- npm · `@pipeworx/mcp-n2yo`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo.md), [page](https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-n2yo`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-n2yo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 758 tokens (~252/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the N2yo MCP server?

N2yo runs locally as an npm package, launched with npx -y @pipeworx/mcp-n2yo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-n2yo -- npx -y @pipeworx/mcp-n2yo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-n2yo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n2yo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-n2yo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n2yo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-n2yo -- npx -y @pipeworx/mcp-n2yo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-n2yo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-n2yo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-n2yo --command npx --arg -y --arg @pipeworx/mcp-n2yo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-n2yo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-n2yo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-n2yo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-n2yo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-n2yo -t stdio -c npx -a -y @pipeworx/mcp-n2yo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-n2yo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-n2yo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-02 (score 80, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `get_positions` (~235 tokens)

Track where a satellite is right now (or in the next few seconds): get its live latitude, longitude, altitude, and look-angles (azimuth/elevation) from an observer on Earth. Use this to answer "where is the ISS right now?" (NORAD id 25544) or to locate any satellite by NORAD id. Example: get_positions({ norad_id: 25544, lat: 40.71, lon: -74.0 }).

Input parameters:

- `_apiKey` (string): Optional — your own N2YO API key for higher limits; omit to use the shared Pipeworx key.
- `altitude` (number): Observer altitude in meters above sea level (default 0).
- `lat` (number, required): Observer latitude in decimal degrees.
- `lon` (number, required): Observer longitude in decimal degrees.
- `norad_id` (number, required): NORAD catalog id of the satellite, e.g. 25544 for the ISS, 20580 for Hubble.
- `seconds` (number): Number of future seconds of positions to predict (default 2, max 300).

### `get_visual_passes` (~246 tokens)

Find when a satellite will be visible to the naked eye overhead from an observer location (visual passes = bright, sunlit passes against a dark sky). Returns start/max/end times, elevation, azimuths, brightness magnitude, and duration. Use this for "when can I see the ISS pass over?" Example: get_visual_passes({ norad_id: 25544, lat: 40.71, lon: -74.0 }).

Input parameters:

- `_apiKey` (string): Optional — your own N2YO API key for higher limits; omit to use the shared Pipeworx key.
- `altitude` (number): Observer altitude in meters above sea level (default 0).
- `days` (number): Number of days ahead to search for passes (default 5, max 10).
- `lat` (number, required): Observer latitude in decimal degrees.
- `lon` (number, required): Observer longitude in decimal degrees.
- `min_visibility` (number): Minimum visible duration in seconds for a pass to be returned (default 300).
- `norad_id` (number, required): NORAD catalog id of the satellite, e.g. 25544 for the ISS.

### `whats_above` (~223 tokens)

List what satellites are currently above a location on Earth, within a given radius of the observer's zenith. Use this to answer "what satellites are overhead right now?" Optionally filter by category (e.g. 52 = Starlink, 18 = amateur radio, 1 = brightest). Example: whats_above({ lat: 40.71, lon: -74.0 }).

Input parameters:

- `_apiKey` (string): Optional — your own N2YO API key for higher limits; omit to use the shared Pipeworx key.
- `altitude` (number): Observer altitude in meters above sea level (default 0).
- `category` (number): N2YO category filter: 0 = all (default), 18 = amateur radio, 52 = Starlink, 1 = brightest.
- `lat` (number, required): Observer latitude in decimal degrees.
- `lon` (number, required): Observer longitude in decimal degrees.
- `radius` (number): Search radius in degrees from the observer zenith (default 70, max 90).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the N2yo MCP server?

N2yo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/n2yo. N2YO MCP, wraps the N2YO Satellite Tracking REST API (n2yo.com). This page covers its npm package (@pipeworx/mcp-n2yo).

### Is the N2yo MCP server safe to use?

N2yo scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the N2yo MCP server expose?

N2yo exposes 3 tools: get_positions, get_visual_passes, whats_above. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.

### Is the N2yo MCP server still maintained?

N2yo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the N2yo MCP server under?

N2yo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the N2yo MCP server?

VerifyMCP ran 16 checks on N2yo, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-n2yo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-n2yo
- Repository: https://github.com/pipeworx-io/mcp-n2yo
- Website: https://pipeworx.io/packs/n2yo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-n2yo/pipeworx-mcp-n2yo