Satnogs MCP server
SatNOGS DB: satellite transmitter and observation data.
C65/100grade C
Adoption
Not measured yet
Usage numbers are collected on the next scan
Reviews
Write oneNobody has reviewed Satnogs yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Satnogs tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
by_modeTransmitters by mode.
transmittersList satellite transmitters.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
no findings
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityno repository or website to verify2/10
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y satnogs-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add satnogs-mcp -- npx -y satnogs-mcp
Satnogs: common questions
- Is Satnogs MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Satnogs safety report
- How do I install Satnogs?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Satnogs need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Satnogs maintained?
- The latest release is v1.0.0.